Sharing Auto Insights

Question

Hi everyone,

I'm running into an issue with Alteryx Auto Insights and was hoping someone might have seen this before.

I created an Auto Insights report and shared it with another user. When the user opens the report, they receive the error message:

"Cannot complete query"

When I shared the Insight, I included the data source permissions as well, so I expected the user to have access to all required data.

A few details:

• The report opens correctly for me.

• The recipient can access Auto Insights.

• The data source was included when sharing.

• The error appears immediately when they try to open the report.

Has anyone experienced this issue before? Are there additional permissions, data source settings, credentials, or sharing configurations that I should verify?

Any suggestions would be greatly appreciated.

Thanks!

andrefc · Answer

Thank you for your prompt response.

I shared the dataset with the user. It's a CSV file that I am using solely as a proof of concept.

I was able to create a new Insight and view the data using that account, although I received a message indicating that I could not proceed further because the account only has Viewer permissions, which makes sense.

However, I am still unable to view the Auto Insights report. I also removed the permissions and shared the dataset again, but the issue persists.

Could you please advise on what I might be missing?

MoramHari · Answer

This error usually happens because sharing a Mission does not automatically grant the recipient the underlying dataset access required to run the queries.Check these three settings to fix it:

* Direct Dataset Access: Go to Data Connections / Dataset Settings in the admin panel. Ensure the user is explicitly added as a Viewer or User on the actual dataset, not just the shared Mission.
* Row-Level Security (RLS): If the dataset uses RLS, the query will fail immediately if the user’s email/profile doesn't map to a valid data restriction filter.
* Live Connection Credentials: If the dataset connects to a live cloud database (e.g., Snowflake, BigQuery) using OAuth or user-level credentials instead of a service account, the recipient's personal database permissions may be blocking the query.

Quick Test: Have the user try to create a brand-new Search/Insight from scratch using that same dataset. If they can't see the dataset, it is a backend permission issue.