Who can do what in the Console, who has been active, and whether the record of it is intact. The fleet API enforces every role on every request; the Console only hides what a role cannot use.
Your role——
Active staff0In the audit trail
Refused actions0None
Audit chain—Checking…
Roles and access
AreaPlatform adminOperationsReleaseSupportTechnicianFinanceMarketing
Fleet, map and logsActActViewViewView——
Alerts and incidentsActActViewViewView——
Missions (cancel)ActActViewViewView——
Assistance (guidance)ActActViewViewView——
Releases and rolloutsActViewActViewView——
Halt and roll backActActAct————
Profiles and mapsViewViewViewViewView——
Devices (register, maintenance)ActActViewViewAct——
Audit trailViewViewViewViewView——
Insights (the views for your team)ViewViewViewViewViewViewView
Everything, including staff roles in the identity serviceRuns the fleet: alerts, incidents, missions, assistanceShips software and configuration to the fleetAnswers partner questions; sees, does not changeKeeps vehicles fit: maintenance, placement, faultsBilling and usage; no fleet accessPartner and public content; no fleet access
Roles are granted in the identity service by a platform admin and reach the Console at the next sign-in; every change is recorded with who, why and before/after.
Activity
| Person | Role | Last action | Actions | Refused | When |
|---|
Loading activity…Every staff action in the Console is recorded here.