Roles and Permissions
How access works in Rover Nexus: organization roles, fleet roles, and how a member's effective access is decided. For Owners and Admins.
Rover Nexus uses two layers of roles:
- Organization roles control who can manage the organization itself — members, fleets, and access.
- Fleet roles control what a member can do within a fleet — plan, dispatch, command, or just view.
Each member has one organization role and one default fleet role that applies to every fleet your organization can access. You can override the fleet role on individual fleets.
Organization roles
Owner > Admin > Member > Viewer. The order reflects typical authority, but exact powers come from each role's permissions rather than a strict ranking.
| Capability | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| View the organization and its fleets | Yes | Yes | Yes | Yes |
| Invite, edit, and remove members | Yes | Yes | No | No |
| Create and manage fleets | Yes | Yes | No | No |
| Share fleets with other organizations | Yes | Yes | No | No |
| Manage billing | Yes | Yes | No | No |
| Transfer or delete the organization | Yes | No | No | No |
Owners and Admins also have administrative access to every fleet the organization can use, regardless of fleet-role settings (see resolution below).
Fleet roles
Manager > Planner > Operator > Viewer.
| Capability | Manager | Planner | Operator | Viewer |
|---|---|---|---|---|
| View fleet, robots, and telemetry | Yes | Yes | Yes | Yes |
| Plan missions and features (boundaries, routes, zones) | Yes | Yes | No | No |
| Dispatch missions and send robot commands | Yes | Yes | Yes | No |
| Teleoperate robots | Yes | Yes | Yes | No |
| Manage fleet settings and per-fleet permissions | Yes | No | No | No |
For the operator-facing how-tos, see the operator tutorials.
How fleet access is decided
When a member tries to act on a fleet, Rover Nexus resolves their effective fleet role in this order:
- Per-fleet override — if the member has an explicit role on that fleet (set on the Fleet Permissions page), it wins.
- Organization Owner/Admin — Owners and Admins get full fleet access even without an override.
- Default fleet role — otherwise the member's organization-wide default fleet role applies.
- Deny — if none of the above grant access, the action is blocked.
One limit always applies: if the fleet was shared to your organization from another organization, that share's role cap limits the result — even for Owners and Admins. See Fleet Access.
To grant someone more (or less) access on a single fleet, set an override on the Fleet Permissions page rather than changing their organization-wide default. See Set fleet permissions.