User Management
User Management
Challenge-specific roles and permissions for the Users page. For shared workflows (create, suspend, search, owner rules), see the shared User Management guide.
Access
- Log in at challenge.veraproof.io.
- Open Users in the main navigation.
- You need Admin or Owner privileges.
User roles
Each user has exactly one role per tenant.
| Role | Typical use | Dashboard | Responder (view) | Responder (submit) | Integrations, SSO, billing, users |
|---|---|---|---|---|---|
| Owner | Tenant creator | Yes | Yes | Yes | Yes |
| Admin | Platform administrators | Yes | Yes | Yes | Yes |
| Analyst | SOC / IR operators | Yes | Yes | Yes | No |
| Viewer | Read-only stakeholders | Yes | Yes (read-only) | No | No |
- Owner — Full access including billing. Cannot be changed or deleted from the UI; contact [email protected] to transfer ownership.
- Admin — Full tenant administration.
- Analyst — Same as Viewer, plus Responder actions (create challenges, revoke sessions). Cannot manage integrations, SSO, billing, or users.
- Viewer — Dashboard and read-only Responder; cannot submit Responder actions or change configuration.
Create a user
- Click Create User.
- Enter Email address and Full name.
- Choose Role: Viewer, Analyst, or Admin.
- Click Create User.
Change a user’s role
- Click Change role in the Actions column.
- Select the new role and click Update role.
- Confirm in the dialog.
You cannot change your own role or the Owner role. Keep at least one Admin before demoting the last admin.
Suspend (recommended when access should end)
Suspend blocks Challenge admin access but keeps audit log links to that user.
- Click Suspend and confirm.
- Click Unsuspend to restore access.
Delete (permanent)
Delete removes the user and:
- Detaches their account from audit logs — Events remain, but no longer show which user performed the action.
- Removes integration configurations they owned.
- Reassigns some tenant settings (IdP, support contact, etc.) to another admin or the owner when possible.
Prefer suspend over delete when audit attribution matters. The delete confirmation in the UI summarizes this impact.
Search and filters
Filter by status (active / suspended) or role (owner, admin, analyst, viewer).
Best practices
- Use Analyst for operators who need Responder but not integration changes.
- Use Viewer for stakeholders who only need dashboard visibility.
- Suspend before delete when audit history must stay attributable.
Related guides
Support
Contact [email protected].