ZenotiHelp

Report permissions and customization

ZTZenoti Docs Team Updated October 12, 2026 7 min readReference

Zenoti controls who can see which reports through report permissions. Legacy and modern reports use two separate, independent permission systems. Organizations can also customize column labels and configure report-level settings. This article explains how these features work.


On this page


How report permissions work

Zenoti has two reporting frameworks: a classic reporting framework (the original reports) and a modern reporting platform (the current Reports Dashboard). They use completely independent permission systems, granted in different places:

  • Classic reporting framework β€” permission is at the module level. You grant access to legacy reports under the functional module that owns them. For example, the classic sales reports are granted through the View Sales Reports row in the Sales section: Configuration > Security > Security roles > the role > Permissions > Sales > View Sales Reports.
  • Modern reporting platform β€” permission is at the report level. You grant access to each modern report individually. For example, to grant the Memberships Payment report: Configuration > Security > Security roles > the role > Permissions > Reports(V2) > Marketing > Memberships Payment Report.

There is no connection between the two systems. Granting (or removing) a classic reporting framework module-level permission has no effect on modern reports, and granting (or removing) a modern report-level permission has no effect on classic reports.

When a permission is missing, the report is not shown. If a role does not have the permission for a report, that report does not appear on the Reports Dashboard for that role. There is no error message, no locked or greyed-out entry, and no "category appears but the data won't load" state β€” the report is absent from the list.

Permission groups

Classic reporting framework β€” module-level permissions

Classic reporting framework permissions live under each functional module section of the security role (Configuration > Security > Security roles > the role > Permissions). The table below lists the section, the row caption exactly as the page shows it, and the actions available under it.

Report family Security role section Row (as shown) Actions (as shown)
Employee reports Employee Manager View Employee Reports Commission, Performance, Team, Time, Sales, Grooming Points, Attendance, Payroll, Tasks
Inventory reports Inventory Manager View Inventory Reports Sales, Orders, Expenditure, Value, Consumption, Bill of Materials, Returns, Alerts, Taxes, Audit History, Orders History, Online Product Sales
Loyalty reports Loyalty Manager View Loyalty Reports Guests, Balances, Custom Data, Enrollment, Feedback, Targets
Marketing reports Marketing Manager View Marketing Reports Effectiveness, Guests, Memberships, Prepaid Cards, Packages, Loyalty Points, Redemptions, Gift Cards, Credit Consumption
Sales (Finance) reports Sales View Sales Reports Pipeline, Conversion
Admin reports Administrator View Admin Reports Sales, Collections, Revenue, Accounting, CSI Export, Xero, Alerts, Prescription, Appointments, Utilization, Notifications, Membership Status, Suspended Memberships, Classes, Import Export, Tally Exports, Online Bookings Report
Daily-reports page (Daily Summary, General - Register Summary, General - Revenue Summary, and the For the Month and For the Day groups such as Center Collection and Center Sales) Administrator DailyReports View

The View Admin Reports row expands into per-area actions, so an administrator can grant only the report areas a role needs. The actions shown are: Sales, Collections, Revenue, Accounting, CSI Export, Xero, Alerts, Prescription, Appointments, Utilization, Notifications, Membership Status, Suspended Memberships, Classes, Import Export, Tally Exports, Online Bookings Report.

Modern reporting platform β€” report-level permissions

Modern report permissions are granted per report in the Reports(V2) section of the security role, organized into category groups. The groups are containers; the access decision is made on each individual report check box inside them. Each check box carries the report name (for example Sales(Cash) Report).

Category group (as shown under Reports(V2)) Example report check boxes
Business Business KPI Report, Salon Summary Report, Audit Transactional Report
Employee Attendance Report, Employee Sales Report, Employee KPI Report
Financial Sales(Accrual) Report, Accounting Summary Report, Register Closure Report
Guest Engagement Guest Retention Report, Feedback Report, Service Forms Report
Integration Integrations Sync Status Report, Accounting Recon Report
Inventory Current Stock Report, Cost of Goods Report, Stock Ledger Report
Marketing Packages Report, Memberships Report, Gift Cards Report
Miscellaneous β€”
Operational Appointments Report, Notification Email Report, Notification SMS Report
Zenoti Payments Reconciliation Report, Dispute Payments Report, Digital Payments Report

Note: A report's category group in Reports(V2) reflects how the product groups it, which is not always the same as the functional area you might expect. For example, the Feedback details (v2) report is grouped under Loyalty, not Marketing. Always grant a v2 report permission from the group the product places it in.

Export permissions

Report file download is controlled separately by the Export permission in the Miscellaneous group. A user who can view a report in the grid but lacks this permission can analyze data on screen but cannot download files.

Permission: Export under Miscellaneous in the Reports(V2) section of the security role β€” required to download report files. Admin path: Configuration > Security > Security roles > the role > Permissions > Reports(V2) > Miscellaneous > Export

For classic reporting framework reports, export access is granted per module alongside the module-level "View … Reports" action rather than through a single global permission.

Why a report may not appear on the Reports Dashboard

If a user cannot find a report on the Reports Dashboard, work through the following layers in order. Role permissions are the last layer to check, not the first.

Layer What to check How to check it
1. Module-level feature flag Some report families require an organization-level setting to be enabled before the reports appear. The V2 membership reports are the known case: they are gated by the Enable V2 Membership Reports organization setting. If that setting is off, no role can see those reports regardless of permissions. Confirm the relevant organization setting is enabled under Configuration > Reports or the relevant feature area.
2. Organization-level enablement A report may be enabled for some organizations but not others. If the report is not listed at all β€” even for the organization owner β€” the report may not be enabled for your organization. Contact your Zenoti account representative to confirm whether the report is available for your organization.
3. Role permission If the setting is on and the report is enabled for the organization, check whether the role assigned to the user has the correct permission. For modern reports, select the report's check box under its category in the Reports(V2) section of the security role (Configuration > Security > Security roles > the role > Permissions). For classic reports, select the report-area action under the View … Reports row in its module section. Navigate to Configuration > Security > Security roles, open the role, and verify the check box is selected.

Who can grant report permissions

Granting report access is restricted to the organization owner or head office. A center-level administrator who cannot find the permission grant in their security settings should route the request to the organization owner or head office.

Permission changes take effect after sign-out

A permission change does not take effect for a user who is already signed in. The user must sign out and sign back in for the new permission to apply.

If a permission grant appears correct but the report is still missing, also verify that the role you edited is the role actually assigned to that user. A user who holds several roles is a common reason a correct-looking grant has no effect β€” the user's active role may be a different one that does not include the permission.

Custom column labels

Organizations can override the default column headers displayed in report grids and exports.

  • Scope β€” Custom labels are defined at the organization level and apply to all centers.
  • Display only β€” Custom labels change the column header text in the report viewer and in exported files. They do not affect filter behavior, sort order, or underlying data values.
  • Per-column β€” Each column can have its own custom label, or you can leave the default label in place.

Custom labels are useful when your organization uses different terminology for standard Zenoti concepts. For example, you might rename "Provider" to "Therapist" or "Stylist" to match your business vocabulary.

Report settings

Report-level settings β€” daily report email subscriptions, dashboard display preferences (Target, Trends, Revenue), cross-center redemption computation, time formatting, profitability reports, report scheduling, the list-of-reports manager, and KPI configuration β€” are configured under Configuration > Reports.

For the complete settings catalog, see Configure report settings.

Was this article helpful?
Your feedback helps us improve our documentation.