Error codes
Access and sign-in
Each code of this family: what it means, its most frequent cause, what to do and who can do it.
session_required
- What it means
- The request carries no valid session: it reached a dashboard route without being signed in.
- Most frequent cause
- You signed out, the session cookie was cleared, or the request came from code — which calls the API with an API key instead.
- What to do
- You are not signed in, or your session has ended. Sign in again, then try again.
- Who can do it
- Any member of the workspace
session_expired
- What it means
- The session is older than the longest a session may last on this deployment, so it is refused even though it is still refreshed.
- Most frequent cause
- You signed in a long time ago — every session ends a fixed time after its sign-in, whatever the activity.
- What to do
- Your session has expired. Sign in again to continue.
- Who can do it
- Any member of the workspace
mfa_challenge_required
- What it means
- Your account has two-factor authentication on, and this session has not completed it yet.
- Most frequent cause
- The sign-in stopped before the code was entered, or the session was opened before the factor was added.
- What to do
- Your account uses two-factor authentication: enter the code from your authenticator app to finish signing in, then try again.
- Who can do it
- Any member of the workspace
workspace_required
- What it means
- The request does not name the workspace it is for.
- Most frequent cause
- A link or a script that leaves out
workspaceId, or a screen opened before a workspace was chosen. - What to do
- This request names no workspace. Choose one in the sidebar, then try again; from code, send the workspace’s id.
- Who can do it
- The developer of the calling code
forbidden
- What it means
- Your account is signed in, but it has no access to what the request names.
- Most frequent cause
- You are a member of no workspace yet, a member of another organisation, or your role in the organisation does not allow this action.
- What to do
- You do not have access to this. Ask an owner to invite you, or to give you a role that allows it.
- Who can do it
- An owner of the workspace · Open the screen
not_a_member
- What it means
- You are signed in, but not as a member of the workspace this request names.
- Most frequent cause
- An invitation not accepted yet, a removal from the workspace, or a link to another organisation’s workspace.
- What to do
- You are not a member of this workspace. Ask an owner to invite you, or switch workspace from the sidebar.
- Who can do it
- An owner of the workspace · Open the screen
admin_required
- What it means
- This action is reserved for the owners and admins of the workspace.
- Most frequent cause
- Your role in this workspace is member or viewer.
- What to do
- Only workspace owners and admins can do this. Ask an owner to give you the admin role (Settings › Access).
- Who can do it
- An owner of the workspace · Open the screen
owner_required
- What it means
- This action is reserved for the owners of the workspace.
- Most frequent cause
- Your role in this workspace is admin, member or viewer.
- What to do
- Only a workspace owner can do this. Ask an owner to make the change, or to transfer ownership to you.
- Who can do it
- An owner of the workspace · Open the screen
mfa_required_by_workspace
- What it means
- The workspace asks every member to sign in with two-factor authentication.
- Most frequent cause
- Two-factor authentication is not on for your account yet, or this session was opened without it.
- What to do
- This workspace requires two-factor authentication. Turn it on in Settings › Access, then sign in again.
- Who can do it
- Any member of the workspace · Open the screen
mfa_enrolment_required
- What it means
- The workspace asks its owners and admins to have two-factor authentication before they change roles, retention, API keys, the governance mode or rules.
- Most frequent cause
- Two-factor authentication is not set up on your account yet.
- What to do
- This workspace requires owners and admins to use two-factor authentication. Set it up in Settings › Access, then try again.
- Who can do it
- An owner or admin of the workspace · Open the screen
membership_lookup_failed
- What it means
- Azoth could not check your membership, so it refused rather than guess.
- Most frequent cause
- A brief database or network problem.
- What to do
- We could not check your access just now. Please try again in a moment.
- Who can do it
- Azoth, or the operator of this deployment
csrf_origin_mismatch
- What it means
- The request came from a web address the app does not recognise, so it was refused to protect you from cross-site requests.
- Most frequent cause
- Azoth opened from another address than its usual one (an old domain, a preview link), or a browser extension that rewrites requests.
- What to do
- This request came from an address the app does not recognise. Open Azoth from its usual address and try again.
- Who can do it
- Any member of the workspace
second_admin_required
- What it means
- This action needs a second person to approve it, and the workspace has a single owner or admin.
- Most frequent cause
- Four-eyes approval is on in a workspace with one owner and no admin.
- What to do
- Four-eyes approval needs at least two owners or admins in this workspace. Invite a colleague as admin first (Settings › Access).
- Who can do it
- An owner of the workspace · Open the screen
reviewer_must_differ_from_declarant
- What it means
- A mandate is reviewed by someone other than the person who declared it.
- Most frequent cause
- You declared this system yourself, then tried to approve it.
- What to do
- You declared this mandate, so someone else must review it: another owner or admin of the workspace (four-eyes).
- Who can do it
- An owner or admin of the workspace · Open the screen
email_not_verified
- What it means
- Your e-mail address is not confirmed yet.
- Most frequent cause
- The confirmation link sent at sign-up was not opened, or it has expired.
- What to do
- Confirm your e-mail address first: open the link Azoth sent you, then try again.
- Who can do it
- Any member of the workspace
captcha_failed
- What it means
- The anti-robot check of the form did not pass.
- Most frequent cause
- The form was sent before the check finished, or a blocker stopped it from loading.
- What to do
- The anti-robot check did not go through. Wait for the check under the form, then try again.
- Who can do it
- Any member of the workspace
invalid_credentials
- What it means
- The e-mail address and password do not open an account.
- Most frequent cause
- A mistyped address or password, an account that does not exist, or an address not confirmed yet — the sign-in page does not say which, so that it reveals nothing about who has an account.
- What to do
- Check the e-mail address and the password. Just signed up? Confirm your address first — the sign-in page can send a new confirmation e-mail. Forgot the password? Reset it from the sign-in page.
- Who can do it
- Any member of the workspace
email_domain_not_accepted
- What it means
- Sign-up is refused for addresses of disposable-mail services.
- Most frequent cause
- A temporary address was used to sign up.
- What to do
- This address comes from a disposable-mail service. Sign up with a work or personal address.
- Who can do it
- Any member of the workspace
professional_use_required
- What it means
- Azoth OS is offered only to businesses and professionals: an account is opened only with the declaration that it is for a business or professional activity.
- Most frequent cause
- The sign-up, or the Terms step, was sent without that declaration.
- What to do
- Azoth OS is for professionals only: tick the box saying you sign up on behalf of a business or professional activity, then try again.
- Who can do it
- Any member of the workspace
weak_password
- What it means
- The sign-up refused the password as too weak.
- Most frequent cause
- The password is long enough (8 characters) but too easy to guess — a common word, a sequence, the address itself.
- What to do
- This password is too easy to guess. Choose a longer one — a few unrelated words, or letters mixed with numbers and symbols — then try again.
- Who can do it
- Any member of the workspace
support_access_required
- What it means
- Azoth’s staff cannot open access to the data of this workspace without an owner’s approval.
- Most frequent cause
- No approved support access is in force: none was asked, it was denied, or it has ended.
- What to do
- Azoth’s support cannot open access to this workspace’s data until an owner approves the request. Owners decide it in Settings › Access.
- Who can do it
- An owner of the workspace · Open the screen
permission_denied
- What it means
- Your role in this workspace does not grant the permission this action needs.
- Most frequent cause
- Your role is viewer or member, or a role without that permission.
- What to do
- Your role in this workspace does not allow this. Ask an owner or an admin to do it, or to give you a role that can.
- Who can do it
- An owner of the workspace · Open the screen
invitee_already_member
- What it means
- An invitation adds a person to a workspace; it never changes the role of someone who is a member already. This address is a member’s, so no invitation was created.
- Most frequent cause
- Inviting a member again, often to give them another role — which is a role change, made in Settings › Access.
- What to do
- This address already belongs to a member of this workspace: nothing was sent. To change what they can do, change their role in Settings › Access.
- Who can do it
- An owner or admin of the workspace · Open the screen
invite_role_not_allowed
- What it means
- An invitation grants its role when it is accepted, under the authority of whoever sent it: any workspace role but owner. The role asked for is not one of them, so no invitation was created.
- Most frequent cause
- Inviting someone as owner — ownership is given by an owner in Settings › Access, once the person is a member — or a role name the workspace does not have.
- What to do
- An invitation carries one of these roles: admin, finance, security officer, member or analyst — never owner. To make someone owner, invite them with another role; an owner then changes it in Settings › Access.
- Who can do it
- An owner or admin of the workspace · Open the screen
already_a_member
- What it means
- You opened an invitation to a workspace you are a member of already. It is used up and changed nothing: your role stays as it is.
- Most frequent cause
- An invitation sent to a member’s address, a second click on a link already used, or an account that is a member under another address.
- What to do
- You are already a member of this workspace: the invitation changed nothing, your role stays as it is. Open the workspace from the sidebar; an owner or admin changes roles in Settings › Access.
- Who can do it
- Any member of the workspace
org_invitee_already_member
- What it means
- An invitation adds a person to an organisation; it never changes the role of someone who is a member already. This address is a member’s, so no invitation was created.
- Most frequent cause
- Inviting a member again, often to give them another role — which is a role change, made in the organisation’s member list.
- What to do
- This address already belongs to a member of this organisation: nothing was sent. To change what they can do, change their role in the organisation’s member list.
- Who can do it
- An owner or admin of the workspace · Open the screen
already_an_org_member
- What it means
- You opened an invitation to an organisation you are a member of already. It is used up and changed nothing: your role stays as it is.
- Most frequent cause
- An invitation sent to a member’s address, or a second click on a link already used.
- What to do
- You are already a member of this organisation: the invitation changed nothing, your role stays as it is. An owner or admin changes roles in the organisation’s member list.
- Who can do it
- Any member of the workspace · Open the screen
feature_disabled
- What it means
- The module this route belongs to is not enabled on this deployment.
- Most frequent cause
- The module is off by default and has not been turned on for this deployment.
- What to do
- This module is not enabled on this deployment. On Azoth's service, ask support; on your own deployment, its operator can turn it on.
- Who can do it
- Azoth, or the operator of this deployment · Open the screen
assistant_disabled
- What it means
- The workspace has turned its assistant off: nothing answers its questions — in the app, in a chat app or through the API.
- Most frequent cause
- An owner or admin turned the assistant off in Settings › Organization.
- What to do
- The assistant is turned off for this workspace. An owner or admin can turn it back on in Settings › Organization.
- Who can do it
- An owner or admin of the workspace · Open the screen
origin_not_allowed
- What it means
- A browser sent this request from a page of another site. The MCP endpoints answer an MCP client, or a page of this deployment — never a page of another site, which could otherwise reach them through the browser of a person who opens it.
- Most frequent cause
- An MCP client that runs in a web page on another address, or a page that calls the endpoint from the browser.
- What to do
- This MCP endpoint does not answer a web page of another site. Call it from an MCP client that runs outside the browser, or from this deployment’s own address.
- Who can do it
- The developer of the calling code
capability_off
- What it means
- This feature runs on this deployment and the workspace’s plan includes it, but the workspace has it off — its own choice.
- Most frequent cause
- A feature a workspace turns on itself that nobody turned on yet, or a part of one an owner or admin turned off.
- What to do
- An owner or admin turns it on in Settings › Modules and retention. The change is recorded and sealed.
- Who can do it
- An owner or admin of the workspace · Open the screen
cannot_remove_self
- What it means
- Nobody removes themselves from a workspace here: an owner or admin removes the other members.
- Most frequent cause
- Your own row chosen in the list of members.
- What to do
- Ask another owner or admin of the workspace to remove you.
- Who can do it
- An owner or admin of the workspace · Open the screen
last_owner
- What it means
- A workspace always keeps one owner at least: its last owner can be neither removed nor given another role.
- Most frequent cause
- The member is the only owner of the workspace.
- What to do
- Make another member owner first, then remove this one or change their role.
- Who can do it
- An owner of the workspace · Open the screen
org_admin_required
- What it means
- Only an admin of an organisation adds a workspace to it.
- Most frequent cause
- You are an admin of the workspace, not of its organisation.
- What to do
- Ask an admin of the organisation to add the workspace, or to make you an admin of the organisation.
- Who can do it
- An owner or admin of the workspace · Open the screen
owner_mfa_first
- What it means
- Requiring two-factor authentication of the workspace’s members needs it on your own account first.
- Most frequent cause
- Your account has no second factor yet, or this session was opened without it.
- What to do
- Set up two-factor authentication on your account, sign in with it, then require it for the workspace.
- Who can do it
- An owner or admin of the workspace · Open the screen
invite_daily_limit
- What it means
- Too many invitation e-mails were sent today — to this address, by you or from this workspace — so this one was not sent.
- Most frequent cause
- Many invitations in one day: the limit protects the people invited from unwanted e-mail.
- What to do
- Send the invitation again after the delay the answer gives (retryAfterMs), or tomorrow.
- Who can do it
- An owner or admin of the workspace · Open the screen
sso_required
- What it means
- The organisation of this address signs its members in through single sign-on: a password sign-in, sign-up or reset is refused.
- Most frequent cause
- The address belongs to a domain whose workspace requires single sign-on.
- What to do
- Sign in with single sign-on, from the sign-in page.
- Who can do it
- Any member of the workspace
member_not_found
- What it means
- No member of this workspace has this id.
- Most frequent cause
- A member removed since, or an id from another workspace.
- What to do
- Reload the list of members, then try again.
- Who can do it
- An owner or admin of the workspace · Open the screen
invite_already_accepted
- What it means
- This invitation was accepted already: an invitation is used once.
- Most frequent cause
- A second click on the link, or the invitation accepted from another browser or device.
- What to do
- This invitation was used already. If you accepted it, open the workspace from the sidebar; otherwise ask for a new one.
- Who can do it
- Any member of the workspace
invite_expired
- What it means
- This invitation has expired and can no longer be accepted.
- Most frequent cause
- The link was opened after its validity ended.
- What to do
- This invitation has expired. Ask the person who sent it to send it again.
- Who can do it
- Any member of the workspace
invite_email_mismatch
- What it means
- This invitation is for another e-mail address than the signed-in account’s: only the invited address can accept it.
- Most frequent cause
- Signed in with another account than the one the invitation was sent to.
- What to do
- This invitation was sent to another address. Sign in with the invited address, or ask for an invitation to yours.
- Who can do it
- Any member of the workspace
invite_no_longer_valid
- What it means
- This invitation no longer holds: the person who sent it can no longer grant the role it offers.
- Most frequent cause
- The sender left the workspace or the organisation, or their role was lowered, after sending it.
- What to do
- This invitation no longer holds: whoever sent it can no longer grant this role. Ask an owner or an admin for a new one.
- Who can do it
- Any member of the workspace
invite_already_pending
- What it means
- An invitation already waits for this address, so no second one was created.
- Most frequent cause
- The address was invited before and has not accepted yet.
- What to do
- An invitation already waits for this address. Send it again from the list of invitations, or take it back first.
- Who can do it
- An owner or admin of the workspace · Open the screen
account_email_missing
- What it means
- The signed-in account has no e-mail address, and this action needs one: an invitation is accepted by its address, a test e-mail is sent to it.
- Most frequent cause
- An account created without an e-mail address, through a sign-in that shares none.
- What to do
- Your account has no e-mail address, and this needs one. Sign in with an account that has one, then try again.
- Who can do it
- Any member of the workspace
org_role_protected
- What it means
- In an organisation, nobody changes their own role, and the owner’s role is neither changed nor removed.
- Most frequent cause
- A change of your own role, or of the organisation owner’s.
- What to do
- This role does not change here: another owner or admin changes yours, and the organisation owner keeps theirs.
- Who can do it
- An owner of the workspace · Open the screen
signup_failed
- What it means
- The account could not be created, for a reason the sign-up does not give.
- Most frequent cause
- An address the sign-up refuses, an account in a state that cannot sign up again, or a brief failure.
- What to do
- The account could not be created. Check the address, then try again; if it keeps failing, contact support.
- Who can do it
- Any member of the workspace
only_workspace
- What it means
- This is the only workspace of your account, so it is not deleted on its own.
- Most frequent cause
- Deleting the last workspace the account belongs to — leaving Azoth is the erasure of the account.
- What to do
- This is your only workspace. To leave Azoth, delete your account instead, from your account settings.
- Who can do it
- An owner of the workspace