User and project management

The super-admin area provides full control over every user account and every project on the instance — independently of the per-project Team page available to project admins. All routes in this section require the super_admin flag; they are not accessible to regular project admins or members.

Users

The user list at /admin/users shows all accounts with their name, email, super-admin status, and the number of projects they belong to. The list is searchable by name or email and paginated at 20 per page.

Creating a user

Go to /admin/users/create. Required fields:

Field	Description
Name	Display name.
Email	Must be unique. Used for login and password resets.
Password	Set an initial password for the account.
Super admin	Check to grant full super-admin access.
Force password change	Check to require the user to set a new password on first login.

After creation the user can log in immediately. If Force password change is checked, they are redirected to the password-change screen on every request until they set a new password.

Editing a user

The edit page (/admin/users/{user}/edit) shows the same fields plus:

• The current list of projects the user belongs to and their role in each.
• A dropdown to assign the user to an additional project with a chosen role.

Caution

You cannot remove your own super-admin access. If you attempt to uncheck Super admin on your own account, the server rejects the change with an error.

Deleting a user

Click Delete on the edit page. The user is removed from all project memberships and the account is deleted. You cannot delete your own account.

Sending a password reset

On the user edit page, Send password reset dispatches a password-reset email to the user’s address using the active mailer (see Mailer configuration). This is equivalent to the user triggering “Forgot password” themselves.

Assigning users to projects

From the user edit page you can add the user to any project they do not yet belong to:

1. Select the project from the Available projects dropdown.
2. Choose a role: admin or member.
3. Submit the assignment form.

The membership is created with active = true. To change the role on an existing membership, use the role selector next to the project name in the membership list. To remove a membership, click Remove next to the project.

Assignments can also be managed from the project side — see Managing project members below.

Projects

The project list at /admin/projects shows all projects with their name, locked status, and member count. Searchable by name and paginated at 20 per page.

Creating a project

Go to /admin/projects/create. Fields:

Field	Description
Name	Project display name.
Locked	Boolean. When locked, the project is visible in the UI but intended for administrative hold — the exact effect on user operations depends on application logic consuming this flag.

Editing a project

The edit page (/admin/projects/{project}/edit) shows the project fields plus:

• The current member list with name, email, and role.
• A dropdown to assign an additional user (any user not already a member).

Deleting a project

Deleting a project permanently removes it and all its data. This action is not reversible.

Managing project members

From the project edit page you can manage membership directly:

• Add member: select a user from the Assignable users dropdown, choose a role (admin or member), and submit.
• Change role: use the role selector next to an existing member.
• Remove member: click Remove next to the member.

Note

The super-admin ProjectMemberController intentionally has no last-admin guard. If a project ends up with no admins (because you removed the last one), super-admins can reassign an admin role from here to recover the project. The per-project Team page used by regular project admins does enforce a last-admin guard — it prevents a project admin from removing themselves if they are the only admin.

Relationship to the per-project Team page

Each project also has a Team page accessible to project admins at /project/{project}/team. From there, project admins can:

• Invite new members by email (invitation tokens, email delivery).
• Resend or revoke pending invitations.
• Change the role of existing members (with the last-admin guard active).
• Remove members.

The super-admin management area and the per-project Team page operate on the same underlying project_user pivot table; changes made in either place are immediately reflected in the other. The key difference is that super-admins bypass the last-admin guard and can access every project without being members, while project admins can only manage the specific project they hold admin rights for.