The Elvo CPMS Platform is used by three kinds of organization, arranged in a three-level hierarchy. The manual calls each of these levels a tier.
The three tiers
- Enterprise. The top of the hierarchy: a white-label operator running its own branded instance of the platform. Enterprise users see every Partner beneath them, every Client beneath those Partners, and all the charging infrastructure across the entire tenant. A typical Enterprise is a company that resells the Elvo platform under its own brand (for example, a national charging network or a regional energy company).
- Partner. A second-level organization under an Enterprise. Partners can also exist as the direct customer of an Enterprise — a local branch, installer, or CPO subdivision. A Partner sees only the Clients it owns and the infrastructure operated by those Clients; it does not see other Partners.
- Client. A third-level organization under a Partner. A Client is the company that physically owns or operates a set of charging stations and manages the drivers who use them. A Client sees only its own stations, drivers, and authorizations.
All three tiers can have their own users — there is no tier that lacks user management. Users at any tier are scoped to the entity they belong to and to its descendants.
Tier-to-role mapping
Each tier exposes three role variants. Roles are assigned per user account and they determine what that user can see and change inside the platform.
| Tier | Roles |
|---|---|
| Enterprise | enterprise-superadmin, enterprise-admin, enterprise-superauditor |
| Partner | partner-superadmin, partner-admin, partner-superauditor |
| Client | client-superadmin, client-admin, client-superauditor |
The three variants in each row follow the same pattern:
*-superadmin— full read/write access within the tier’s scope.*-admin— read/write access within the tier’s scope, with a few specific features reserved for*-superadmin(such as Public Drivers at the Enterprise level).*-superauditor— read-only access within the tier’s scope. A superauditor can view all pages and export data, but cannot create, edit, or delete anything.
The complete role-to-feature matrix lives in section 10.2.
How the manual handles tier differences
Most platform features behave the same across all three tiers, so most
sections are tagged [All tiers] at the top of the page. Where a feature is
not available at a given tier, the badge narrows:
[All tiers]— the section applies to Enterprise, Partner, and Client.[Enterprise + Partner]— the section applies only at the Enterprise and Partner tiers; the Client tier does not see this area.[Enterprise only]— the section applies only at the Enterprise tier.
You can also restrict the entire HTML build to a single tier using the View as selector at the top right of every page — Enterprise, Partner, Client, or the unrestricted master view.
For finer-grained variations — where two tiers can both reach a feature but the UI differs at the step level — the manual uses inline tier callouts. These appear in the relevant numbered step and look like this:
Choose the Partner from the dropdown.
Choose the Client from the dropdown.
A step with no callout applies to every tier in the section’s badge.
A concrete example
When you create a new location (see section 4.2), the form asks you to attach the location to an owning organization. The dropdowns shown depend on which tier you are signed in as:
- Enterprise. You see both a Partner dropdown and a Client dropdown, because you can place the new location under any Partner and any Client.
- Partner. You see only a Client dropdown — the Partner is already determined by your account.
- Client. Neither dropdown appears. The Partner and Client are both fixed by your account, and the new location is automatically scoped to your Client.
Steps in Part 4 (Locations) are written using callouts like the ones above so that operators at each tier see only the dropdowns and fields relevant to them.