Users

Introduction

What is the Users screen?

The Users screen is the control room for who can get into your Testver instance and what they are allowed to do once inside. From a single table you can add new users, change roles, reset passwords, enable or disable accounts, sign people out of every device, and delete accounts entirely.

It is the practical front end to Testver’s role-based access control. Every other screen quietly checks a user’s role before showing buttons or accepting changes; this is where those roles are assigned.

Caution

The Users screen is visible only to users with the Admin role. Testers and Viewers do not see it in their navigation and cannot reach it directly.

Note

In one sentence: Users is the admin-only roster where you grant, change, and revoke access to Testver.

Who this guide is for

• Admins responsible for onboarding teammates, assigning roles, and offboarding people who leave.
• Team leads deciding who should be a Tester versus a read-only Viewer.
• Anyone doing incident response who needs to disable an account or revoke sessions quickly.

Key terms

Term	What it means
User	An account that can sign in to Testver, identified by a unique username.
Role	The permission level attached to a user — Admin, Tester, or Viewer. Determines what the user can see and do.
Status	Whether an account is Active (can sign in) or Disabled (blocked from signing in).
Session	One active login on one device. An account can have several. Revoking sessions forces re-authentication.
Display name	Optional friendly name shown alongside the username throughout the app.
Initial password	The first password set when an account is created. The user can change it later from their own Profile.

How access control works

Testver ships with three built-in roles arranged from most to least privileged: Admin, Tester, Viewer. A user has exactly one role. The role is checked server-side on every sensitive action, so it is a real security boundary, not just a UI hint.

Caution

Even admins do not get a magic window into other users’ personal data. Chat history, recording history, and AI-generated case bodies remain user-scoped and are never exposed through this screen.

Getting Started

Opening the Users screen

1. Sign in as a user with the Admin role.
2. Open the Admin section in the navigation (or the header user menu) and choose Users.
3. The roster loads as a single table with a toolbar above it.

Tip

If you cannot see the Users entry at all, your account is not an Admin. Ask an existing admin to elevate you — or, if you are the only admin and locked out, recreate access from the server.

The screen layout

Users is a single-screen table view. A toolbar sits above the table (with the + New User button); every other operation happens against a row in the table itself.

Roles in depth

Choosing the right role for each teammate is the most important decision on this screen. Here is exactly what each role can and cannot do.

Admin

Full access. An Admin can do everything a Tester can, plus:

• User management — this screen.
• Audit Log — read the full, all-users audit trail.
• All-user Browser Sessions — view and close any browser session, including those owned by test runs.
• Settings (write) — LLM provider keys, org-level connector configuration, and other instance settings.

Caution

Admins still cannot read other users’ chat history or recording history — those are personal data and remain user-scoped no matter the role.

Tester

The day-to-day testing role — the right default for most teammates. A Tester can:

• Read everything in the project.

• Create, edit, and run test cases, plans, and executions.

• Use AI Assistant, AI Record, and AI Test Gen.

• Edit project files in Project Explorer and commit via Git.

• Run tests via the Runner and Schedules.

• File and edit Defects.

• Build Reports.

• Manage their own Profile and Local Browser Connector tokens. A Tester cannot:

• Manage users.

• Read the Audit Log.

• Change org-level Settings.

Viewer

Read-only access, ideal for stakeholders who want visibility without the ability to change anything. A Viewer can:

• View test cases, plans, results, defects, and dashboards. A Viewer cannot run, edit, create, or use any AI feature that consumes tokens.

Tip

Use Viewer for managers and external stakeholders who need a window into quality without the risk of accidental edits or token spend.

The user table

Each row in the table represents one account and shows:

• Username — the unique handle used for login and display.
• Display name — optional; shown alongside the username.
• Email — optional contact address.
• Role — Admin, Tester, or Viewer.
• Status — Active or Disabled.
• Created — when the account was created.

Creating a user

Click + New User in the toolbar to open the creation modal.

Field	Required?	Notes
Username	Required	Must be unique. This becomes the login handle and cannot be changed later.
Display name	Optional	Friendly name shown next to the username.
Email	Optional	Contact address; used for identification and any configured notifications.
Role	Required	A single pick — Admin, Tester, or Viewer.
Initial password	Required	The first password. Share it securely; the user can change it from their Profile.

1. Fill in the fields above.
2. Pick the appropriate role (default to Tester unless there is a reason not to).
3. Click Save — the new user appears in the table immediately and can sign in right away.

Tip

Send the username and initial password through a secure channel, and ask the user to change the password from Profile ▸ Change Password on first sign-in.

Per-row actions

Open the actions menu on any row to manage that account.

Action	What it does
Edit	Open a modal to change display name, email, role, and the active toggle. The username is immutable and cannot be edited.
Reset password	Set a new password for the user — useful when someone is locked out and cannot reset it themselves.
Revoke sessions	Sign the user out of every device immediately. Their next request requires a fresh sign-in.
Toggle active	Disable or enable the account. Disabled accounts cannot sign in; existing sessions persist until they expire (pair with Revoke sessions for an instant lockout).
Delete	Permanently remove the account. Requires confirmation and is irreversible.

Caution

Disabling an account does not kill live sessions on its own — it only blocks future sign-ins. For an immediate lockout, use Revoke sessions and Toggle active together.

Common workflows

Onboarding a new teammate

1. Click + New User.
2. Enter a username, optional display name and email.
3. Choose Tester (the usual default).
4. Set an initial password and click Save.
5. Share the credentials securely and ask them to change the password on first sign-in.

Offboarding someone who left

1. Find their row and open the actions menu.
2. Click Revoke sessions — they are signed out everywhere instantly.
3. Click Toggle active to disable the account so they cannot sign back in.
4. Keep the account disabled (don’t delete) if there’s any chance they return; delete only once you’re certain.

Promoting a Tester to Admin

1. Open the user’s Edit modal.
2. Change Role to Admin.
3. Save. Keep the admin group small — one or two people is plenty for most teams.

Tips & best practices

• Default to the Tester role for most teammates. Reserve Admin for one or two trusted people, and use Viewer for stakeholders who only need to look.
• Revoke sessions + disable when offboarding. The user is signed out instantly and cannot return. Disabling is reversible; deletion is not, so prefer disabling unless you are certain.
• Review the roster periodically — remove or disable accounts that are no longer needed to keep your attack surface small.
• Cross-check changes in the Audit Log. Every user-management action is recorded there, which is invaluable during security reviews.

Troubleshooting

Symptom	Likely cause & fix
I can’t see the Users screen	Your account is not an Admin. Ask an existing admin to change your role.
”Username already exists” on create	Usernames must be unique. Pick a different handle — usernames cannot be reused while the account exists.
A disabled user is still active	Disabling blocks new sign-ins but not live sessions. Also click Revoke sessions to sign them out immediately.
I can’t change a username	Usernames are immutable. Create a new account if a different handle is essential, then disable the old one.
I deleted a user by mistake	Deletion is irreversible. Recreate the account; its prior personal data (sessions, chat) does not come back.
A new user can’t sign in	Confirm the account is Active and that you shared the exact initial password. Reset password if in doubt.

Frequently asked questions

Can a user have more than one role?

No. Each account has exactly one role. Change it via the Edit modal when responsibilities change.

Can admins read other users’ AI chats or recordings?

No. Those are personal and user-scoped. Admins manage accounts, roles, and sessions — not personal content.

What happens to a user’s data when I delete them?

The account and its sessions are removed. Deletion is irreversible, so prefer disabling unless you are certain the account is gone for good.

Is every change here logged?

Yes. User creation, role changes, and enable/disable/delete actions are recorded in the Audit Log for later review.

Related screens

• Audit Log — the record of what users did (and what you changed here).
• Profile — the per-user counterpart, where each person manages their own account.
• Settings — org-level configuration that admins control.
• Local Browser Connector — per-user token management.

Related screens

• Audit Log — the record of what users did (and what you changed here).
• Profile — the per-user counterpart, where each person manages their own account.
• Settings — org-level configuration that admins control.
• Local Browser Connector — per-user token management.

Related

• Audit Log — what users did.
• Profile — per-user view.
• Local Browser Connector — per-user token management.