Operators are the people who sign in to the console. Manage them on the Users page (Admin only).
Roles
| Role | Can do |
|---|---|
| Viewer | See everything read-only — dashboards, feeds, events. Cannot change settings. |
| Admin | Full control, including changing settings and managing other operators. |
Give Admin only to people who need to change configuration; Viewer is right for anyone who only needs to watch.
Managing operators
- Add an operator with a username, a starting password, and a role.
- Edit an operator's role or enabled state.
- Set password — reset any operator's password.
- Delete an operator.
- Each operator's last sign-in and whether they have two-factor on is shown in the list.
Safety: you can't remove the last admin
PortWall refuses to disable, demote, or delete the last enabled Admin, so you can never lock every administrator out of the console.
If everyone is locked out
You can always recover from the server itself (an elevated session):
C:\portwall\control-plane\portwall-admin.exe reset-password --user admin --generate
This resets (or creates) the admin and prints a new password. The path assumes the default install folder, C:\portwall; if PortWall is installed elsewhere, replace C:\portwall with its folder. See the command-line reference.
Self-service two-factor
Each operator turns their own two-factor on or off from My Security — an admin doesn't hold anyone else's authenticator secret.
Scripts vs people
Operators are people who log in. For scripts and integrations, use API keys rather than a shared operator account, so access can be scoped and revoked precisely.