Admin permissions
How access works for the people on your account: finely scoped permissions for your internal admins, location restrictions, and external admins (fleet managers) who manage only their own fleet.
EOSVOLT has two kinds of admin accounts:
- Internal admins: your own team members. Each one carries a set of permissions you configure when creating or editing the admin (see Admins), deciding which modules they can open and which actions they can perform.
- External admins (fleet managers): people at a customer fleet company. They log into the fleet view and manage their own fleet only: its drivers, cars, and charging keys. They never see your wider operator data.
How internal admin permissions work
Permissions come in two layers, set per admin:
- Module access: whether the admin sees a section at all: Dashboard, Sessions, Charge points, Customers, Price profiles, Booking, Load balancing, Fleet, Intelligence, My finances, Diagnostics, OCPP Toolkit, Settings, Admins.
- Actions within a module: view, add, edit, delete, export. A view-only admin can inspect everything in a module without being able to change anything.
A third dimension is location restriction: an admin can be limited to specific locations, in which case every module only shows data from those locations. Permissions and location restrictions combine. For example, an admin with Sessions and Charge points access restricted to location A sees only location A's sessions and chargers.
Typical permission setups
| Admin | Typical permissions |
|---|---|
| Owner | Everything, including Admins and Settings |
| Operations | Sessions, Charge points, OCPP Toolkit, Diagnostics, Intelligence. No finances |
| Support | Sessions and Customers (view), Charge points (view). No editing |
| Finance | My finances, Sessions (view and export). No infrastructure changes |
| Site host | Charge points and Sessions, restricted to their own location |
What a restricted admin experiences
Modules they lack are absent from their menu and cannot be opened by URL. Data from locations outside their restriction never appears. The AI support assistant follows the same rules: it only offers lookups the admin's permissions allow, so it can never become a way around a restriction.
External admins (fleet managers)
When you service a customer fleet (see Internal & External Fleets), the fleet company gets its own admin login. A fleet manager can manage their fleet's drivers, cars, charging keys, and teams, and see their fleet's charging activity. They have no access to your locations, pricing, finances, or other customers.
Common questions
Can I make a view-only admin? Yes. Enable the modules they need and leave the add, edit, and delete actions unchecked.
How do I give someone access to only one location? Assign them that location when creating or editing their admin account. Everything they see is then limited to it.
What can a fleet manager see? Only their own fleet: drivers, cars, charging keys, teams, and their fleet's sessions. Nothing about your wider operator account.
Who can manage admins? Only internal admins whose own permissions include the Admins module.
Does restricting an admin affect the AI assistant? Yes. The assistant's abilities mirror the admin's permissions exactly, including location restrictions.
Updated 26 days ago