Access control
Understand roles, charging access and authentication.
Contents
Understand access control
Access control answers three different questions: What can a person manage, who can charge and how is a charging session authorised?
User role
What can I manage?
Access level
Who can charge?
Authentication
How is it authorised?
Your user role determines what you can manage. The access level determines who can charge.
Access levels: Who can charge?
The access level determines who is allowed to start a charging session.
Open
Anyone with physical access to the charger.
No authentication is required.
Public
People with an Easee account. A site invitation is not required.
Authorisation through the Easee App, an Easee Key or a compatible RFID tag.
Private
Only people approved for the site or charger.
Authorisation through the Easee App, an assigned Easee Key or a compatible RFID tag.
Without authentication, a charging session cannot be assigned to a specific person. Consumption remains available in reports for the site and charger.
User roles and permissions
User roles determine what a person can manage and view at a site. A role alone does not determine whether the person can charge.
Site OwnerHighest permission level at the site
Manages site settings, chargers, administrators, users, access levels and reports. Only the Site Owner can transfer ownership. A site has exactly one Site Owner.
AdministratorDay-to-day site administration
Can manage site settings and access levels, invite users and view site reports. An Administrator cannot transfer ownership.
UserUse of approved chargers
Can use approved chargers and view personal consumption. Users cannot manage the site, other users or access levels.
Authorise charging sessions
Authentication verifies charging permission and allows a charging session to be assigned.
Easee App
Depending on the access level, an approved user can authorise the charging session through the associated Easee account.
Easee Key or compatible RFID tag
The user taps the key or RFID tag on the charger. If the key is assigned to an account or approved user, the session can appear in the corresponding consumption data.
No authentication
Available only with the Open access level. Anyone with physical access can charge; consumption cannot be assigned to a person.
Linked and unlinked chargers
The access level can apply to every charger at a site or be configured separately for an individual charger.
A linked charger inherits the site access level. Changes to the site access level also apply to every charger linked to the site.
An unlinked charger does not follow the site access level. Its access is configured separately, and users can be added directly to the charger.
Unlinked separates only the charger access level from the site access level. The Site Owner and Administrators retain their management permissions.
MANAGE IN EASEE CONTROL
Set the access level
Open the site and manage the access level for the site or an individual charger.
Manage access in Easee Control →Frequently asked questions
Answers to common questions about roles, charging permissions and linked or unlinked access.
What is the difference between a user role and an access level?
A user role determines what you can manage or view. The access level determines who can start a charging session.
What happens when I change the site access level?
The change applies to every linked charger. Unlinked chargers retain their separately configured access level.
Does an unlinked charger remain part of the site?
Yes. The charger remains part of the site. Only its access level is managed separately.
Can linked and unlinked chargers be used at the same site?
Yes. This can be useful when a site has both shared and assigned parking spaces. Consider the difference between SDU and MDU sites when adding users.
Can a site have more than one owner?
No. A site has exactly one Site Owner. Multiple Administrators and Users can be added.
Does every user need an Easee Key?
No. Whether authentication is required and which method can be used depends on the access level and configuration.