Scopes

A feature’s scope decides who can see it — and everything inside it inherits that audience. Concepts: Scopes and sharing.

The two scopes

Scope	Meaning (product wording)	Who can reach it
Private	“Visible only to the creator.”	Only the feature’s creator (admins retain governance powers)
Organization	“Available across the organization.”	Access Groups the feature is attached to, plus any access group set to share all features — see below

Note

To share an org feature with specific teams, an admin attaches it to access groups on the Features × access groups matrix (Shared features page). An access group with “Share all features” turned on reaches every org feature automatically — and because the default access group ships with this on, an org feature is typically reachable across the whole organization unless an admin narrows the default.

Who approves a feature scope change

Scope changes are staged: the current scope stays in effect until an approver accepts. The requester can withdraw any time before that.

Change	Approver
Private → Organization	An Admin
Organization → Private (demotion)	An Admin

• Requesting a promotion is open to the feature’s owner; requesting a demotion is admin-only.
• If the requester is themselves an eligible approver (and the org allows self-approval), the request executes directly.
• Approvals are blocked while a pending move request targets the feature, or while the change would break a dependency.

Scope per resource

Resources don’t carry their own scope — they inherit the feature’s:

Resource	How scope shows up
Table, Workflow, Note, Automation, Data app, Saved Agent	Visible to whoever can reach the owning feature; chips show “Shared” vs “Personal” where relevant
Secret, MCP server	Chip Personal (private feature) or Shared (organization feature); sharing happens by promoting or moving the feature, never per secret
File	Not scope-managed — chat uploads attach to conversations; generated files list under the feature’s File outputs
Exploration	Not scoped at all — private by default and shared per person or access group with View / Full access modes

Moving a resource between features

Moving is its own approval lane, routed by the source and destination scopes:

Move	What happens
Private → your own private feature	Executes immediately (no request)
Anything ↔ Organization-scoped feature	Requires an Admin’s approval

Your explicitly chosen items (“seeds”) can never be excluded from the move; auto-derived dependencies (“linked”) can be unchecked by you or the approver. Each user can have up to 100 open move requests.

Scope and roles, in brief

Action	Minimum role
Create a private feature	User
Request a promotion	User (the feature’s owner)
Approve into the organization / approve demotions	Admin
Attach org features to access groups (the matrix)	Admin

Full role detail: the roles capability matrix.