Modules
Find out which modules the client has, and what happens when a module is installed or uninstalled.
Goals and why
What you will learn
- read the module overview and see which modules the client has
- find out whether a missing feature is caused by the module or the permission
- who gets access to the new pages when a module is installed
- what you lose when a module is uninstalled
When a user misses a feature, you check the module first and the permission after. Many features build on each other. Products in the menu requires the invoice module. Resource Reporting under Settings requires the FleetX module. The fuel surcharge on the vehicle type only shows with the invoice module.
A new module changes the system for everyone. New menu items and subpages appear. Active users in the Manager group get access automatically, and everyone else needs the permission from you. Users must log out and in again before they see the change. Uninstalling is more serious. You lose access to data created with the module, and some modules cannot be uninstalled. So make that decision together with the customer and support.
Key terms
Show me
The images show the module overview and the card for a module the client does not have yet. Click a part of the module overview to see what it means. Never install or uninstall a module to test.
Try it yourself in Steptour
An interactive walkthrough recorded in Frakt24. You click through the steps yourself, and it opens on top of this page.
Try it yourself
Check yourself
All correct completes the lesson- Some modules ask for extra details on install: Prepayments wants an Accounting id and creates the price code PREPAY, Tracksys and VEGA want an API key.
- When the client has the FleetX app, the new module list is sent to the app on install and uninstall.
- Modules marked Private are only shown to super administrators. Never test installing in a customer tenant.