Who can see what.
Who can do what.
Down to the toggle.
System is the platform's control room — role-based access control down to 44 individual permissions, per-community app module visibility, and the platform-wide settings that govern email, security, notifications, and maps for every deployment.
System at a glance
Two tools governing everything below them: who has access, and how the platform behaves.
System sits at the bottom of the sidebar for a reason — it's the foundation every other module runs on. Administration controls who can do what, and Settings controls how the platform itself behaves.
Legacy-safe by design. Admin users without any role assigned retain full access automatically — role-based access control only restricts an admin once a role has actually been assigned to them, so existing admin accounts are never locked out by rollout.
Admin Roles & RBAC
Three default roles, 44 granular permissions, and a clear split between Global and Community-Scoped access.
Administration opens on a live readout of your own access — role, scope, and permission count — before showing every Admin Role defined on the platform, each with its permission set visible at a glance.
Global vs. Community-Scoped is the key distinction. A Global role sees and manages data across the entire platform; a Community-Scoped role — like Account_admin — is locked to only the specific communities it's been granted, making it safe to hand out to third-party account managers or dealer partners.
Creating a Custom Role
Beyond the three defaults, build a role around exactly the permissions a job needs — nothing more.
Create Role builds a bespoke access profile from the full 44-permission catalogue, organised into 17 functional categories from Dashboard through to App Modules — with Select All / Clear All for fast setup.
- Role Name & Description — e.g. "Community Manager" or "PSIM Operator", so the role's purpose is clear to whoever assigns it later.
- Global Access toggle — off by default, meaning the role is Community-Scoped until explicitly widened.
- 17 permission categories — each expandable to granular View / Manage rights for that specific area of the platform.
- Live permission counter — "0 of 44 permissions selected" updates as boxes are checked, so scope is always visible before saving.
Design roles around real jobs, not job titles. A "PSIM Operator" role might only need View Dashboard, View Events, and PTT permissions — resist granting Manage Users or Administration rights unless that operator genuinely needs them.
Administrators
Assign roles and community access to every admin user on the platform, and see their current standing at a glance.
The Administrators tab lists every admin user with their currently assigned role and scope — and flags anyone still running in legacy full-access mode with no role assigned.
How RBAC works, in plain terms: admin users without any role assigned retain full access (backward compatible). Once a role is assigned, that admin only sees the modules and data allowed by their role and community scope. The Super Admin always has unrestricted access.
App Module Visibility
Control exactly which features appear in the Citizen App and Responder App — per individual community.
App Module Visibility is where a community's actual in-app experience is shaped: disabled modules disappear entirely from that community's app navigation, rather than just being greyed out.
Once a community is selected, three panels appear — Citizen App Modules, Citizen Home Buttons, and Responder App Modules — each a simple toggle list, with safety-critical items like SOS/Panic locked permanently on.
- Citizen App Modules — Reports, Groups, Chat/Messages; Home/Panic is always visible and cannot be disabled.
- Citizen Home Buttons — Fire, Suspicious Vehicle, Virtual Guardian, FaceMap; SOS/Panic is always on.
- Responder App Modules — Reports, Patrols, Health Check, Digital OB, Assignments, PTT, News; Panic/SOS is always on.
A cleaner app for a simpler community. A small residential estate that doesn't run patrols can disable Patrols, Health Check, and Digital OB for its Responder App entirely — decluttering the interface down to only what that community actually uses.
Portal Settings
The platform's own configuration — email delivery, general preferences, notifications, security policy, and default map providers.
Portal Settings covers five categories of platform-wide configuration, each in its own tab, from the SMTP server that sends every report email to the map provider used across admin, citizen, and responder views.
Email (SMTP)
Configure the outgoing mail server used for reports and notifications, with one-click Quick Setup for Gmail, Outlook, Yahoo, SendGrid, Mailgun, and Amazon SES, plus Test Connection and Send Test Email to verify before going live.
General & Notifications
General Settings sets the platform's identity and session behaviour — Platform Name, Description, Timezone, Date Format, Default Language, Session Timeout, and Max Login Attempts. Notifications sets default sound/vibration behaviour for new users and auto-notification rules for admins and communities.
Security & Maps
Security Settings governs authentication policy platform-wide — Two-Factor Auth, Email Verification, minimum password length, public registration, auto-approval, and API rate limiting. Maps sets the default map provider — Google Maps, Mapbox, or OpenStreetMap — independently for the Admin Panel, Citizen App, and Responder App.
Individual users can still override the default. Setting a platform-wide map provider here doesn't lock anyone in — individual users can still choose their own preferred map provider in their personal preferences.