ZenotiHelp

Configurations overview

ZTZenoti Docs Team Updated September 5, 2026 8 min readGuide

Zenoti's configuration system provides a centralized interface for managing all administrative settings across your organization and centers. The system uses a dynamic approach that adapts the interface based on your organization's active features and permissions.

Before you begin

  • You need access to Configuration to view and manage configurations.
  • Settings visibility and edit access are controlled by your security profile and the features enabled for your organization.

On this page


How it works

All configuration is accessible from Configuration. The page uses a sidebar on the left to navigate between configuration areas and a content panel on the right to display the settings for the selected area. The interface is data-driven: settings are defined in a centralized schema, and the page renders each section, subsection, and field dynamically based on those definitions.

Settings hierarchy and scoping

Settings operate at different organizational scopes:

  • Organization level β€” Global defaults that apply across all centers.
  • Zone level β€” Regional settings that override organization defaults for centers in a zone.
  • Center level β€” Location-specific overrides that take precedence over both zone and organization values.

Centers inherit organization defaults automatically. You only need to configure center-level overrides where a center's behavior must differ from the default.

Dynamic interface

The settings interface adapts based on active features and user permissions. Fields, validation rules, and dependencies are declared in configuration definitions rather than hardcoded. This keeps the interface clean by showing only the settings that are relevant and permitted for the current user and scope.

Cross-setting dependencies

Many settings have dependency relationships. Enabling a master toggle may reveal additional child settings. Changing a dropdown value may enable or disable related fields. These relationships are managed automatically β€” the system shows, hides, enables, or disables dependent settings as you make changes.

Contextual help

Each setting can display inline help text adjacent to the field, providing descriptions and guidance without navigating away from the settings page. This help content is keyed to the setting and appears as a tooltip or help panel.

Pre-save validation

Some settings perform validation before saving. Client-side validation runs immediately when you click Save, checking inputs such as format and uniqueness. If client validation passes, the save request proceeds to the server, where additional checks β€” such as database uniqueness β€” are performed. If either validation step fails, the system displays an error message and no settings are persisted.

Key features

  • Schema-driven interface β€” Settings definitions control rendering, validation, and field relationships without requiring code changes.
  • Hierarchical scoping β€” Organization, zone, and center-level settings with cascading overrides.
  • Permission-based visibility β€” Settings appear only when you have the required permissions and the relevant features are active.
  • Settings search β€” Find any setting by name or keyword using the built-in search function.
  • Contextual help β€” Inline help text explains what each setting does without leaving the page.
  • Dependent settings β€” Enabling or changing one setting automatically affects related settings.
  • Zenoti Labs β€” Discover and enable preview features through the dedicated Labs section in the sidebar.

Settings categories

The sidebar organizes all configuration into the following groups:

Business details

  • Business details β€” organization identity, branding, timezone, currency, and operating hours.

Master Data

  • Services, Products, Memberships, Packages, Fitness, Lockers β€” catalog-level settings for each item type.
  • Add ons β€” Zenoti Connect automated responder configuration.
  • Product header β€” separate product organization structure for centers with distinct product entities.

Bookings

  • Appointments β€” booking rules, scheduling, waitlist, provider requests, and the appointment book interface.
  • POS β€” invoice setup, checkout behavior, tips, prepaid cards, and receipt configuration.
  • Online booking β€” Webstore booking flow and guest self-service options.
  • Employee mobile apps β€” mobile app behavior for providers and front desk staff.

Employee

  • Employee β€” scheduling, commission, attendance, payroll, and performance settings.
  • Security β€” password policies, session management, and account security.

Guests

  • Guests β€” guest profiles, merge rules, communication preferences, and feedback.
  • Loyalty program β€” loyalty point earning, redemption, and tier rules.
  • Gift cards β€” gift card occasions, templates, numbering, and redemption behavior.
  • Marketing β€” campaign targeting, automation, and communication channels.
  • Opportunities β€” lead tracking and follow-up settings.
  • HyperConnect β€” cross-center guest timeline and communication sharing.

Notifications

  • Notifications β€” email, SMS, and push notification templates and triggers.

Payments and Inventory

  • Payments β€” payment methods, processing rules, employee payouts, and refund policies.
  • Inventory β€” inventory tracking and stock management.

Reports and Integrations

  • Reports β€” report access, scheduling, and default parameters.
  • Integrations β€” third-party integrations, API applications, and webhook subscriptions.
  • Accounting β€” accounting export and journal mapping.

Clinical

  • Forms β€” intake forms, consent forms, and form assignment rules.
  • Prescriptions β€” prescription settings and ePrescription portal configuration.
  • AI Scribe β€” AI-powered clinical charting setup.
  • Photo management β€” photo sequences and photo manager permissions.
  • Clinical setup β€” clinical rules and Treatment Hub configuration.
  • ePrescribe settings β€” ePrescription user and center management.

Dashboard

  • Setup dashboards β€” setup dashboard configuration and the organization checklist.

Note: The sidebar groups listed above reflect the 13 menu groups in the configuration system. Not all groups or items are visible to every user β€” visibility depends on your security role and the features active for your organization.

Settings documented in other categories

Some settings areas have their own dedicated help categories. For those areas, this category links out rather than duplicating the content:

Zenoti Labs

Configuration > Zenoti labs is a dedicated section where administrators can discover and enable innovation features before they become generally available. Zenoti Labs is available by default to Business Owners and Admins β€” no separate access request is required.

Each feature in Zenoti Labs is independently controlled. Enabling a feature activates its corresponding settings and menu items elsewhere in the system. For example, enabling Enable Employee Survey makes Employee > Employee survey available in the navigation.

The following features are currently available in Zenoti Labs. Because this list changes as features graduate or are withdrawn, the rows below reflect the page as of the date this article was last reviewed.

The page is a single-level list of toggles with a single Save button. There are no sections or drill-in pages within Zenoti Labs itself.

Feature Description
Enable Payments Dashboard Enables a dashboard view with comprehensive payment details and the flow of transaction activity over time.
Enable Smart Fraud Shield Automatically blocks suspicious payment attempts based on abnormal patterns β€” such as rapid retries, multiple cards from the same device, or high-risk activity β€” helping to prevent fraud and protect revenue without affecting genuine guests.
Enable Employee Survey Send surveys to employees.

Note: Zenoti Labs features are groupings within the existing Configuration menu. Enabling a feature here activates its corresponding settings and menu items β€” it does not create a separate configuration area.

Important: Enable New Booking Experience is not a Zenoti Labs toggle. It is configured under Configuration > Appointments.

Note: The page label in the sidebar is Zenoti labs (lowercase "l"). This matches the navigation entry you see in the product. Some older documentation uses "Zenoti Labs" with a capital L β€” both refer to the same page.

Support login and read-only access

When Zenoti support staff access your organization using a support login session, the settings page operates in a restricted mode:

  • Standard settings sections are visible but save functionality is disabled β€” support staff can review settings without modifying production configuration.
  • The Zenoti Usage Checklist section, which is hidden during normal administrator sessions, becomes visible during support login. This section provides system health and usage information for diagnostic purposes.

Note: The Zenoti Usage Checklist is only visible during support login sessions. It is not accessible to regular administrators.

MyZen missed check-in requests

Administrators can allow employees to raise requests from the MyZen app to add a missed check-in or modify an existing one for a past day. This setting sits under Configuration > Employee > Employee attendance > Check in (center scope).

When the Allow employees to request missed checkin setting is enabled:

  • The Request changes to clock in option becomes available in the employee's MyZen schedule.
  • When an employee submits a missed check-in or clock-out correction request, the system routes the request to a manager for review and approval.

Employee PIN login

Administrators can enable employees to operate the appointment booking experience using a PIN instead of their full password. This setting is configured under Configuration > Appointments.

The relevant settings are:

  • Employee PIN login (organization level) β€” Enables PIN-based login for employees across the organization. When enabled, Require authorization with PIN to delete appointments and invoices appears, and the center row of the same name unlocks the center PIN rows.
  • Enable pin mode by default on entering appointment book (center level) β€” When enabled, PIN mode activates automatically when an employee accesses the Appointment Book, simplifying the login experience. This setting can be overridden at the center level.

Note: The Enable pin mode by default on entering appointment book setting is a center-level override. Each center can independently control whether PIN mode activates by default.

Membership revenue recognition in reports

An organization-level setting in the Reports section of Configuration controls whether three membership revenue-recognition values β€” Initial Revenue Recognition (IRR), Monthly Revenue Recognition (MRR), and Service Credit Revenue (SCR) β€” are included in report calculations and views. This setting is disabled by default.

When the setting is enabled, Zenoti uses the IRR, MRR, and SCR values in redemption, sales, and collection calculations across the reports that support them, including the Sales Accrual report, Sales Tax report, and related reports.

Any role with access to Administrator mode can enable this setting. No additional special permission is required beyond standard administrator access.

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