There are different roles defined in the ATOM Dashboard, depending on the functions each role performs and accesses required to do so.
Below you will find explanations for each of the roles:
GLOBAL ADMIN / ADMIN:
ADMINISTRATOR role holders have a comprehensive view of all the sections in the dashboard, are able to add and edit information in the various dashboard sections and maintain system preferences for the apps through the dashboard.
NB! GLOBAL ADMIN has access to aggregated data for all subaccounts (Global view) and can access all subaccounts. This is not available for a regular ADMIN role.
NB!! A GLOBAL ADMIN role is initially granted to at least one user on your team by ATOM Mobility's technical team - afterwards a GLOBAL ADMIN can extend GLOBAL ADMIN privileges to other users on your team, as well as revoke GLOBAL ADMIN privileges and change the role for any user.
GENERAL MANAGER:
2nd level after ADMIN
Primary focus is ride and vehicle information
Can view IoT data and add new IoT devices
Can create and edit different zones
Sees customer and ID information, customer statistics
Purpose: role designed to actively manage the fleet and service - expand or reduce if needed (adding/removing IoT devices and vehicles, adding and editing zoning of the service area).
FLEET MANAGER:
Focus on IoT devices & vehicles
Purpose: role designed to actively manage the existing fleet in terms of hardware - IoT devices and vehicles themselves. The role has no access to sensitive customer information or ability to maintain system preferences or personalize the apps through the dashboard.
MANAGER:
Focus on rides & vehicles
Purpose: role designed to actively manage the existing fleet, without access to sensitive customer information or ability to maintain system preferences or personalize the apps through the dashboard.
CUSTOMER SUPPORT:
Focus on customers, rides & vehicles
Purpose: role designed to be able to support B2C customers with their inquiries into ride charges, subscriptions and other support-related topics, without access to business revenue information or ability to maintain system preferences or personalize the apps through the dashboard.
OPERATOR:
Focus on vehicles & maps
Purpose: role with access to vehicle and mapping information relevant for team members responsible for vehicle placement and maintenance.
NB! The service app can be used only by ADMINS, CUSTOMER SUPPORT and OPERATORS.
REDACTOR:
Ride verification view only
Purpose: in case you have mandatory ID and/or parking photo verification enabled and need for someone to manually check and approve documents and images submitted by your customers.
MARKETEER:
Vehicle statistics view only
Purpose: in line with the marketing campaigns of your business this role can monitor vehicle usage statistics and create promo codes for your users in order to boost the number of new customers or engage existing customers more actively.
DATA ANALYST:
Statistics view only
Purpose: for governmental bodies, local municipality representatives and anyone else asking for detailed data.
FRANCHISEE:
Manage vehicles, Maps and Statistics view only (specific to the assigned subaccount)
Purpose: when franchising business model is in place, this role is granted to your franchise partners in order to let them view and interact with their specific subaccount information. This role has no overview of sensitive customer information.
VEHICLE OWNER:
Manage vehicles, Maps and Statistics view only
Purpose: when P2P sharing is in place, each account belongs to a vehicle owner who rents his/her vehicle.
For a comparison of all the roles and their access levels, please refer to the file below:
As an Admin you're able to extend access to other members of your team, so once you've determined what kind of roles your team members should hold depending on the accesses they will need, you can assign roles to them as per below:
In the ATOM dashboard got to the section More -> Team and accounts -> Team permissions:
Choose Add new user to the top right-hand side and fill in the user information, choose their role and assign applicable subaccount(-s) to them, then Save: