Team roles
Choose Owner, Editor, and Member by what each person needs to run, maintain, or administer.
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 team.
Give people the work, not the keys
Owners administer the team, Editors maintain its shared agents and context, and Members run what the team has built. Each person gets what their job needs and nothing they'd have to be careful with.
Permission matrix
| Responsibility | Owner | Editor | Member |
|---|---|---|---|
| Run Team agents and use Team skills | Allowed | Allowed | Allowed |
| Read Team memories | Allowed | Allowed | Allowed |
| Edit Team-owned agents and skills | Allowed | Allowed | Not allowed |
| Add and curate Team memories | Allowed | Allowed | Not allowed |
| Read another member's runs on a team-owned agent | Allowed | Not allowed | Not allowed |
| Manage members, invitations, roles, and Team settings | Allowed | Not allowed | Not allowed |
| Permanently delete Team memories | Allowed | Not allowed | Not allowed |
Choose the smallest role that fits
Member
A support rep runs Scout, uses its escalation skill, and reads approved team 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 Editor access to membership nobody needs is a risk, and a Member who should be maintaining Scribe is a bottleneck.
Roles don't reach shared personal resources
Roles govern what the team owns. A personal agent or skill shared with the team 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 team-owned.
Denied memory changes
A denied Team change stays denied
When a Member tries to add or change Team memory, Hyperagent denies the change. It does not save the attempted Team update as personal data instead.
The result is either a permitted team change or no change, never a personal memory that looks like the team update worked. Give someone Editor when curating shared context is part of their job.