Charger connections
OCPP security profiles, set per charger.
Each charger runs at the profile it supports, and can be held to that profile or exempted one by one, with every change logged.
Unsecured
Only for legacy chargers, and flagged with a warning.
Basic authentication
A password per charger, stored hashed.
TLS + password
The connection encrypted, the charger authenticated.
Mutual TLS
Charger and platform both prove who they are with certificates.
Access
People see what they need, and nothing more.
Every customer in its own branch
Each organisation sees its own branch of the customer tree and what’s below it. Widening one customer’s view never widens anyone else’s.
Page by page, action by action
Roles come from permission templates, and an admin can never grant more than they hold themselves.
Help is recorded as help
When your team works in a customer’s console through “view as customer”, the change is recorded as made on their behalf.
Always an admin
Every organisation keeps at least one admin, so access never depends on a single account that might disappear.
One switch, everywhere
Suspending a customer stops its users, its charging authorisations and its stations at once.
No answer means no
When an authorisation can’t be decided, the charger is refused rather than left open.
Data
Your data stays yours.
- ExportableCustomers can export their own data, including if they move to another provider.
- Drivers’ data kept on our sideWhen partners build their own app on our API, drivers’ personal and payment data stay with ChargeIT, under GDPR controls.
- Payments through the providerCard payments run through the payment provider connected for that customer.
- PROFILE-ENFORCE-OVERRIDECP-014 · held to profile 2
- PROFILE-EXEMPT-OVERRIDECP-003 · legacy exemption
- Authorization key rotatedCP-022 · two-phase
- Change made via view as customerrecorded as on their behalf