Controlling which reports each role can see

Report permissions let you control which reports appear in the Reports menu for each role. This keeps the interface clean and prevents users from accessing data they should not see.

Before you start

• You must have administrator access.
• Know which reports the role should be able to view and run.
• Reports are often sensitive (profit margins, payroll, aging analysis). Plan access carefully.

Steps

1. Go to Settings → Users & Roles → Roles, then open the role you want to configure. Open in Usystems

2. Scroll down to find the Report Permissions section.

3. Look for the list of available reports. Each report has a checkbox next to it.

4. Check the boxes for the reports you want to allow this role to see. For example:

   • Check "Sales Summary" to let the sales team view sales performance.
   • Check "Inventory Aging" to let the warehouse team see stock age and slow-moving items.
   • Leave "Profit Margin" unchecked if you want to hide it from junior staff.

5. Save the role.

How report visibility works

When a user logs in, the Reports menu shows only the reports their roles allow. If a user belongs to multiple roles, they see the union of all reports from all their roles.

For example:

• Role "Sales" has permission to view "Sales Summary" and "Customer Aging."
• Role "Viewer" has permission to view "Sales Summary" only.
• A user in both roles can see "Sales Summary" and "Customer Aging."

Tips & common mistakes

• Empty reports menu? If a role has no report permissions checked, the Reports menu will not appear for users in that role. You can still navigate directly to a report's URL if you know it.
• Data still visible elsewhere: report permissions only hide the Reports menu. If a user has permission to view documents (invoices, bills, etc.), they can still see their financial impact. Use document-level permissions to truly restrict data access.
• Test before deploying: create a test user, assign the role, and verify they see only the intended reports.
• Changing permissions mid-session: like other permissions, users may need to log out and log back in to see the change reflected in the Reports menu.