Roles and permissions

A role sets what a user can do in Connect: which pages they can open, and which actions they can take on the data their customer scope already gives them access to.

​

Overview

Every Connect user has a customer and a role. The customer decides which data they see; the role decides what they can do with it. Setting one without thinking about the other is how someone ends up able to edit tariffs across an entire portfolio, or unable to see the site they were hired to run. Five roles form a general ladder, from full edit rights down to read-only. Three more are shaped around a specific job and sit outside that ladder. A user can hold more than one role at a time. You assign roles in Team Access, which also covers who is allowed to assign which role.

​

Choosing a role

Start from the job, not the role name.

​

The general roles

Operator, Editor, Supporter, User, and Viewer cover most people you invite. They overlap heavily, so the differences are easier to read as a table than as descriptions. A dash means the role has no access to that area. Tokens appear as charge keys in Connect’s interface; the two mean the same thing.

​

Operator is for your own team

Keep Operator for colleagues at your own company, on the operator side of the account. Users scoped to a customer should hold Editor or below, however senior they are on their own side: an Operator can change billing, settings, and pricing everywhere their scope reaches. That makes the Operator and Editor boundary the one worth knowing. Creating locations and charge boxes, charge box configuration, payment terminals, SLAs, settings, branding, and the Operations Center all stay with Operator. An Editor does the rest, including editing and deleting locations. So an Editor who needs a new charger on a site has to ask, which is usually the point: adding a charger changes what that site bills.

​

Specialist roles

These three exist for one job each. They don’t sit above or below the general roles, and they pair well with one — an on-site engineer who also fields driver calls might hold Depot Manager and Supporter together.

​

Holding more than one role

A user can hold several roles at once, and their access is the sum of them. Pairing Depot Manager with Supporter gives someone the site’s chargers plus driver support, without handing over the whole account. Combine roles when no single one fits the job. It’s the better answer than moving someone up the ladder to reach a single feature they need.

​

Dependencies & limitations

• The roles are fixed. They’re shaped around how charging teams actually divide the work, so the set covers the common shapes without configuration. Where one role doesn’t fit a person, combine two.
• Scope data with the customer hierarchy, and features with the role. A role applies across everything the user can already see, so narrow their reach by placing them under the right customer rather than by picking a smaller role. See Customers.
• Role assignment follows the hierarchy. You can assign any role at or below your own, so an Operator can appoint another Operator and an Editor can build out a team of Editors and below. Covered in Team Access.

​

Related