You need the Owner or Admin role on the project to change users. Other members see the screen read-only, and disabled controls explain why on hover. The Activity tab is limited to Owners, Admins, and organization admins.
The Users tab
The Users tab lists the users of the current environment. Search by name or email, sort the list, and filter by status.User statuses
The status filter also offers Pending activation, for users who were invited or created but haven’t activated their account.
Create users
Click Create user and enter the person’s email, name, and Roles. You can also create a new role from the dialog with New role. Then choose a First credential:
With a temporary password or a password you set, the person must change the password at their first sign-in.
Users created with an activation link or a temporary password appear in Pending activation until they set their own password. From the row menu there you can Resend activation, Copy activation link, Resend temporary password, or Revoke access.
Manage passwords
The row menu of a user with a password also offers:Invitations
Use Invite user to invite someone by email. The account is created when they accept. Enter the email and Roles, and Archie sends the invitation. The Invitations tab lists every invitation. Filter by status, then use these actions on a row:
Select several invitations to Resend or Revoke them in one step.
Invitations by email are controlled in the Settings tab with the Invitations by e-mail switch. Admins can always create users directly. If you turn invitations off, every pending invitation link stops working permanently, and turning them back on doesn’t revive them. Activation links for users you created are not affected. The Settings tab also links to Edit account e-mails →, where you word the invitation email. See Email templates.
Require 2FA for a user
Under Two-factor authentication in a user’s row menu, set the 2FA policy for that user:
You can add an optional reason. The change applies from the user’s next sign-in. For the project-wide policy, grace period, and how users enrol, see Multi-factor authentication.
Disable and enable users
Use Disable for investigations and account suspensions. To remove a disabled user from an active session immediately, Sign out everywhere after disabling.
Resend verification
If a user didn’t receive (or lost) the verification code, choose Resend verification in the row menu. A new 6-digit code is generated with a fresh 1-hour expiry. The previous code is invalidated.Terminate sessions
With Sign out everywhere, the user’s access token stays valid until natural expiry (15 minutes by default), but they can’t refresh. They return to the sign-in screen on the next refresh attempt. For an instant kick-out, combine it with Disable. The token blacklist on every request rejects the access token even before it expires.
Use Terminate all sessions after a security incident, such as a leaked signing key or a database breach, when every user must sign in again. Its blast radius is environment-scoped: terminating sessions in
master doesn’t touch staging.
Activity
The Activity tab is the authentication log for the environment. It records every sign-in, 2FA event, and admin action, including who did it.
Filter the log by Type, Outcome, Date, and user. The type groups are Sign-in, Password, 2FA, User management, Invitations, Sessions, and E-mails. Date ranges run from Last 24 hours to Last 90 days, or Any time. Click an event to open its details.
The log covers:
- Sign-ins: successful and failed sign-ins, sign-outs, locked accounts, social sign-ins, and magic links.
- Passwords: password changes and recovery requests, and temporary passwords issued or revealed.
- 2FA: enrolment, verification, recovery codes, and admin resets and policy changes.
- User management: users created or deleted by an admin, role and status changes, and activation links revealed.
- Invitations: invitations sent, resent, edited, accepted, and revoked.
- Sessions: sessions ended and all sessions terminated.
- Emails: emails sent or failed, and test emails.
Per-environment scope
User management is scoped to the current environment. A user registered instaging is a different record from a user with the same email registered in master. Switching the environment selector changes the entire users table.
This separation is the point — it means dev and staging traffic doesn’t pollute production user records, and a developer logging in to staging doesn’t burn rate-limit budget in master.
GraphQL admin API
Every dashboard action has a corresponding GraphQL operation. Useful for scripted user-management — bulk-revoke after an incident, sync user state from another system, or build your own admin UI.
The reference page documents the first five. The input fields of the others are not covered there yet.
Permissions
Admin operations require admin-level authentication — typically a user with theadmin role or an API key attached to that role. Define the role in Role-Based Access and grant it the system permissions needed for the admin mutations.
FAQ
What's the difference between Disable and Sign out everywhere?
What's the difference between Disable and Sign out everywhere?
Disable prevents future sign-ins. Sign out everywhere terminates the current session by invalidating the refresh token. Combine them for an instant kick-out: Disable stops new sign-ins; Sign out everywhere cuts the live session.
A user is locked but the lock duration is too long — how do I unlock them?
A user is locked but the lock duration is too long — how do I unlock them?
Disable then enable the user. That clears the lockout state. Alternatively, run a successful password reset — the recovery flow clears the lockout on success.
Does Terminate all sessions affect API keys?
Does Terminate all sessions affect API keys?
No — API keys are managed separately under Backend → Settings → API Keys and aren’t touched by user-session operations. Rotate compromised API keys there.
Can I delete a user instead of disabling them?
Can I delete a user instead of disabling them?
Use the Data Model’s
users table or _auth_credentials to delete the row. Hard deletion removes the credential entirely; disabling preserves history. Most teams disable rather than delete to keep an audit trail.How do I bulk-export the user list?
How do I bulk-export the user list?
Use
adminListCredentials over the GraphQL API, or query the _auth_credentials table directly via the Data Viewer or SQL Playground.