Organize projects and workspaces
Keep project membership, application resources and context grants understandable.
Use the right unit of organization
A workspace organizes project or client resources. An ACN space organizes agent context. Do not assume membership in one automatically grants access to the other.
Assign project responsibilities explicitly
The workspace guide describes the Owner, Admin, Member and Viewer roles. Review who can manage apps and invite collaborators in the console before assigning access.
Workspace referenceOne balance per account
Workspaces have no credits of their own: every workspace draws on the account's one balance. A workspace budget cap is stored as a label only; nothing counts spending against it and nothing is refused when it is reached.
Credits, limits and usageVerify a client boundary
- Create two test workspaces with distinct members and resources.
- Verify which resources each identity can list, read and modify.
- Check agent context permissions across the boundary: a workspace role grants nothing on an ACN space.
- Review the audit information visible to each role.
Machine-readable contracts: MCP tools JSON · OpenAPI JSON. See the contract notes for older examples.
CONTINUE READINGPublish an app on Exchange →