Scopes
A feature’s scope decides who can see it — and everything inside it inherits that audience. Concepts: Scopes and sharing.
The three scopes
Section titled “The three scopes”| Scope | Meaning (product wording) | Who can reach it |
|---|---|---|
| Private | “Visible only to the creator.” | Only the feature’s creator (admins retain governance powers) |
| Workspace | “Shared within a single workspace.” | Members of that one workspace |
| Organization | “Available across all workspaces.” | Workspaces the feature is attached to — see below |
Who approves a feature scope change
Section titled “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 → Workspace | A workspace admin of the target workspace, or a Data Admin |
| Private / Workspace → Organization | A Data Admin |
| Organization → Workspace (demotion) | A Data Admin |
| Any → Private (demotion) | A Data 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
Section titled “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 (workspace/org 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 workspace with View / Full access modes |
Moving a resource between features
Section titled “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 a Data Admin’s approval |
| Anything → Workspace-scoped feature | Requires a workspace admin of the destination |
| Workspace → Private | Requires a workspace admin of the source |
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
Section titled “Scope and roles, in brief”| Action | Minimum role |
|---|---|
| Create a private feature | User |
| Request a promotion | User (the feature’s owner) |
| Approve into a workspace | Workspace admin or Data Admin |
| Approve into the organization / approve demotions | Data Admin |
| Attach org features to workspaces (the matrix) | Data Admin |
Full role detail: the roles capability matrix.