FCPlus hierarchy manual
Related Manuals
- FCPlus Settings manual
- FCPlus Organization settings
- FCPlus Events settings
- FCPlus Hierarchy
- FCPlus Settings People tab
FCPlus Hierarchy
Hierarchy is a level (tree like) structure that limits user access to parts of the system: vehicles, areas, events etc.
Customers with complex company structure where different users need to be setup with different access rights will benefit from using hierarchies.
1. Setup organization hierarchy structure
FCPlus -> Settings -> Hierarchy -> Add
Here you can create new hierarchy levels and configure access rights for each level.
You can add access rights for areas, vehicles , people etc. Each tab must be saved individually!
You will need to go through each tab to add the details you want to be visible and accessible to users.
Please note the setup will LIMIT user access. Users not belonging to the hierarchy node will NOT see assets selected for hierarchy.
2. Configure users
Settings -> People
Select user. User has 2 features related to hierarchy ‘Hierarchy level’ and ‘Hierarchy user access rights’. ‘Hierarchy user access rights’ means user belong s to hierarchy and can only see/edit assets assigned to that hierarchy.
‘Hierarchy level’ means user belongs to hierarchy and cannot be seen by other users outside same hierarchy level.
3. Check user roles
Check the roles of your users to make sure they have proper setup to limit the viewing of items outside their hierarchy.
Settings -> Roles -> look for Hierarchy node (center column)
If ‘Has access to unassigned assets’ is ticked that means users will be able to see any ‘assets’ (areas, vehicles etc) which are not assigned to any hierarchy level. Under standard hierarchy setup this option MUST BE UNTICKED.
4. Login as user view the result of hierarchy setup
Use case:
I have organization with areas, vehicles and users. I want to limit user access to certain users can only see certain vehicles, areas and other users. I create hierarchy. I give parent node access to certain areas vehicles and users. API user should have access to Hierarchy assets.
User access rights for API user:
Limit user access for selected areas:
Limit user access for selected vehicles:
You can set up hierarchy access for multiple items at once by using the ‘Select All’ checkbox in the hierarchy tabs: Vehicles, Areas, People, and User Access Rights.
My Settings ->Users ->API user Hierarchy user access rights-> has parent hierarchy selected and 2 roles.
For both roles my Settings -> Roles ->Hierarchy node-> has ‘Access to unassigned assets’ is unticked, meaning no user can see any assets unless assets and user belong to same hierarchy level.
If I login as API user who was added to hierarchy I can see all assets that were ticked for the hierarchy.
The only selected hierarchy vehicle is visible:
Only selected hierarchy areas are visible:
If I login as any other user I cannot see anything, meaning user MUST be added to hierarchy level(s) to get access to see ‘assets’.
Please note enabling hierarchy some other parts of the system can be affected:
- Reports can be run Filtered by Hierarchy.
- Events must be added to hierarchy to be visible to hierarchy users.
Hierarchy and Trips module
Trips module respects hierarchy setup. If user has access to all vehicles but only selected drivers, only trips will be shown - are by drivers whom user is allowed to see based in hierarchy setup.