Each organisation has access to a specific set of modules. They define which functionalities the organisation has access to and affect, in turn, what actions each user role in the organisation will be able to perform.
To see a detailed table of all roles and permissions according to modules, please read Roles description.
What modules are there in the system
We have built modules around the different use cases we have identified in our different customer organisations. They are divided into three main categories.
Basic modules are always included, for all organisations and user roles. They are what makes the system whole and glue your user experience together.
They include access to:
- The dashboard*
- Your user settings
- The notifications*
- The support panel
*Widgets and notification types displayed will however depend on which functional modules you have access to. For example, if you do not have access to Team data, you won't be notified when a new team member joins, despite having access to the Notifications page.
Functional modules define what kind of organisation you are - what its role in the system is. Depending on the functional modules you have access to, you might be able to manage charging stations, view maintenance data, update your organisation's information, manage team members...
Functional modules you have access to are always a sub-set of the modules of your parent organisation. This means that your children organisations can never have access to any functional module you do not have access to.
Examples of functional modules: Alerts, Reports, Stations > Find, Stations > Manage, Stations > Logs, Customership > My team...
(Full list available on Roles description)
The set of functional modules you have access to is always defined by the parent organisation that has invited you to create (or has created) your organisation. It is often based on the business contract you have with that entity, but can also be affected by a wish to make your life easier by giving you access to only the features you need.
As a reseller, this also means that you can customise the access given to your customer organisations not only based on the roles, but also on the modules you'll enable for them.
We invite you to direct the questions about your modules to the business organisation providing you access to the Virta platform.
Premium modules are a type of module that can never be passed on to children organisations. They can only be included as part of agreements contracted directly with Virta, and give you access to additional functionalities such as reselling features.
If you would like to hear more about premium modules, please get in touch with us at Virta directly.
How to manage modules (Coming soon)
As modules are always defined by an organisation higher in the system hierarchy than yours, it is not possible to manage your own modules directly.
Depending on your access, however, you might be able to create and manage your own sub-organisations.
We are currently developing the modules management functionality.
At the moment, modules are automatically copied from one organisation to their children.
In the near future, module management will be possible during the organisation creation process. You'll be able to select, from there, the sub-set of your own modules you wish to give this new organisation access to.
We will later develop stronger (premium) reseller features allowing you to view and edit the modules of all your children organisation.
How does this relate to the old admin panel?
If you have been a user of our old system, you might wonder how this all affects your permissions there. It doesn't. Modules are a pure functionality of the new platform.
It is however good to note that when creating organisations from the old system, it will therefore not be possible to select modules with as much precision as in here. So when inviting users over to the new platform, you might need to update modules manually.
For this reason, we advise you to create any "custom" organisation rather from the new platform.