Users & Roles
The Users section is an admin-only area for managing Runner user accounts. Here you can create users, assign global roles, manually confirm accounts, impersonate users for debugging, and remove accounts that are no longer needed.
Global roles
Every Runner user has one of two global roles.
User — the default role. Users can create projects and access any project they are a member of. They can manage their own account (change their email address) but cannot access admin functions. See Members & Roles for how project-level access works.
Admin — full system access. Admins can manage executors, configure global settings, and manage all user accounts, including creating and deleting users, changing roles, and impersonating users. An Admin role does not automatically grant access to all projects — admins still need to be added as project members like anyone else.
Your users
The user list shows all registered accounts. Each row displays the user's Gravatar and email address, when they registered, and when they last logged in. Admins and unconfirmed users are marked with a badge next to their email.
You can sort by email, registration date, or last login date, and search by email.
Each user has up to three actions in the list:
- Confirm — manually confirm an unconfirmed account. Only visible when the account has not yet been confirmed.
- Impersonate — open a session as this user in a new tab. See Impersonating a user.
- Delete — see Deleting a user.
Adding a user
Click Add User, enter an email address, select a role, and click Save. No password is set during creation — the user should use the Forgot Password flow on the login page to set their password before their first login.
New accounts are created in an unconfirmed state. The user becomes fully active once they confirm their email address via the confirmation link sent on registration, or once an admin confirms them manually.
Editing a user
Click any user row to open their detail page. Two fields are editable:
Email Address — the user's login email and the address used for notifications and avatars. Admins can change any user's email; regular users can change their own.
Role — the global role assigned to this user. Requires Admin. You cannot change your own role — ask another admin to do it.
Confirming a user
When a user registers, Runner sends a confirmation email with a link to activate their account. Until confirmed, the user has no access to any part of the application.
If a user did not receive the confirmation email or needs to be activated immediately, an admin can confirm the account manually by clicking the Confirm button on the list row or the user detail page.
Impersonating a user
Impersonation lets an admin open a session that behaves exactly as if they were logged in as another user. This is useful for diagnosing access problems or verifying that a user's project permissions are set up correctly. The impersonated session opens in a new browser tab so your own session is unaffected.
Impersonation is only available to Admins and only for confirmed user accounts. You cannot impersonate yourself, and you cannot start an impersonated session while already impersonating someone.
Deleting a user
Deleting a user removes their account and revokes all their access tokens. If SMTP is configured in Settings, the user receives a notification email when their account is deleted.
A user can only be deleted if they have no activity in the system — no projects, environments, files, schedules, runs, or project memberships where they appear as creator, last editor, or member. In practice this means that any user who has actively used Runner cannot be deleted. If you need to revoke access without deleting, remove them from all projects via Members & Roles instead.
You cannot delete your own account.