Printexus combines functional rights with data scope. Permission to read Fleet is paired with the countries, cities, sites or exact devices the user may actually see.
Before you begin
- Define job responsibilities before individual users.
- Prepare the real territory each technician covers.
- Decide who may create, change and delete operational records.
Roles and modules
A role provides a safe baseline. Module permissions refine read, create, update and delete access. Dashboard remains available to every signed-in user.
Data scope
Assign specific devices, locations, cities or countries to a technician. Fleet, Dashboard and tickets then use the same scope.
Dispatch rule
A ticket cannot be assigned outside the technician’s allowed territory. If no technician qualifies, explicitly extend the scope instead of bypassing the control.
Recommended practice
- Start with least privilege and expand when work requires it.
- Verify role changes with a test user.
- Review access whenever job or territory changes.
Common pitfalls
- Checking every module “just in case” defeats least privilege.
- Module access does not replace territory scope.
- Deleting instead of deactivating may hinder accountability.
How to verify the result
Each user sees exactly the functions and data needed, while dispatch blocks work outside territory.
✓
Continuously updated for the current Printexus release.
Still need help? Contact support.