Profile

Introduction

What is the Profile screen?

The Profile screen is your personal corner of Testver. Where Settings governs the whole project and applies to everyone who opens it, Profile is just yours: your display name, your password, the devices you are currently signed in on, a log of your own recent actions, and your personal theme preference.

Nothing you change here affects other users or the project’s data. Editing your display name changes only how your name appears; changing your password changes only your login; revoking a session signs out only your devices. Think of Profile as the account-settings page you would expect in any web app — small, safe, and entirely self-service.

Note

In one sentence: Profile is your private account page — update your name, change your password, see and revoke your logins, review your own activity, and pick your theme.

Who this guide is for

• Every Testver user, regardless of role — Profile is available to Admin, Tester, and Viewer alike.
• Anyone who just created an account and wants to set a friendly display name and a personal password.
• Security-conscious users who want to review where they are logged in and sign out a lost or shared device.
• People investigating their own account — “did I really delete that case?” — using the Recent Activity list.

Key terms

These terms appear throughout the Profile screen and this guide.

Term	What it means
Username	Your unique handle, chosen at account creation. Used to sign in and shown throughout Testver. It cannot be changed after creation.
Display name	An optional friendly name shown alongside (or instead of) your username. Editable here at any time.
Role	Your permission level — Admin, Tester, or Viewer. Set by an admin on the Users screen; shown here read-only.
Session	One active login. Each browser or device you sign in from creates its own session, identified by its user-agent and IP.
Current session	The session you are using to view this page right now. It is badged and cannot be revoked from itself (sign out instead).
Activity	A record of a consequential action you took — a login, an edit, a run, an AI call. The personal subset of the audit trail.
Theme	Light or dark appearance. Saved against your account, so it follows you to every device you sign in from.

How the data is scoped

Everything on this screen is scoped to the signed-in account and stored server-side:

• Profile fields (display name, theme) are saved against your user record and apply on every device the moment you sign in.
• Sessions are live server records. Revoking one invalidates the token immediately, so the affected device is signed out on its very next request — not at some later expiry.
• Recent Activity is a read-only slice of the central audit log, filtered to just your actions. The full, all-users view lives in Audit Log and is admin-only.

Caution

Profile shows your data only. It is never a window into anyone else’s account. Admins manage other people from the Users screen, not from here.

Getting Started

Opening Profile

1. Sign in to Testver as usual.
2. Click your avatar / name in the top-right of the header to open the user menu.
3. Choose Profile from the dropdown.
4. The page opens as a single vertically-scrolling column.

Tip

Profile is always one click away from anywhere in the app — it lives in the header user menu, not behind a project or a specific screen.

The screen layout

Profile is a single-column page with five stacked sections, top to bottom:

1. Profile Overview — your username, email, role, and the editable display name.
2. Change Password — a short form to set a new password.
3. Active Sessions — every device you are currently signed in on.
4. Recent Activity — a chronological list of your own recent actions.
5. Preferences — your theme and other personal settings.

At a glance

• Read Profile Overview first to confirm who you are signed in as and with what role.
• Glance at Active Sessions to make sure every listed device is one you recognise.
• Skim Recent Activity to confirm the last few actions match what you remember doing.
• Set your theme once and forget it — it follows you everywhere.

Profile Overview

The first section shows your account’s core identity:

• Username — your unique login handle. Read-only; it is fixed at account creation.
• Email — shown when an email was provided during account creation. Used for identification and (where configured) notifications.
• Role — your current permission level: Admin, Tester, or Viewer. Read-only here; only an admin can change it on the Users screen.
• Display name — the one editable field. It is what other users see next to your username throughout Testver — on activity feeds, defect reporters, commit authors, and more.

Editing your display name

1. Click into the Display name field.
2. Type the name you want others to see.
3. Save inline — the change takes effect immediately and is reflected wherever your name appears.

Tip

Pick a recognisable display name (e.g. “Asha R.”) rather than leaving it blank. It makes activity feeds, defect ownership, and Git commit authorship far easier for your teammates to read.

Change Password

A simple three-field form to rotate your own password without involving an admin.

• Current password — required, to prove it is really you.
• New password — must satisfy the password policy in force for your instance.
• Confirm new password — must match the new password exactly. On save, your password is updated immediately. Your current session stays signed in, but any future sign-in must use the new password.

Caution

Changing your password does not, by itself, sign out your other devices. If you are rotating the password because you suspect it leaked, follow up with Revoke all other sessions (below) so any other login is killed at once.

Active Sessions

This section lists every login your account currently has open — one entry per browser or device. It is the single most useful security tool on the page.

What each entry shows

• Device / browser / OS — detected from the session’s user-agent, e.g. “Chrome on Windows”.
• IP address — the address the session was created from.
• Created — when the session began.
• Last activity — when the session was last used.
• Current badge — marks the session you are using to view this page right now.

Revoking a single session

Each session row has a Revoke action. Revoking invalidates that session immediately: the user on that device is signed out on their next request and must sign in again. Use it when you spot a login you do not recognise, or to clear out an old device you no longer use.

Revoke all other sessions

A single button at the top of the section signs out every session except the one you are using now. Reach for it when:

• You suspect your account is compromised.
• You just changed your password and want a clean slate everywhere.
• You signed in on a shared or public machine and forgot to sign out.

Caution

There is a confirmation, but no undo. Every other device — including your own phone or laptop — will need to sign in again afterwards. That is exactly the point, but be sure before you confirm.

Recent Activity

A chronological list of your own recent actions in Testver — logins, edits, runs, AI calls, and more. Each entry shows the action, the resource it targeted, the outcome, and a relative timestamp (“5 minutes ago”).

It is built for fast, personal triage:

• Verifying “did I really delete that case?” before blaming the system.
• Spotting unauthorised access — if an action appears that you do not remember performing, that is a red flag worth investigating alongside Active Sessions.

Note

Recent Activity is your personal slice. The full historical view — every user, with filtering, expansion, and export — lives in Audit Log, which is available to admins.

Preferences

Theme

Choose Light or Dark. The same toggle is mirrored in the top-right header, so you can switch from anywhere. Your choice is saved per user, so it follows you to every device you sign in from rather than being tied to one browser.

Common workflows

First-day account setup

1. Open Profile from the header user menu.
2. Set a friendly display name so teammates recognise you.
3. Use Change Password to replace the initial password your admin gave you.
4. Pick your theme.
5. Glance at Active Sessions to confirm only your own device is listed.

”I think my account was accessed”

1. Open Active Sessions and look for any device, browser, or IP you do not recognise.
2. Click Revoke on anything suspicious — or use Revoke all other sessions to be safe.
3. Use Change Password to set a new password.
4. Scan Recent Activity for actions you did not perform, and report them to an admin.

Switching machines cleanly

1. Sign in on the new machine.
2. Open Profile ▸ Active Sessions there.
3. Use Revoke all other sessions to sign out the old machine remotely.

Tips & best practices

• Revoke all other sessions is the right reflex when changing your password. There is a confirmation but no undo — any device that was logged in will need to sign in again.
• Recent Activity is the fastest triage for “what happened on my account?” — much quicker than asking an admin to filter the Audit Log for you.
• Keep your display name set and recognisable — it propagates to activity feeds, defect ownership, and Git authorship.
• Review your sessions occasionally, especially after travelling or using a borrowed device.

Troubleshooting

Symptom	Likely cause & fix
New password is rejected on save	It does not meet the password policy, or the confirmation does not match. Re-enter both fields carefully.
”Current password is incorrect”	The current-password field must hold your existing password, not the new one. Re-type it.
A session I do not recognise appears	Revoke it immediately, then change your password and tell an admin. Cross-check Recent Activity for unfamiliar actions.
My other devices are still logged in after a password change	Password changes do not auto-revoke sessions. Use Revoke all other sessions to sign them out.
Theme keeps resetting	Confirm you are signed in — the preference is saved against your account, not the browser. A signed-out (guest) view falls back to the default.
I cannot change my username	Usernames are immutable by design. Ask an admin to create a new account if a different handle is essential.

Frequently asked questions

Can I change my own role here?

No. Role is read-only on Profile. Only an Admin can change roles, and they do it from the Users screen.

Will changing my password log me out?

Not your current session. Future sign-ins use the new password. Use Revoke all other sessions if you also want to sign out other devices.

Can an admin see what I typed in the AI Assistant from here?

No. Chat and recording content are personal and user-scoped. Neither Profile nor the Audit Log exposes conversation content — only the fact that a call happened.

Why does a session show an unfamiliar city or IP?

IP-to-location is approximate and can reflect your ISP or VPN exit. If the device and browser look right, it is usually benign — but when in doubt, revoke and re-sign-in.

Related screens

• Settings — project-level configuration (the counterpart to this personal page).
• Audit Log — the full, all-users audit trail (admin only); Recent Activity here is your personal subset.
• Users — where admins manage accounts, roles, and sessions for everyone.
• Local Browser Connector — manage your personal local-browser tokens.

Related screens

• Settings — project-level configuration (the counterpart to this personal page).
• Audit Log — the full, all-users audit trail (admin only); Recent Activity here is your personal subset.
• Users — where admins manage accounts, roles, and sessions for everyone.
• Local Browser Connector — manage your personal local-browser tokens.

Related

• Settings — project-level configuration.
• Audit Log — full audit trail (admin only).
• Local Browser Connector — manage your local-browser tokens.