Register Closure Report Scope by Role
Zenoti delivers the register closure report to every center within a user's organizational scope β not only the center they are primarily assigned to. This article explains how role-based scoping works, why a user may receive closure reports for multiple centers, and what administrators need to know when managing access.
On this page
- Before you begin
- How role-based scope determines report delivery
- Why a user receives reports for multiple centers
- How scope changes take effect
- Related articles
Before you begin
- You must have administrator or owner-level access to manage security roles and view report distribution settings.
- To change the centers a user receives reports for, update that user's security role scope β no separate report subscription list exists.
Permission: Managing security roles requires the appropriate permission under Configuration > Security > Security roles.
How role-based scope determines report delivery
When Zenoti delivers the register closure report, it evaluates the organizational scope of the recipient's security role at the time of delivery. The report is sent to every center that falls within that scope β not only the center to which the user is primarily assigned.
For example, a manager whose security role grants access to three centers receives the register closure report for all three centers in a single distribution cycle. A front desk employee whose role is limited to one center receives the report for that center only.
This behavior is by design. The register closure report reflects end-of-day financial activity, and users with multi-center responsibility need visibility across all the centers they oversee.
Why a user receives reports for multiple centers
If a user receives register closure reports for centers they did not expect, the most common reason is that their security role scope includes those centers. This can occur when:
- A manager role is configured at the zone or organization scope rather than a single-center scope.
- A user has been granted access to additional centers through their security role without a corresponding update to their report expectations.
- The organization uses a role that inherits access from a parent scope (organization or zone), which automatically includes all centers beneath it.
Zenoti resolves center scope at delivery time using the role-based access rules applicable to the recipient. There is no static distribution list to maintain β the system always reads the current role configuration when the report runs.
How scope changes take effect
Because scope is evaluated at delivery time, any change to a user's security role is reflected in the next report distribution cycle automatically. No manual list maintenance is required.
- Granting access to a center: The user begins receiving the register closure report for that center starting from the next distribution cycle.
- Revoking access to a center: The user stops receiving the register closure report for that center starting from the next distribution cycle.
Note: Changes to security role scope apply immediately to role-based access across Zenoti. The register closure report distribution reflects these changes in the next scheduled delivery.