Manage a user's site access
Site access only applies to the Viewer role. Admins, Operators, and Owners are org-wide by design — changing their site list here has no effect. If a Viewer has no sites assigned, they see nothing; the system fails closed. Changes take effect on the user’s next API call.
Procedure
- Open Admin → Users.
- Open the row menu on the user.
- Click Manage Site Access.
- Tick the sites this user may see; untick the sites they must not see. The dialog replaces the entire assignment list at save time — what you see is what they get.
- Click Save. NovaVMS records a
site.user_access_grantedentry for added sites andsite.user_access_revokedfor removed sites in the audit log.
Common variations
- Assign sites during initial user creation: do it in the same dialog at invite time. See Invite a user.
- Grant everyone a new site at once: no bulk tool in v1. Assign per user, or raise the target user’s role to Operator if they genuinely need org-wide access.
- Temporary site access (e.g., contractor for a week): assign the site now, put a calendar reminder to revoke, and flag the change in the audit log for later review.
If this didn’t work
- If the dialog shows no sites, the org has no sites yet. See Create a site.
- If the user still cannot load the site after you saved, their browser is using a cached permissions response. Ask them to refresh. If the problem persists, see User cannot see a site they were granted.
- If Manage Site Access is not in the row menu, your role is Operator or Viewer.
Related
- Roles and permissions — which roles honour site scoping
- Five-role RBAC — why only Viewer is site-scoped in v1
- Governance vs operations