# Team roles

Source: https://www.hyperagent.com/docs/concepts/teams/members

> For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL.

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.

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 [#permission-matrix]



## Choose the smallest role that fits [#choose-the-smallest-role-that-fits]

A support rep runs Scout, uses its escalation skill, and reads approved team
memories.

A documentation specialist improves Scribe and curates the context it needs.

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-dont-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 [#denied-memory-changes]

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.

## FAQs [#faqs]

Member. It lets someone run the team's agents, use its skills, and read approved team memories without changing the maintained source. Editor is for the people who improve those resources; Owner is for whoever is accountable for the team itself.

No. Membership, invitations, roles, and team settings are Owner-only. Editors maintain the team's agents, skills, and memories, which is a deliberate separation: maintaining a shared agent shouldn't come with control over who belongs.

No. A shared personal agent stays under its owner's control whatever your role. Editors can run it and nothing more. If several people need to maintain it, it should be team-owned instead.

The change is denied outright. It doesn't quietly become a personal memory that looks like the team update worked, so there's never any doubt about whether shared context changed.

Only the team's Owner, read-only, on agents the team owns. Editors can maintain a shared agent without seeing what anyone did with it, and Members see only their own threads. The grant exists so someone is accountable for what the fleet does. See [what's private and what's shared](https://www.hyperagent.com/docs/concepts/teams/whats-private).

Yes, and it usually should. A team must always have at least one, so the last Owner can't be demoted or removed. Promote a second Owner before anyone needs to step down.