ZenotiHelp

Default security roles and permissions

ZTZenoti Docs Team Updated October 18, 2026 7 min readGuide

Security roles decide what an employee can do in Zenoti. Permissions are configured per role, so everyone assigned the same role gets the same capabilities β€” which is why picking the right starting role matters more than adjusting permissions one at a time afterwards.

Every employee profile needs at least one role. Use the summaries below to match a job function to a role, then adjust that role's permissions if your business needs something different.

On this page


Before you begin

  • You need access to manage roles and permissions at the level you are working β€” organization or center.
  • The employee profile must already exist, or you need access to create one.
  • Decide the employee's data reach before you pick a role: a single center, a zone, or the whole organization. This is the part that is awkward to change later.

Choose the right default role

Role Assign it to
Owner Complete access to all data and capabilities. The Owner can also modify the default roles and permissions themselves.
Administrator Assigned at the organization level, gives access to organization-level settings; assigned at the center level, gives access to center-level settings. Admin is the full-access profile β€” it provides broad access without the ability to redefine default roles.
Zonal Manager Almost the same access as a Manager, but across every center in a zone. Use this as the narrower alternative to Owner when someone needs broad cross-center access but should not be able to redefine roles.
Manager Your center's manager. Grants extensive access to data and capabilities.
Supervisor More than a receptionist, less than a manager β€” manage appointments, check staff in, manage issues, and create purchase orders.
Receptionist Booking appointments through the Appointment Book and collecting payments.
HR Manager Full access to employee data for attendance, performance, and employee management.
Marketing Manager Staff who create, deploy, and track discounts, memberships, promotional packages, campaigns, and loyalty programs.
Inventory Manager Staff responsible for inventory β€” tracking product checkouts and maintaining stock levels.
Accountant Access to administrative reports.
Therapist Your service providers. They can sign in and see a dashboard with their own monthly schedule, appointments, and payroll details.
Monitor Read-only access to the Appointment Book. Useful for a screen displayed in an employee breakroom.
Authentication An employee who only needs to authenticate a machine with their credentials, and nothing else.
Admin Staff Employees whose jobs do not require Zenoti access, but who you still want in Zenoti so you can manage their schedules, track performance, and check them in.

Note: Two defaults are worth respecting. Receptionist, Manager, and Owner can view the Appointment Book by default. Access to the Inventory module should be given only to the Inventory Manager and Owner roles.

Important: These are illustrations of the roles that ship with Zenoti. They are not a list of what is guaranteed in every account β€” administrators can customize any default role, so the actual permissions in your account may differ. The Owner role is the only role that can redefine the default roles themselves. If someone needs broad cross-center access without the ability to redefine roles, assign Zonal Manager or organization-level Administrator instead.

How effective permissions are calculated

When an employee works at a particular view β€” organization level, zone level, or center level β€” Zenoti evaluates their permissions in two steps.

Step 1: Filter role assignments by view scope

Zenoti looks at the view mode the employee is currently working in and keeps only the role assignments that are applicable to that scope:

  • At the organization level β€” only roles assigned at the organization level (with no center and no zone attached) are included.
  • At the zone level β€” organization-level assignments and any assignments matching that zone are included.
  • At the center level β€” organization-level assignments, matching zone-level assignments, and that specific center's assignments are all included.

Step 2: Calculate the union of permissions

Once the applicable assignments are identified, Zenoti combines them: a permission granted on any in-scope role assignment is granted to the employee for that session context. Holding the same permission on two roles does not increase access β€” it confirms it.

What this means in practice

A permission granted by a role that is assigned to one center has no effect while the employee is working at the organization level or at a different center. This is the most common reason an employee appears to hold a permission on paper yet cannot exercise it in a given context. Before assuming a permission is missing from the role, verify which level the role granting it is assigned at and compare it to the view mode the employee is currently working in.

Note: If a reviewer holds a Forms Review permission and still cannot mark forms as reviewed, check which level the role granting that permission is assigned at and compare it to the view mode the reviewer is working in. See How effective permissions are calculated for the scope rule, and see the Forms Review permission entry in Manage form reviews for additional context.

Assign a role to an employee

  1. Create or open the employee profile.
  2. In the Role/Permissions section, select the role or roles the employee needs.
  3. Save.

The employee inherits every permission attached to the roles you assigned β€” but only the assignments that apply to the level they are working at count. See How effective permissions are calculated.

Give a manager Owner-level access

Assigning Owner is a deliberate act. Select Owner in the Role/Permissions section of that employee's profile. The Owner role carries complete access to all data and capabilities, and it is the only role that can change the default roles and permissions themselves.

If someone needs broad access across centers but not the ability to redefine roles, Zonal Manager or organization-level Administrator is the narrower alternative. Admin is the full-access profile for administrators who need wide-ranging access without Owner-level role editing rights.

Change what a role can do

  1. Go to Configuration > Security and select Security roles.
  2. Select the role to edit.
  3. Enable or disable permissions.
  4. Select Save, and tell the affected employees what changed. A permission change takes effect for everyone holding that role.

To change the same permission across many roles at once, see Bulk security role permission update.

Things to know

  • Defaults may already have been changed. Administrators can customize any default role, so the actual permissions in your account can differ from the summaries above. Treat this as a starting map, not a guarantee.
  • Roles differ in reach, not only in power. Some grant access only at the center level; others β€” Zonal Manager, or Administrator at the organization level β€” span multiple centers. The level at which a role is assigned determines where it takes effect.
  • Roles are also ranked, and rank limits who a user can see. Security roles carry a rank, and that rank controls which employees appear to a user in the employee list. See Role rank and employee visibility below.
  • Some capabilities need more than a role. Certain advanced features require separate feature enablement before the permission has any effect.
  • A permission can be granted and still not apply. What decides it is the level the role was assigned at, compared with the level the employee is working in. A role assigned at a single center is not counted while that employee works at the organization level, so the permission appears to be missing even though the role holds it. Switch to the center, or grant the permission on an organization-level assignment.
  • Owner assignment is the exception, not the rule. Because the Owner role can redefine default roles for the entire account, assign it only when that capability is genuinely needed. For broad access without that authority, use Zonal Manager or organization-level Administrator.

Role rank and employee visibility

Every security role carries a rank, and rank decides which employees a user can see in the employee list:

  • A user does not see an employee who holds a role ranked above the user's own highest-ranked role at that center.
  • A user also does not see an employee who holds an organization-level role ranked above the user's highest-ranked role at that center.
  • Roles of equal rank see each other.

The default roles in rank order, from highest to lowest:

  1. Admin
  2. Owner
  3. Authentication
  4. HR Manager
  5. Administrator
  6. Accountant
  7. Manager, Zonal Manager, and Monitor (these three share the same rank)
  8. Marketing Manager
  9. Inventory Manager
  10. Supervisor
  11. Receptionist
  12. Therapist
  13. Admin Staff

Note: A role's rank cannot be changed on screen. If a user needs to see employees who are currently hidden from them, assign a higher-ranked role rather than looking for a rank setting to edit.

For the full set of rules that govern what appears in the employee list, see Employee listing.

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