Invite colleagues, set roles, and understand the first sign-in.
Your organization is managed in the sign-in provider. The Organization page of the dashboard shows 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 on the Admin page.
The colleague accepts the invitation, connects a client, and signs in. 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.
| 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.
A Mana admin changes a role on the Admin page: choose the new role beside the person and Set role. 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 person's open sessions end and the next sign-in carries the new role. The last admin of an organization cannot be demoted.
To remove a person, revoke the access on the Admin page and remove the person in the Organization page of the sign-in provider. Automatic revocation on removal is planned.
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.
A role change in the sign-in provider does not widen existing access on its own. Widening is a human act: a Mana admin sets the role on the Admin page.