Permissions determine who can view, change, run, or manage work. Start with three things: the person or application, the resource, and the intended action. Access to one step does not automatically authorize the rest of a workflow.
Ownership and participation
A resource has an individual owner within a Workspace. Sharing gives another person a role on that resource without transferring ownership. Workspace membership establishes organizational participation; a resource invitation provides access to particular work.
| Need | Access |
|---|---|
| Help with one Chat or Project | A resource invitation. |
| Participate in the organization | Workspace membership. |
| Run an Agent from software | An explicit Agent application grant. |
| Use a released application | Site visitor access and any application login. |
A consultant can collaborate on one Project without joining its Workspace. Use Members for organizational roles and Sharing for choosing the appropriate resource or result.
Membership and resource access
Workspace-visible Chats, Agents, Projects, and Artifacts inherit each active member's Admin, Editor, or Viewer role. Private resources require individual ownership or an explicit resource grant; being the Workspace Owner does not by itself give access to an active member's private content. Site management and visitor access follow Site access.
For example, a Workspace Viewer can read a Workspace-visible Chat. Making that Chat private removes membership-derived access, but preserves explicit grants. A direct Editor invitation can still allow that person to edit it. The highest applicable role governs resource access, while inactive membership denies access to the Workspace.
Separate kinds of authority
Reading a file, editing source, running work, assigning an external account, and releasing software can require different permissions.
- An Agent application grant governs an application's access to the Agent.
- A connection assignment governs use of an external account.
- A developer credential limits authenticated operations to its scope and the user's current access.
- A resource role governs actions on that resource.
- Site access distinguishes visitors from people who manage production.
Mentioning a resource or linking to a private document does not grant access to it. Likewise, associating an Agent with a Project or Site organizes the work without granting invocation authority.
Approvals and policy
An approval determines whether an otherwise authorized action may proceed within a reviewed scope. It cannot supply missing access. Instructions and Skills guide behavior but cannot override platform restrictions or organizational policy.
For example, approving a Plan to prepare a release does not give the Operator permission to use an unassigned production connection. If the proposed approach changes materially, revisit the reviewed Plan and its scope.
Preferences explains supported approval behavior. Enterprise covers organizational controls and their current limits. Funding remains separate: credits do not grant access, and approval does not add credits.
Example: release a customer portal
A collaborator may be able to edit a Project without being able to update its Site. Before release, check source access, destination authority, production configuration, and required approvals. Use Releases for the workflow.
If an action is denied, identify which boundary applies before broadening access. Check the active account and Workspace, the resource role, and any connection assignment. A larger role is not always the missing requirement.
When responsibilities change
Review both membership and explicit resource grants. Before deactivation or removal, consider owned resources, schedules, application consumers, and production dependencies. These relationships can outlast the original task.
Follow Members and Workspace lifecycle for the supported departure and continuity workflows.