Wiki

Users

Create and manage uVersion accounts: roles, passwords, deactivation, licence seats. Who can do what between super admin and project_admin.

Introduction

The user list: name, email, role, status (active/inactive), last login.

The Users tab of the admin panel is where you create accounts, assign them a role, reset a password, and deactivate or reactivate an account. The list shows each user's name, email, role, status (active / inactive) and last login.

The role assigned here determines what the account can do. For the full breakdown of roles, see Roles & admin panel.

Access and scoping

Super admin: sees every account and has every action available (create, edit, reset, deactivate).
project_admin: can only create accounts. Their list is scoped: they see themselves, the accounts they created, and anyone holding a permission (direct or through a group) on one of their repositories. The Edit / Reset / Deactivate buttons are not shown to them.

Creation is the "safe half": a brand-new account has access to nothing until it is granted a permission. Editing or resetting an existing account touches an access that is already in place, which is why it is reserved for the super admin.

Create a user

The Create User form (Username, Email, Password, Role) with the role selector limited by rank.

Users tab → Create User.
Fill in the fields, then confirm.

Field	Constraint
Username	1 to 64 characters, unique.
Email	Not empty, must contain `@`, unique.
Password	At least 8 characters.
Role	One of the 9 roles. Defaults to `user`.

A username or email that is already taken is rejected (conflict error).

Choosing the role

The selector lists all 9 roles, but you can only assign a role strictly below your own rank. A lead therefore cannot create an admin, and nobody can create an account of a rank equal to or higher than their own. See Ranks and guard.

Edit an account

The account edit window: email, role, active state (the username is fixed).

The Edit button (super admin) lets you change the email, the role and the active state. The username itself is fixed.

Immediate effect Changing an account's role immediately revokes its current sessions: a demotion or a promotion takes effect at once, without waiting for the token to expire naturally (up to 30 days otherwise).

Reset the password

The Reset Password button (super admin) sets a new password (minimum 8 characters). As with a role change, this revokes all existing sessions of the account: the old password and any tokens already issued stop working immediately.

Deactivate, reactivate

uVersion does no hard delete. The delete button is in fact a deactivation: the account goes inactive, its locks are released, and it is signed out. You can reactivate it later.

An active account offers Deactivate.
An inactive account offers Reactivate.
You cannot deactivate yourself.

Keeping the account rather than destroying it preserves the history (who committed what) and lets an employee return without recreating an account.

Licence seats

Creating and reactivating consume a seat Every active account occupies a seat on the server licence. If the quota is reached, creating a new user or reactivating one fails with an explicit error (not silently). Free a seat by deactivating an account, or increase the number of seats from your licences area.

Common pitfalls

Reactivation refused even though the account exists

This is not a bug: the seat quota is full. Deactivate another account first, or add seats.

"I don't see a user in my list"

If you are a project_admin, the list is scoped. An account only appears there if it belongs to you (created by you), if it holds a permission on one of your repositories, or if it is you. Grant it a permission on one of your repositories so it becomes visible.

A role change does not "take"

The change is immediate on the server side, but the affected user is signed out: they must log back in for their client to reflect the new role.