Configure security settings
Security settings control access, authentication policies, and data protection rules for your organization. You manage security roles and permissions, PII export controls, password policies, geographic access restrictions, session management, and account lockout rules. All security settings are organization-level only β there are no center-level overrides.
Before you begin
- You need administrator access at the organization level.
- Security settings affect all centers in your organization.
- Password policies are dynamically loaded from the policy engine and may vary based on your organization's configuration.
- Some sections require specific feature flags to be enabled.
Permission: Organization administrator access β these settings open for roles that carry organization-level administrator rights, such as the default Owner and Administrator roles. The role editor has no separate check box for this: the Organizations row in the Administrator section reads No applicable permissions.
On this page
- Navigate to security settings
- Security roles
- Guest permission rows
- PII export settings
- Password rules
- Country restrictions
- Security settings
- Tips
- Related articles
Navigate to security settings
- Navigate to Configuration > Security.
- The settings page displays all available sections based on your permissions and active feature flags.
Security roles
The Security roles section lets you define roles, assign permissions, and control what each employee can see and do in Zenoti.
| Setting | Type | Description |
|---|---|---|
| Security roles | Manager (embedded) | Embedded security role management interface. Create, edit, and delete security profiles. Assign permissions per module and action. |
Understanding security profiles
Security profiles are named sets of permissions. The profile names you see in your organization are examples of common profiles β they are not a fixed set that ships with every tenant. Your organization may use different names or a different number of profiles.
Admin is the profile that carries full access to all modules and settings. If you want to give a manager owner-level rights β so they can configure any setting, view all reports, and perform any action β assign them the Admin profile.
Other common profile examples include:
- Manager β center-level management with reporting access
- Receptionist β appointment booking and front-desk operations
- Therapist β service delivery and guest notes
Important: Creating or editing a security profile is only half the task. After you save the profile, you must assign it to the person on their employee record. For instructions, see Employee management FAQ.
Guest permission rows
The Guest Manager security object groups all permission rows that control what a role can do on guest profiles. Each row in this group controls a single action independently β for example, a role may be configured to allow editing a guest profile without allowing deletion of that profile.
The table below covers the most frequently asked-about rows in the Guest Manager section. It is a starter reference, not a complete inventory. For permissions not listed here, open the role in the role editor and check the Guest Manager section directly.
| Permission row | What it controls |
|---|---|
| Delete | Whether the delete option appears on the guest profile. When this permission is off for a role, the delete option is not shown. For guidance on deleting a guest profile, see Delete a guest profile. |
PII export settings
Configure limits and controls on the export of Personally Identifiable Information (PII) data.
| Setting | Type | Description |
|---|---|---|
| PII Export Settings | Manager (embedded) | Configure export quotas and MFA requirements for data exports containing sensitive guest or employee information. Set per-role record limits for PII exports. |
PII export controls help your organization comply with data protection regulations by:
- Setting maximum record counts per security role for PII exports
- Requiring MFA verification before allowing PII data downloads
- Supporting role-based export permissions
Password rules
Password rules control password complexity, expiration, reuse restrictions, and lockout behavior. The rows below appear on the Password rules page.
| Setting | Type | Description |
|---|---|---|
| Enforce minimum password length | Toggle | Requires passwords to meet a minimum character count. |
| Enforce maximum password length | Toggle | Caps passwords at a maximum character count. |
| Do not use common and breached passwords | Toggle | Blocks passwords that appear in known breach databases. |
| Users cannot reuse the last five passwords | Toggle | Prevents employees from reusing recent passwords. |
| Set password to expire after a specified number of days | Toggle | Forces periodic password changes. When enabled, an employee whose password has passed that age is redirected at their next successful sign-in to the Change Password page rather than signed in. On that page, the employee must supply their username, their current password, and a new one. This redirect takes precedence over two-factor authentication and new-device verification. The employee experience for updating an expired password is documented in the article Update an expired password. |
| Add CAPTCHA after a specified number of failed login attempts | Toggle | Displays a CAPTCHA challenge after repeated failures. |
| Lock account after a specified number of failed login attempts | Toggle | Locks the account after the configured number of failures. |
| Unlock account after a specified number of minutes | Toggle | Automatically unlocks a locked account after a set duration. |
| Two-factor authentication with text verification code | Toggle | Requires a one-time code sent by text message at login. |
| Two-factor authentication with email verification code | Toggle | Requires a one-time code sent by email at login. |
| Two-factor authentication with authenticator app | Toggle | Requires a code from an authenticator app at login. |
| Challenge with 6-digit verification code when a new machine or browser is detected; code is sent via email | Toggle | Triggers an additional verification step on unrecognized devices. |
| Challenge with 6-digit verification code when a new machine or browser is detected; code is sent via text | Toggle | Same as above, delivered by text message. |
| Unlock with text verification code | Toggle | Allows account unlock via a text-delivered code. |
| Unlock with email verification code | Toggle | Allows account unlock via an email-delivered code. |
| Password must contain at least one number (0-9) | Toggle | Enforces numeric character inclusion. |
| Password must contain at least one lowercase letter (a-z) | Toggle | Enforces lowercase character inclusion. |
| Password must contain at least one uppercase letter (A-Z) | Toggle | Enforces uppercase character inclusion. |
| Password must contain at least one special character (# % $ etc.) | Toggle | Enforces special character inclusion. |
| Remind users to change their password before password expires | Toggle | Sends a reminder ahead of expiry. This toggle has effect only while Set password to expire after a specified number of days is also enabled, because the reminder is evaluated against the active expiry period. Enabling this reminder toggle alone β without the expiry toggle on β produces no reminder. |
| Enable Captcha in Forgot password page | Toggle | Adds CAPTCHA protection to the forgot-password flow. |
| Allow users to trust devices for a specified number of days | Toggle | Lets employees skip two-factor challenges on trusted devices for a configured period. |
| Send email alert upon new device login | Toggle | Notifies the employee by email when a login occurs from an unrecognized device. |
| Send email alert when a user logs in with a breached password | Toggle | Alerts the employee if their password appears in a known breach. |
| Enable key-in password update at employee profile | Toggle | Allows employees to update their password directly from their profile page. |
Country restrictions
Geographic access restriction settings that limit which countries can access your Zenoti system.
Note: Both settings in this section require the country restrictions feature to be enabled.
| Setting | Type | Description |
|---|---|---|
| Enable country restrictions | Toggle | Master toggle for geographic access restrictions. When enabled, only users from the selected countries can access the Zenoti web application. When disabled, the country selection list is hidden. |
| Allow users to access Zenoti web app only from these countries | Multi-select | Select which countries are permitted. Users attempting to log in from a country not in this list are blocked. Only visible when Enable country restrictions is enabled. |
Important: When you disable country restrictions, the allowed countries list is automatically cleared. If you re-enable the restriction later, you must re-select the allowed countries.
Security settings
General security configuration including session management and account locking.
| Setting | Type | Description |
|---|---|---|
| Logout inactive users after | Dropdown | Time before an idle session automatically expires and the user must log in again. Options: 5 minutes, 10 minutes, 15 minutes, 20 minutes, 25 minutes, 30 minutes, 45 minutes, 1 hour, 2 hours, 3 hours, 4 hours, 5 hours, 10 hours, or 24 hours. |
| Lock employee account and exit PIN mode after a specified number of failed login attempts | Toggle | Master toggle for automatic employee account locking after failed login attempts. When enabled, a numeric field appears to set the maximum number of failed attempts before the account locks. |
| Lock account and exit PIN mode after how many failed login attempts? | Number | Failed attempts allowed before the account locks. Appears when the row above is on. |
Tips
- Review security roles before granting access to new employees. Assign the least-privilege role that allows each employee to perform their job duties.
- To give a manager the same access as an owner, assign them the Admin profile β it carries full access to all modules and settings. Remember to save the profile assignment on the employee record after updating the profile itself.
- Set a reasonable session expiry timeout that balances security with usability. For front-desk workstations that are always supervised, a longer timeout may be appropriate. For shared or remote-access devices, use a shorter timeout.
- Enable account locking with a sensible failed-attempt limit to protect against brute-force password attacks without locking out employees who occasionally mistype their password.
- If your organization has data protection compliance requirements, configure PII export limits to restrict the volume of sensitive data that can be exported at one time.
- Geographic country restrictions provide an additional layer of protection for organizations that do not need global access. Enable this feature if your staff only logs in from specific countries.
- Password expiry reminders only take effect when the expiry policy itself is active. Enable Set password to expire after a specified number of days before turning on Remind users to change their password before password expires β otherwise no reminders are sent.