Ask Flux
Help Center
How can we help?

Charging Authorization Restrictions

This page aims at explaining what was previously called Location Tied Token (LTT) feature, which aimed initially at addressing the use case where a certain token would only be able to charge in a specific location.

This feature is designed to enhance user control and security for various charging scenarios, by defining authorization restrictions in what regards the charging services. Here's a comprehensive overview of the key aspects and functionalities of the Location Tied Token feature:

Feature Definition:

The following customer use cases are supported:

Configuration Steps:

EvPortal Access and permissions required to use this functionality

In order to complete the steps below, the EvPortal user must hold a role which contains the following permissions:

  1. For steps 1 and 2: the required permissions are:
    1. Create exception groups
    2. Read exception groups
    3. Update exception groups
  1. For step 3:
    1. Create exceptions
    2. Read exceptions
    3. Update exceptions
💡

Existing roles with the above permissions:

  1. Admin
  1. CPO manager
  1. eMSP manager

Steps 1 and 2. Create a CPO (1) / eMSP (2) exception group (or use an existing one)

Go to the left tab to Exception Groups and click '+ Add New' button

Each group is composed by a set of items from only one given category - list of available categories for CPO groups (1):

  1. CPO
  1. Location

Each group is composed by a set of items from only one given category - list of available categories for eMSP groups (2):

  1. eMSP
  1. Customer
  1. Driver
  1. Token

Step 3. Define the required authorization restriction

The user can add new exceptions, by selecting at least a CPO group and at least an eMSP group, and then configure the exceptions based on the desired interactions between CPOs and eMSPs: whitelisting or blacklisting eMSP groups for CPO groups and vice versa.

Validity Range:

  1. Validity ranges are specified in date-time format without timezones.
  1. Timezone resolution occurs during authorization at the charger, accommodating global time differences.

Available flows in the exception menu:

Edit (an existing authorization exception group)

User can change Name and Notes (Category cannot be edited)
Did this answer your question?
😞
😐
🤩