Authentication & sessions
How members sign in to the dashboard and manage their sessions and organizations, and how API keys authenticate your systems.
Avra authenticates two kinds of callers. People sign in to the dashboard with their corporate email, and their role decides what they can do there. Systems call the API with an API key, which belongs to one workspace. This page covers signing in, sessions, your account, and switching organizations, and explains where API keys fit in.
Sign in
Open the dashboard
Go to app.avra.ai.
Sign in
Sign in with your corporate email.
Start working
The dashboard opens your organization, at the workspace you used last, or at its first workspace if you haven’t picked one yet.
If your account isn’t part of any organization yet, the dashboard shows No organizations available. Ask a Creator in your organization to invite you, then refresh the page. See Team management.
To sign in through your company’s identity provider, contact your Avra representative.
Sessions
Sessions don’t last indefinitely: when a session expires, or after signing out, a member signs in again. To sign out yourself, open the user menu at the bottom of the sidebar and select Log out.
Your account
The user menu’s Account item opens your profile.
Open the user menu
Select your name at the bottom of the sidebar.
Open your account
Select Account.
Review your security settings
Under Security, manage how you sign in, and review or sign out your active sessions.
The same menu switches the dashboard between Light Mode and Dark Mode.
Switch organizations
If you belong to more than one organization, open the switcher at the top of the sidebar and pick one under Switch organization. The same list is in the user menu, under Switch organization. The dashboard opens that organization at the workspace you used last there, and stays in the section you were in, such as Models or Settings → Organization → Billing. If you were on one item, such as a model, it opens the list instead, because that item belongs to the other organization.
Each organization gives you its own role, so what you can do may change when you switch. See Roles & permissions.
API access
API keys authenticate your systems, not people. Each key belongs to one workspace, and the key list shows who created it. Your systems send the key as a bearer token on every request:
curl https://api.avra.ai/v1/api/models \
-H "Authorization: Bearer $AVRA_API_KEY"
A request with a missing or invalid key gets 401 Unauthorized.
Rotating a key can keep the old one working for up to 30 minutes, so you can switch without downtime. You can also rename and delete keys. Keys belong to the workspace, so removing a member doesn’t revoke the keys they created. Rotate or delete any key that should stop working.
See API keys to create, rotate, and delete keys, and to check which workspace a key belongs to.