Multi-tenancy and app configuration
Understand how the customer mobile app is configured and published as a branded experience for each organization.
Before you begin
- This article describes how the app is configured for your organization. Configuration is managed by your Zenoti administrator.
- For organization settings, see organization settings documentation.
How multi-tenancy works
The customer mobile app is a multi-tenant platform. Each published app instance is configured specifically for one organization. When your organization's app is published to the App Store or Google Play, it contains your branding, service catalog, and feature settings. Guests download your branded app and interact only with your organization's data.
Platform availability
The app supports three platforms:
- iOS — Requires iOS 14 or later
- Android — Requires Android 12 or later
- Web — Accessible through supported web browsers
Organization-level feature configuration
Your organization controls which features are available to guests through configuration settings managed in the Zenoti admin portal. These settings determine what guests see and can do in the app, including:
- Whether appointment booking, queue, loyalty, memberships, packages, gift cards, and referral features are available
- Which booking modes are active (service-based or provider-based)
- Whether guests can cancel or reschedule appointments
- Whether the product shop, fitness module, and Zenoti Go are available
- Display preferences such as service pricing, service duration, member pricing, and tax-inclusive pricing
When a feature is not enabled for your organization, it does not appear in the app.
Center-level configuration overrides
If your organization operates multiple centers, each center can have its own configuration that overrides the organization-level defaults. Center-level settings control:
- Catalog visibility — Whether the center appears in the app's center list
- Appointment booking — Whether booking is enabled for that specific center
- Credit card requirements — Whether a saved card is required to book (not required, warn if not on file, or block if not on file)
- Booking date range — Earliest date guests can book, and temporary booking blocks
- Feature toggles — Queue, gift card sales, and service sales can be enabled or disabled per center
- Deposit settings — Each center can override the organization's deposit configuration
- Booking modes — Gender-based booking and shared booking can be set per center
When a center is configured to use organization-level settings, it inherits all defaults from the organization.