Roles
Nobody can give a role above their own. An organisation has exactly one Owner. See Organisations and roles.
Bring in a colleague
Send them an invitation by email: they open the link, choose a password, and they are in. They do not need an account first. See Invitations. If they already have an account on this MITHUNAI deployment, the same invitation works: they confirm with the password they already use.Change someone’s role
Choose a new role in their row and confirm. Their access changes straight away.- You cannot change your own role. Ask another Administrator.
- You cannot change the Owner’s role here. Ownership moves with Make owner (below).
- You cannot change someone more senior than you, or give a role above your own.
- Lowering a role also stops the API keys that person created, and the invitations they sent, for roles above their new one.
Remove someone
Press Remove in their row and confirm. Removing someone:- signs them out of the console on every device, and stops their sign-ins to Chat, Agents and the Gateway from being renewed;
- takes away their access to this organisation (their account itself is not deleted, and other organisations they belong to are not affected);
- stops every API key they created here, so check the API keys list first if an integration uses one;
- withdraws the invitations they sent that have not been accepted.
Make someone else the Owner
Only the Owner sees this. Press Make owner in a member’s row and confirm. In one step:- that person becomes the Owner;
- you become an Administrator, so you can still manage the organisation, but only the new Owner can transfer it again;
- any API key you created with the Owner role stops working, because an Administrator cannot create one;
- both of you are sent an email about the change, if your deployment can send email.
With the API
Every change takes a signed-in console session, not an API key, so a leaked key can never be used to add, change or remove people. Listing members works with either.
What a member can open
A member signs in to the console with their own account and sees what their role allows. The same account opens Chat, which admits members of the organisation it serves. The Model Gateway admits platform administrators and, where the deployment allows it, an organisation’s Owners and Administrators. Agents is in beta, with access on request. See One sign-in.Not available yet
- Self-service sign-up. Request access on the sign-in screen does not create an account on its own: you confirm your email address, a person on the MITHUNAI team approves the request, and a welcome email lets you choose a password (Request access). Inside an existing organisation, a colleague’s invitation is the way in.
- SSO and SCIM provisioning. See Product status.