User Management¶
This page explains how to create, edit, and delete user accounts. Each person who uses Campus WoL needs their own account with a role that controls what they can see and do.
Role Required: Admin
You need the Admin role to manage user accounts.
Prerequisites¶
- You must be logged in with an Admin account
Creating a User¶
- Navigate to Users in the Administration sidebar
- Click Add User
- Fill in the form fields:
- Username -- A unique identifier for the account
- Password -- An initial password for the user
- Role -- Select Viewer, Operator, or Admin (see role descriptions below)
- Click Save
The new user can log in immediately with the credentials you provided.
User List and Form
Capture the user list showing status badges and the create/edit user form with username, password, and role fields.
Tip
Ask users to change their password after their first login via the Security Center.
Roles¶
Campus WoL uses RBAC (Role-Based Access Control) to determine what each user can do. There are three roles:
| Role | What They Can Do |
|---|---|
| Viewer | Read-only access. Can view the dashboard, Lab Status, and classroom device views. |
| Operator | Everything a Viewer can do, plus wake operations, viewing discovery results, and dismissing discovered devices. |
| Admin | Full access to all features including inventory management, user administration, schedules, audit log, and Security Center. |
For the complete permissions breakdown, see Role-Based Access Control.
Editing a User¶
- Navigate to Users in the Administration sidebar
- Click the user you want to edit
- Update any of the following fields:
- Username
- Password
- Role
- Click Save
Deleting a User¶
- Navigate to Users in the Administration sidebar
- Locate the user you want to remove
- Click the Delete button next to the user
- Confirm the deletion when prompted
Warning
Deleting a user is permanent. The user will no longer be able to log in. Their past actions remain in the audit log.
Limitations¶
The user form in the current UI has three fields only: username, password, and role. The following features are available through the backend API but do not have UI controls:
- Site scoping -- Restricting a user to specific sites. This must be configured via the API.
- Enabling/disabling accounts -- Toggling an account on or off without deleting it. This must be done via the API.
The user list displays an active/disabled status badge next to each user, but this badge is read-only in the UI. You cannot change a user's enabled status from the web interface.
Next Steps¶
- Security Center -- Monitor login activity and manage your own password
- Role-Based Access Control -- See the full permissions matrix