Skip to Content
Baseera Docs

Team and roles

Invite teammates, choose their roles, set up two-factor sign-in and read the audit log.

Everyone in an organization signs in with their own account. You decide what each person can change with a role, protect sensitive actions with two-factor sign-in, and review every change in the audit log.

Roles

CapabilityOwnerAdminDeveloperViewer
Read sessions, traces, usage, overviewYesYesYesYes
Edit an agent's draft, theme and knowledgeYesYesYesNo
Write and run tests, compare setups, label answersYesYesYesNo
Create publishable keysYesYesYesNo
Publish, roll back, choose required testsYesYesNoNo
Provider keys, secret keys, webhooksYesYesNoNo
Spending limits, purge a tenant, read the audit logYesYesNoNo
Publish past failing testsYesNoNoNo
Invite and manage peopleAll rolesDevelopers and viewersNoNo
Require two-factor for owners and adminsYesNoNoNo

In the dashboard the short descriptions are: Owner, "Full control, including keys, secrets and the team." Admin, "Manages keys, secrets, developers and viewers." Developer, "Builds and tests agents. No keys or secrets." Viewer, "Reads sessions and traces only."

Roles are enforced by the database, not only by what the page shows. A button you cannot use is hidden, and a request that tries anyway is refused.

Invite a teammate

Open Members from the account menu, or Settings.

Under Invite a teammate enter the Email address and choose a Role.

Press Send invitation. You see "Invitation queued. The email goes out in a moment and the link works for 7 days."

The person opens the link, signs in or creates an account with that same email address, and presses Accept the invitation. Opening the link never joins by itself. If the page says "This invitation link isn't valid", it may have expired, been used, been revoked, or been sent to a different email address.

Under Pending invitations you can Resend (the earlier link stops working once the new one is sent) or Revoke. An organization can have up to 100 members and pending invitations together, with at most 50 pending.

Change a role or remove someone

Use the role menu next to a person in People, or Remove. Owners can change any member except themselves. Admins can move developers and viewers between those two roles. Nobody changes their own role, so an owner steps down by having another owner demote them. Anyone can Leave.

An organization always needs one owner: "Make someone else an owner first."

Removing someone ends their access at once. Keys and agents they created stay.

Two-factor sign-in

Anyone can add an authenticator app (TOTP) to their account. Owners and admins of an organization that requires it must.

Open Security from the account menu and press Set up authenticator.

Scan the QR code, or type the setup key into your authenticator app.

Enter the 6-digit code and press Turn on two-factor.

Copy your recovery codes. They are shown once. Each works once. Press I saved my recovery codes.

After your password you then enter a 6-digit code. Creating keys, adding provider keys and changing webhook secrets are refused from a session that has not passed this step.

Make new recovery codes replaces the old set. If you lose your authenticator, choose I lost my authenticator at sign-in and enter a recovery code. That removes your authenticator and all other recovery codes, and signs you out everywhere else, so you can set up a new one. Five wrong recovery codes in 15 minutes lock recovery for 15 minutes.

Require it for owners and admins

An owner can switch on Two-factor for owners and admins under Security (and from Settings). Every owner and admin must then set up two-factor, and granting someone owner or admin needs your own code in that session. You must be signed in with your own code, and have an authenticator, to turn it on.

Read the audit log

Open Audit log. Owners and admins see who changed what in the organization, newest first. Filter by Event (Organization, Agents, Agent keys, Provider keys, Webhooks, Knowledge, Test runs, Two-factor sign-in, Spending limits, Live session judging, Human review, Team) and by Person.

Each entry shows When, Who, Event, Done to and Details. Entries can be added but never edited or removed, even by owners. They keep names of fields, versions and the last four characters of keys, and never a key, a prompt or its text. Changes made by Baseera itself show as "Baseera (automatic)", and by a server key as "Server API key".

What can go wrong

MessageCause and fix
"You can't do that with your role."See the table above.
"That person is already a member." / "That address already has a pending invitation."Find them in People or Pending invitations.
"This organization is at its limit of members or pending invitations."Revoke old invitations or remove members.
"Too many invitations. Try again later."Invitations are rate limited per person and per organization.
"Sign in with your two-factor code first. Sign out and back in, then try again."Your session has not passed the code step.
"That code didn't work."Check the 6-digit code and your phone's clock.
"Too many attempts. Wait a minute and try again."Wait.
"Only owners and admins can read the audit log."Ask an owner or admin.

Next steps

On this page