Introduction: Accounts vs. Users
Accounts represent a private person or an organisation. It contains al necessary information you need for billing or contact:
account plan (optional) > this unlocks features of the selected account plan
account type: private or company
account name
language: used for e-mails
contact person: name, phone, e-mail
billing address
payment
reimbursement charge sessions account
notifications: enable automatic e-mails about issues of the charging station
Users are part of an organisation and have a specific role:
Account roles: These roles give the user access within the scope of the account.
Name | Description |
no role | User-role with limited access, only to own location and sessions. |
API developer | Someone who can access our API Credentials (only read) |
Locations facilitator | A location facilitator can access (by invite) a location from another account to have insight in sessions. |
Field Service Technician | Person who installs/configures the charge stations |
Billing admin | Person who can see invoices on the account. |
Account admin | Admin of an account, can add users and see all sessions on the account. |
How to create an account
We always advise to let customers complete the signup flow.
Via the api: Check https://dashboard.road.io/docs/reference/accounts for instructions how to create accounts via the api.
In the dashboard:
Go to ‘accounts’ and click on + New Account
Enter all the information except for ‘Integrations’ and ‘NetSuite’ and save.
How to create an user
Via the api: Check https://dashboard.road.io/docs/reference/users for instructions how to create users via the api.
In the dashboard:
First create the account
Go to the account and click on ‘Invites’
Click on + Create Invite and enter the e-mail address of the user.
IMPORTANT: Postmark needs to be activated otherwise the e-mail can’t be sent.
Import and export of accounts
Import of accounts and users: if you want to import accounts and users from a legacy system this is possible. Make sure the CSV file you are importing contains the following fields:
Accounts
contact.gender - can be "female" (lowercase), all other values will default to "male"
featureFlags - comma,separated,list
Users
contact.gender - can be "female" (lowercase), all other values will default to "male"
defaultLangCode - can be "nl" (lowercase), all other values will default to "en"
migrated - "true", "false" (default is "false" if empty)
The UI calls the same endpoint as when you create an account via the normal UI flow, so hopefully all of the spreadsheet columns map to something in the UI so that it makes sense