01Features · Platform
The right people, the right chargers, the right buttons
A charging business quickly involves more people than founders: field technicians, city managers, finance, support, franchise partners. zevOS lets you give each of them exactly the reach their job needs and nothing beyond it — enforced on the server, where it counts.
Roles & access control
Server-side
Enforcement
Station groups
Scope
Audited
Trail
Capabilities
What this gives you
Roles for how teams actually work
Owners run the business, operators run the chargers, viewers read the numbers, and support handles drivers. Permissions follow the role rather than being assembled per person.
Station groups
Restrict a staff member to the sites they are responsible for. A city manager in Ludhiana sees Ludhiana. Owners always see everything, so nobody can accidentally lock themselves out of their own network.
- Per-group permissions: view, operate, manage
- A staff member can hold several groups
- Restrictions apply to data, exports and commands alike
Tenant isolation
Every operator on zevOS is a separate tenant, and tenant scoping is applied in the data-access layer rather than trusted to individual queries. One operator cannot read another’s data through any surface, including the API.
Audit trail
Tariff changes, remote commands, refunds, permission changes and settlement approvals are recorded with who did them and when.
Questions
What operators ask about this
Can I restrict who issues refunds?
Yes. Financial actions — refunds, settlement approval, payout marking — are separately permissioned from operational ones.
Is the front-end check enough?
No, and zevOS does not rely on it. The interface hides what you cannot do, but every request is authorised again on the server.
Related
Works closely with
See roles & access control working
A walkthrough against your own chargers and tariffs, rather than a demo tenant with tidy data.