Grant the smallest useful scope
Choose the job first, apply read-only or read-and-write inside that role, then grant only the workspaces the agent needs.
Role boundary
Admin can manage granted workspaces and route both specialist skills. Appointment Setter can read relationship and knowledge context but cannot write knowledge or call Atomic Article tools. Content Writer can read workspace knowledge, propose draft revisions, and call the Atomic Article control plane, but cannot initialize or activate knowledge or administer a workspace. Authenticated tools/list hides tools outside that role, and direct calls are checked again server-side.
Read-only agents
Read-only credentials are suited to search, retrieval, context loading, reporting, and verification. The server rejects mutating operations even if the client attempts to call one.
Read-and-write agents
Grant write access only when the automation must modify workspace state. A Content Writer knowledge change is stored as a draft revision and enters human review; it does not replace the active document. Review the exact tool and its annotations before approving any workflow that changes data.
Workspace grants
- Grant only the workspaces required for the agent’s job.
- Use separate agents when automations have different owners or responsibilities.
- Review and revoke unused grants regularly.
- A tool marked Human action requires an authenticated person rather than an isolated agent.