Accounts & sign-in
Signing in to the web app, and what an account is attached to once you are in.
How you sign in
You always start by entering an email address (or phone number); what happens next depends on which sign-in methods your deployment offers for that account.
| Method | How it works |
|---|---|
| Email code | You enter your address and are emailed a code. Preferred wherever it is available. |
| Phone code | The same, by SMS. Only offered when the deployment has phone sign-in enabled; otherwise the option does not appear. |
| Password | Asked for only when the account has a password and no one-time-code route is available for it. You are taken to a password step after entering your address. |
| Ordinary OAuth sign-in. |
You do not choose between the code and password routes — the app follows the first method your account supports, preferring one-time codes. On a deployment configured for passwordless email codes you will never see a password field.
If the deployment has two-factor authentication switched on, whichever route you took is followed by a 6-digit code emailed to you. It looks identical to the code step above, and a password on its own will not get you in.
Signing in and signing up are the same flow. An address that has no account yet is offered one rather than being told it is wrong.
Your profile
Name, email address, avatar and connected sign-in methods are managed in the account interface reached from your avatar in the app. Mesa does not keep a second copy for you to edit, and the web app's Settings screen — which is not built — would not be where to do it in any case.
Tenants
Your account is not the unit that owns things. A tenant is: bots, keys, conversations, authorized chats and apps all belong to a tenant, and you reach them by being a member of one.
If you belong to more than one, the app asks which you are working in before loading a page that needs it. Everything you then see is scoped to that choice.
Most screens require a tenant. If you have somehow ended up with none, pages that need one will not load, and that is a membership problem for whoever administers your deployment rather than something you can fix from the app.
Organizations
Organization membership is administered outside the app, by whoever runs your deployment. Joining, leaving and role changes are not self-service, and there is no invitation screen in the web app.
Enterprise sign-in
SSO through a corporate identity provider is described under SSO & identity, where its actual status is set out.