Skip to content
New: Mac downloadRead →

Data and reporting

Explore data within your workspace permissions

Data Explorer lets you inspect workspace data through a visual canvas, supported query syntax, or an AI-assisted query. The same server-side access controls apply regardless of how you build the query.

Reviewed October 2026

Build and inspect a query

  1. Open Data Explorer and choose a source from the source library.
  2. Start with a small set of columns and a narrow filter. Use the canvas to add relationships or the query editor for supported SQL-style queries.
  3. If you use the AI query bar, describe the question, then inspect the generated sources, joins, fields, and filters before running it.
  4. Run the query and review its results. Use the available chart or saved-query controls when you want to revisit the analysis.

Understand row visibility

Access requires the effective Data Explorer read permission. A stored denial still applies. Ownership and reporting hierarchy then determine which rows are available to the actor.

Owned sources follow permitted owners. Child records inherit their parent’s visibility, and account-linked sources follow visible accounts. Workspace-shared sources have their own classification. A source without a visibility classification is withheld from restricted users.

A team or organization scope does not override hierarchy restrictions. Empty results can reflect access boundaries as well as filters.

Administrator-only sensitive fields

Within Data Explorer and its reporting surfaces, sensitive fields require workspace administrator access. They are removed from non-admin schemas and results, and requests that explicitly name them are rejected.

  • Meeting transcripts and summaries.
  • Meeting recording file URLs.
  • Calendar event descriptions.
  • Task comment content.
  • Form submission response data.

Apply the same expectations to reports

Custom Reports use the same hierarchy and sensitive-field boundaries, including grouping and detail queries. AI-generated queries do not bypass those checks. If a needed field or record is unavailable, ask an administrator to review your role and reporting hierarchy instead of trying alternate query syntax.

Related guides