What each role can do
Everything you can see and do in IFMS comes from your role — a named bundle of rights that an administrator puts on your account. If a menu item or a button described in this manual is missing from your screen, your role does not include it. Nothing is broken.
This page is the full answer to "who can do what". Use it when you are deciding which role to give a colleague, when you are building a custom role, or when somebody says a button has disappeared.
The roles in this table
| Role | Who it is for | What it allows |
|---|---|---|
| System admin | The Kairos platform administrator | Full platform access. Only this role can change platform settings, run permission sync or edit the role catalogue. |
| Operational manager | The Ministry's top person | See everything. Create and manage users. Give any of the three Ministry roles. Manage geozones, alert rules and alert routing. |
| Supervisor | Command-centre shift lead | See everything. Acknowledge and resolve alerts. Manage geozones, alert rules and alert routing. Cannot create or manage users. |
| Operator | Daily monitoring staff | See the map, vehicles and alerts. Acknowledge and resolve alerts. Cannot change anything else. |
Machine roles are hidden from the portal's role lists and pickers.
The Ministry roles cannot change vehicles, platform settings, permission sync or the role catalogue. Operational manager can also acknowledge and resolve alerts.
How to read the tables
| Mark | Meaning |
|---|---|
| Yes | The menu item, screen or button is there and works. |
| No | The item is simply not drawn. IFMS hides what you may not use rather than greying it out, so there is nothing to select and no explanation on screen. |
| Read only | The screen opens and you can look, search and filter, but the buttons that change something are not there. |
Which screens each role can open
| Screen | System admin | Operational manager | Supervisor | Operator |
|---|---|---|---|---|
| Dashboard | Yes | Yes | Yes | Yes |
| Overview | Yes | Yes | Yes | Yes |
| Inbox and the bell | Yes | Yes | Yes | Yes |
| Live map | Yes | Yes | Yes | Yes |
| Fleet and vehicle details | Yes | Yes | Yes | Yes |
| Providers and provider details | Yes | Yes | Yes | Yes |
| Events | Yes | Yes | Yes | Yes |
| Alert Policies | Yes | Yes | Yes | Read only |
| Geofencing | Yes | Yes | Yes | Read only |
| Reports & Analytics | Yes | Yes | Yes | Yes |
| Users | Yes | Yes | No | No |
| Roles & Permissions | Yes | Read only | No | No |
| Alert routing | Yes | Yes | Yes | No |
Overview and Inbox are open to everyone signed in, whatever their role. Every alert IFMS raises reaches every active person's Inbox, including people who cannot open the Events screen.
Live map and Inbox have no sidebar entry. Live map is reached with Open live map on the Overview, and Inbox through the bell's View all. See Find your way around.
What each role can do on each screen
Overview
Everyone who may see vehicles gets the same four counters, the same live map and the Open live map button. There is nothing to change.
Live map
| Action | System admin | Operational manager | Supervisor | Operator |
|---|---|---|---|---|
| Open the map, switch to Table, search, filter | Yes | Yes | Yes | Yes |
| Open a vehicle from a marker or a row | Yes | Yes | Yes | Yes |
Fleet and vehicle details
| Action | System admin | Operational manager | Supervisor | Operator |
|---|---|---|---|---|
| Open both tabs, search, filter, page through, Export CSV, quick view | Yes | Yes | Yes | Yes |
| Open a vehicle's own page | Yes | Yes | Yes | Yes |
Nobody can add, edit or remove a vehicle in the portal. Vehicles arrive on their own, after IFTMS says the vehicle is legal and IFMS accepts a position.
Providers
| Action | System admin | Operational manager | Supervisor | Operator |
|---|---|---|---|---|
| Open the list and a provider's page, search, filter | Yes | Yes | Yes | Yes |
Nobody can change a provider in the portal. Everybody sees the same list, counts, scorecard, recent alerts and vehicles, read only.
The provider's page also shows recent alerts and its vehicles, so somebody who can open Providers but not Events or vehicles sees "No events recorded for this provider." and "This provider has no vehicles in the catalogue." even when there are plenty of both.
Events
| Action | System admin | Operational manager | Supervisor | Operator |
|---|---|---|---|---|
| Open the queue, filter, search, switch to Map | Yes | Yes | Yes | Yes |
| Open an alert's detail panel | Yes | Yes | Yes | Yes |
| Export CSV | Yes | Yes | Yes | Yes |
| Acknowledge an alert | Yes | Yes | Yes | Yes |
| Resolve alert | Yes | Yes | Yes | Yes |
| Tick several alerts and use Acknowledge or Resolve on them together | Yes | Yes | Yes | Yes |
Everybody who can open Events can use Export CSV on the page they are looking at.
Without the right to acknowledge or to close alerts, there are no tick boxes on the rows and no action bar at the bottom of an open alert's panel.
Nobody has an "escalate" button or a "reopen" button. Escalation happens by itself — see Response times and escalation.
Alert Policies
| Action | System admin | Operational manager | Supervisor | Operator |
|---|---|---|---|---|
| Open the list, search, filter | Yes | Yes | Yes | Yes |
| Select a row to open the policy, read only | Yes | Yes | Yes | Yes |
| New policy and the wizard | Yes | Yes | Yes | No |
| Edit on an open policy | Yes | Yes | Yes | No |
| Active switch on a row | Yes | Yes | Yes | No |
| Delete a policy (the waste-basket button) | Yes | Yes | Yes | No |
| Add, remove or import the policy's target vehicles | Yes | Yes | Yes | No |
For the read-only roles the Active switch is still drawn on each row, but greyed out; hovering it reads "You can't change this policy's state".
Geofencing
| Action | System admin | Operational manager | Supervisor | Operator |
|---|---|---|---|---|
| Open the screen, search, select a zone, hide and show zones, Live vehicles, look at Show deleted | Yes | Yes | Yes | Yes |
| Add geozone and the drawing map | Yes | Yes | Yes | No |
| Edit geozone and Groups… in a row's ⋯ menu | Yes | Yes | Yes | No |
| Delete geozone in a row's ⋯ menu, and Restore under Show deleted | Yes | Yes | Yes | No |
| The Active switch on a row | Yes | Yes | Yes | No |
| Import CSV | Yes | Yes | Yes | No |
| New group | Yes | Yes | Yes | No |
| Edit group (rename, recolour) and Delete group | Yes | Yes | Yes | No |
Where a role holds none of the row actions, the ⋯ button is not shown at all. Delete group sits inside Edit group, so a custom role needs both the right to edit groups and the right to delete them to reach it. A custom role that cannot read alert policies still gets a refusal when it tries to delete a zone a policy uses, but as a red message instead of the Can't delete this geozone window.
Reports
Reports has a right of its own, Read on Reports, which all four roles have. Everybody who has it can open every report and export it to Excel, CSV or PDF; there is no separate export right. Anybody else does not see Reports in the menu, and gets Access denied at its address.
Dashboard
All four roles can open the Dashboard and arrange their own copy. A tile whose data the role cannot see reads "Your role can't see this tile."
Users
| Action | System admin | Operational manager | Supervisor / Operator |
|---|---|---|---|
| Open the list, search, filter | Yes | Yes | No |
| Add user | Yes | Yes | No |
| Edit a user's details and roles | Yes | Yes | No |
| Deactivate a user | Yes | Yes | No |
| Reactivate a user | Yes | Yes | No |
| Roles you can give | All person roles and active custom roles | Operational manager, Supervisor, Operator | — |
| Deactivate limits | Never yourself, and never the last active System admin | The same | — |
For the full rules, see Users — Which roles you can give.
Roles & Permissions
| Action | System admin | Operational manager / Supervisor | Operator |
|---|---|---|---|
| Open the list and search | Yes | Yes | No |
| Select a role's row to view it and everything it grants | Yes | Yes | No |
| Add role | Yes | No | No |
| Edit a custom role | Yes | No | No |
| Activate / Deactivate a custom role | Yes | No | No |
| Delete a custom role | Yes | No | No |
System roles can only ever be viewed, by anybody, and have no three-dot menu. For a System admin, selecting a custom role that is switched on opens it for editing instead.
Alert routing
| Action | System admin | Operational manager / Supervisor | Operator |
|---|---|---|---|
| Open the list and search | Yes | Yes | No |
| Add rule | Yes | Yes | No |
| Edit a rule | Yes | Yes | No |
| The Enabled switch (asks you to confirm) | Yes | Yes | No |
| Delete a rule | Yes | Yes | No |
The roles in plain words
Operational manager leads the Ministry team. This person sets up users, geozones, alert rules and alert routing. They can give any of the three Ministry roles. They cannot change vehicles or the platform setup.
Supervisor leads the command-centre shift. This person handles alerts and manages geozones, alert rules and alert routing. They cannot manage users.
Operator monitors the map, vehicles and alerts each day. This person can acknowledge and resolve alerts. They cannot change anything else.
System admin is the Kairos platform administrator. This person manages the platform, the role catalogue and vehicle records.
Things worth knowing before you hand out a role
When you sign in, the sidebar briefly shows every item and then shortens to the ones your role allows. That flicker is normal. If the menu stays short when it should not, reload the page — see Troubleshooting.
When an administrator changes your roles, the portal can take up to about five minutes to notice, and a page you already have open keeps the old rights until you reload it. Sign out and back in if you need the change immediately.
Some screens use a second right they do not check at the door. A custom role that may open Users or Alert routing also needs the right to read roles, or the Role filter and the Target role list stay empty. Alert routing also needs the right to read providers for its provider list, and a role that may edit roles needs the right to read the list of permissions. Nothing on screen says what is missing. The person roles that use these screens already include these; only custom roles are affected.
A three-dot menu shows only the items your role allows. Where it allows none, the button is not drawn at all.
Deactivate on the Users screen switches off the person's sign-in and signs them out everywhere. They cannot sign back in until somebody reactivates them.
Related pages
- Who uses IFMS — the same roles described as jobs rather than tables.
- Roles and permissions — how to build a custom role.
- Users — giving roles to people.
- Troubleshooting — what to do about Access denied and missing menu items.