Can manage Spotter privilege

Can manage Spotter is the privilege for Spotter administrators — the people responsible for how Spotter behaves across the organization. It lets a user manage Spotter’s global coaching, memory, Spotter instructions, and Spotter Analysts.

Nothing changes for your existing setup. Can manage Spotter is opt-in and assigned by an administrator. No existing privilege or access is modified — coaching access, Can manage data models, and Can use Spotter privileges all continue to work exactly as before.

Who this is for

Managing Spotter is bigger than any one data model. Some of it is tied to a specific Model — the global coaching and memory built on that Model. But Spotter instructions and Spotter Analysts shape how Spotter behaves for everyone across the whole Org.

Managing Spotter through per-data-model coaching access is too narrow — it only ever covers one Model. Reserving it for the administrator role is too broad — that also grants control over users, data, and security. Can manage Spotter is the dedicated middle ground: a single Spotter administrator role for governing Spotter across the organization.

What you can do with this privilege

Can manage Spotter works at two levels.

On the data models you can read, you can:

  • Manage global coaching — promote reference questions, business terms, and data model instructions to the global level.

  • Manage Spotter memory, including memory from Liveboards that span multiple data models. (Any Spotter user can create personal memory from a conversation; this privilege lets you manage it at the global level and across models.)

  • Delegate coaching access to other users — you cannot grant access beyond your own read boundary.

You can only manage coaching and memory on a data model you can read. On a Model you cannot read, you cannot manage its coaching or memory; in a multi-Model Liveboard, Models you cannot read remain inaccessible.

Across Spotter in your Org, regardless of which data models you can read, you can:

  • Add and manage Spotter instructions.

  • Manage every Spotter Analyst in the Org — including Analysts built on data models you cannot read.

Can manage Spotter implies Can use Spotter — no separate Spotter privilege is needed.

What this privilege does not do

  • It does not grant edit access to data models. You cannot change a Model’s structure — columns, synonyms, descriptions — or enable and disable Spotter on a Model. That requires data model edit access. The AI context feature (auto-generated column-level summaries) is a data-model capability and is not governed by this privilege.

  • It does not override data access. It does not grant read access to any data model.

Coaching access is unchanged

Can manage Spotter is additive. Coaching access keeps working exactly as before, scoped to the data model it was granted on. Can manage Spotter is the broader role for someone governing Spotter across many Models; an administrator assigns it explicitly, and it is not an automatic upgrade from coaching access.

Creating and managing Spotter Analysts

Can manage Spotter lets a user manage every Spotter Analyst in the Org, including Analysts built on data models the user cannot read. Creating a Spotter Analyst is different: building one means attaching data models to it, and you can only attach Models you can view — so you cannot create an Analyst on data models you cannot see. Spotter instructions you set do not apply to a Spotter Analyst by default; each Analyst’s instructions are configured by its creator.

Spotter Analysts are beta in 26.7.

Assigning the privilege

Only an administrator can assign Can manage Spotter, from the Admin panel:

  • In instances with role-based access control (RBAC) enabled, add the privilege to a role, then assign the role to a group.

  • In instances with RBAC disabled, add the privilege directly to a user group.

How the privilege surfaces depends on RBAC, not on Org enablement. Can manage Spotter is Org-gated: a user manages Spotter only within their own Org, the same way Spotter’s coaching, memory, and instructions are Org-scoped. It does not grant any control across Orgs.

Because Can manage Spotter grants broad authority over how Spotter behaves for everyone in the Org, assign it to a small, trusted set of users. A holder can add or change global coaching, instructions, memory, and Spotter Analysts — including content other teams maintain.

Because Can manage Spotter grants authority across every data model a user can read, assign it to a small, trusted set of users. A holder can add or change global coaching, instructions, and memory on any Model they can read — including Models maintained by other teams.

Was this page helpful?
×