Workspace roles
Choose by what each person needs to do: run, maintain, or administer agents.
Roles split responsibility by outcome, so broad use never requires broad authority. Someone can run Scout every day without touching its escalation logic; someone else can maintain Scout and Scribe without managing who belongs to the workspace.
Give people the work, not the keys
Owners administer the workspace, Editors maintain its shared agents and context, and Members run what the workspace has built. Each person gets what their job needs and nothing they'd have to be careful with.
Roles and Capabilities
| Responsibility | Owner | Editor | Member |
|---|---|---|---|
| Run workspace agents and use available skills | Yes | Yes | Yes |
| Read workspace-library memories and documents | Yes | Yes | Yes |
| Edit workspace-owned agents and skills | Yes | Yes | No |
| Add and curate workspace memories and documents | Yes | Yes | No |
| Review other members' workspace threads read-only | Yes | No | No |
| Manage members, invitations, roles, and workspace settings | Yes | No | No |
| Permanently delete workspace-library memories and documents | Yes | No | No |
Workspace oversight includes agentless workspace threads. It does not grant access to Personal. Channel visibility follows its own workspace-wide read rules; see privacy and sharing.
Choose the smallest role that fits
Member
A support rep runs Scout, uses its escalation skill, and reads approved workspace memories.
Editor
A documentation specialist improves Scribe and curates the context it needs.
Owner
The person accountable for membership, roles, settings, permanent deletion, and read-only oversight of other people's runs.
Match the role to ongoing responsibility, not seniority. Start narrow and widen it later, since unnecessary edit access is a risk, while a Member who should maintain Scribe cannot make the changes their job needs.
Roles don't reach shared personal resources
Roles govern what the workspace owns. A personal agent or skill shared with the workspace stays under its owner's control: Editors can run Press but not edit it, and only its owner can change its configuration. When several people need to maintain it, make it workspace-owned.
Denied memory changes
A denied Workspace change stays denied
When a Member tries to add or change Workspace memory, Hyperagent denies the change. It does not save the attempted Workspace update as personal data instead.
The result is either a permitted workspace change or no change, never a personal memory that looks like the workspace update worked. Give someone Editor when curating shared context is part of their job.