Members and roles
Invite colleagues, set roles, and understand the first sign-in.
On this page5 parts
Your organization is managed in the sign-in provider. In Settings, Manage members on the Members card opens it: members, invitations, and the subscription. The first visit asks you to continue to your organization once; you are already signed in, so nothing is typed again. Mana reads the organization when a person signs in for the first time and sets up the access. There is no separate Mana user list to maintain.
The first person of an organization to sign in becomes its Mana admin. Every later person joins as a member. An admin promotes a member with Manage members.
Invite a colleague
- Open Settings, and choose Manage members on the Members card.
- Choose Invite and enter the email address.
- Choose the role: Admin or Member.
- Send the invitation.
The colleague accepts the invitation, connects an agent, and signs in, as You were invited to a team shows. The sign-in shows an organization selector: the colleague picks your organization. Mana creates the member access at that moment. No operator step is needed.
To give every member the Claude Code plugin at once, an admin adds the managed settings in Claude Code.
Roles
| Role | Reads up to | Adds memories | Corrects memories |
|---|---|---|---|
| Admin | confidential | yes | yes |
| Member | internal | yes | no |
The access lasts one year from the first sign-in and renews at the next sign-in after that.
Change a role or remove a person
An admin changes a role with Manage members. When the sign-in provider reports the change, Mana issues the access of the new role, ends the earlier access, and moves the person's sign-in to it in one step. The next sign-in of the person's agents carries the new role. Mana does not demote the last admin of an organization, so the organization always keeps one.
To remove a person, an admin removes them with Manage members. When the sign-in provider reports the removal, Mana ends the person's access and their sign-in. Their agents are refused from the next call. There is no second step in Mana.
Teams: who reads what
A team is a part of the organization that can be given knowledge. A Mana admin manages teams from Settings, then Teams:
- New team creates one.
- On a person's row, Add to puts them in a team and Remove takes them out. Mana issues the person's access again with the new teams and ends the earlier access in one step, so their agents sign in once more.
- Under Imports, tick the teams that read an organization import and Save. Everything the import holds is read by those teams at once, and so is every file a later sync brings. An organization import nobody ticked is read by nobody. A person's own vault is not on this page: it is read by that person alone until they share it, and no admin sets its readers.
A member does not see the page, and the store refuses a member who tries anyway.
No organization yet
A person who signs in without an organization gets a personal space. The person is its admin. Knowledge stored there is not shared with any organization. Create an organization and invite people when you want to share.
Roles and members are kept in one place: Manage members on the Members card of Settings. Mana keeps no second list of members. An invitation gives no access on its own: a person gets access at their first sign-in. Widening stays a human act, because only an admin of the organization can change a role there.