PRODUCT GUIDE
Define the permitted scope
Define the maximum workspace/function/object/provider scope automation may use.
Product guide · Based on the September 18, 2026 product documentation. Connected proof is reported for specific operations; this guide is not a new live certification. Private work and provider authorization take place in Agent.
What this is for
Define the maximum workspace/function/object/provider scope automation may use.
Versioned envelope and autonomy assignments can narrow but never widen platform authority.
Before you start
Prerequisites
- authorized admin
Operating modes and access
Documented modes: ASSIST and AGENT. Modes do not grant access or execution authority.
Relevant roles: OWNER, ADMIN. A listed role does not imply that every action on the screen is permitted.
Check mode and role boundariesWhat is checked
- versioned revision
- underlying authority conjunction
Evidence and limits
Documented connected scope. The supplied documentation reports bounded connected evidence. It does not establish every configuration, provider, user or operation.
No provider-wide integration claim is made by this capability.
Important limits
- Envelope cannot make an otherwise forbidden action legal.
Apply it to your service
Start with the service you deliver. Industry examples are hypotheses to review, not proof of demand or results.
Choose the next step
Explore the public sample, or open Agent to review the relevant setup and permissions for an existing Workspace.
YOUR NEXT MOVE
Start with a clearer
next move.
Explore a Blueprint before deciding how much work to delegate.
Preview available. Paid checkout is not open.