Roles and permissions
Give each member the right standard role (Admin, Operator, Viewer), create custom roles limited to a selection of tags, and personalize your navigation.
Roles and permissions
In Drexo, a member's access is decided on two axes:
- Standard role — what they can do;
- Scope — where they can do it.
Standard role
| Standard role | Can do |
|---|---|
| Admin | Configures the organisation: members, roles, navigation, sharing, installed Apps. Sees everything. |
| Advanced Operator | Like Operator, plus advanced actions (critical commands, e.g. cutting a motor). Same data as Operator. |
| Operator | Acts on devices (routine commands, alarm acknowledgement) and views. |
| Viewer | Views only (read-only). |
The four standard roles cover the whole organisation. To limit a member to specific zones, create a custom role (below) and assign it.
The Advanced Operator sees exactly the same data as the Operator; the only difference is permission for advanced actions on devices. Fine-grained per-command checks arrive with the device manager; until then the role is assignable and behaves like an Operator.
You assign a role in Settings → Members: at invite time and at any point after.
Access period (optional)
By default a member's access is permanent. On a member's detail, the "Add an access period" button reveals two dates:
- Active from: access opens automatically on this date (handy for a contractor starting next month);
- Until: access is cut off automatically on this date (handy for a temporary engagement).
Leave a date blank to leave that side open-ended (for example "from July 1st" with no end date). The restriction is enforced, not just cosmetic: outside the window the member loses all access to the organisation (devices, locations, navigation, actions), with nothing to remember to revoke. The member list flags scheduled and expired access at a glance.
The "Remove the period" button restores permanent access. The only Admin cannot set an access period on themselves (a guard against locking the organisation out).
Custom roles
In Settings → Roles, each organisation defines its own roles.
A custom role:
- rides a standard role (Advanced Operator, Operator or Viewer) — that's what determines real access;
- is limited to a selection of tags and/or locations — the member only sees devices carrying those tags or placed in those locations (no scope = whole organisation);
- has its own menu, curated right on the role card (see below).
Examples: "North-zone Technician" (Operator · North locations), "Town-hall Contact" (Viewer · the town's tags).
Scope (tags and locations) is set on the role, not on the user: to restrict a member, add the tags/locations to the role, then assign that role. Scope stays strictly bounded to your organisation.
Deleting a role does not remove members' access: they fall back to their standard role (whole organisation), without the custom menu.
Per-role menus (navigation)
Navigation visibility is a menu-curation tool, not a lock: hiding a dashboard from a role removes it from that role's menu, but if the member has access (via their role and scope) it remains reachable through its direct link.
On a custom role's card
In Settings → Roles, select a custom role in the left list — its editor opens on the right. The Menu section offers a mode:
- Open (default) — the whole menu is visible; you hide individual items as needed. Hiding an item also hides its children. Any new item added to the menu is visible automatically.
- Restricted — the member sees only the items you show. An item whose parent section isn't shown is promoted to the top level. Until something is shown, the menu is empty; any new item stays hidden until you show it.
The header shows what the role sees ("sees N/M"), and the Preview (member's view) beside the editor shows the resolved menu exactly as a member of this role will see it — handy to check the result before assigning the role.
The Settings → Navigation page is now purely structural (sections, dashboards, tools, order, nesting) — per-role visibility is configured entirely here, on the role's card.
Personalize my navigation
Each user can tailor their own sidebar without changing anyone else's:
- Favourites — hover a dashboard and click the star to pin it. Your favourites appear at the top of the navigation.
- Hide for me — hover an item and click the crossed-out eye to remove it from your navigation. An "N hidden item(s)" button at the bottom brings them back.
These preferences are private: they affect neither other members nor permissions.
Navigation colours
The top bar and the sidebar come in six themes: Classic (the original white), Cyan, Graphite, Night, Pink and Zen. Each follows the page's light or dark mode; page content does not change.
- For the whole organisation: an Admin picks the theme in Settings → General, "Appearance" card. Every member sees it on their next page load. An organisation created since this change, or with no settings saved yet, starts on Classic. An existing organisation keeps the look it shows today (Cyan if nobody picked another one) until an Admin changes it. Each organisation has its own: a sub-organisation does not inherit its parent's.
- For you only: My account → Preferences, "Thème" section, under the Light / Dark / Auto choice: "Couleurs de la navigation". Your choice wins over the organisation's; "Follow my organisation" goes back to it. When you switch organisation, you then follow the theme of the one you open.
Rights and access (read-only)
Settings → Rights and access is a read-only screen, restricted to Admins. It shows, without changing anything, the detailed rights being rolled out alongside the standard roles:
- Security groups: their members, and the validity window of each membership;
- Role assignments: which role each person holds, over which scope (the whole organisation, a location, a device...) and for which period;
- Permission catalogue: every existing permission, grouped by domain then by risk level, each with its explanation;
- Role by permission matrix: what each role allows or denies, with a search bar and keyboard navigation (arrows, Home, End).
Two things surprise on a first read, and both are deliberate:
- Expired rows stay on screen, labelled "Expired". They no longer grant anything; they remain visible precisely because they are the ones to clean up. The count shown ("2 active out of 5") only counts rows still valid.
- A permission can be flagged "not declared in the registry": a role carries a rule aimed at a permission that no longer exists. The rule grants nothing, and it is displayed so that you can remove it.
Changes (creating a group, assigning a role, editing the matrix) cannot be made from this screen yet; they arrive in a later release.