Manage employee codes
Each employee has a unique code within the organization, used for quick lookup at Point of Sale (POS), time clock, and external integrations. This article covers code management workflows, including manual assignment, auto-generation, lookup behavior, and editing restrictions. For initial setup, see Create and manage employees.
Audience: Administrators who configure employee profiles and front desk staff who manage employee records.
On this page
- Before you begin
- Manual code assignment
- Auto-generated codes
- Code-based lookup
- Editing restrictions
- Tips
- Troubleshooting
- Related articles
Before you begin
- At least one employee record must exist in the organization.
- To edit employee codes on non-consultant profiles, you need the following permission:
Permission: Edit Employee Code (under Other Settings) β Required to modify employee codes on non-consultant employee profiles. Grant it on the Other Settings row in the Employee Manager section of the security role (Configuration > Security > Security roles > the role > Permissions).
- If auto-generation is enabled for your organization, the Employee Code field is pre-filled when you create a new employee. You can override the generated code subject to uniqueness validation. Auto-generation settings are configured at Configuration > Employee > Essentials. See Configure employee settings.
Manual code assignment
When auto-generation is not active, you enter a code manually on the employee profile.
Assign a code to a new employee
- Navigate to Employee > Employees.
- Click Add to open the employee creation form.
- In the Employee Code field, enter a code for the employee.
- Complete the remaining required fields and save the record.
Zenoti validates uniqueness in real time as you type. If the code is already assigned to another employee in the organization, the following message appears:
Another user account with the same Employee code exists. Please provide a unique Employee code and retry.
Correct the code before saving.
Edit a code on an existing employee
Important: Before editing a code, confirm that the employee profile does not have the Consultant flag set. If it does, the Employee Code field is locked regardless of your permissions. See Editing restrictions.
- Navigate to Employee > Employees.
- Open the employee's profile.
- On the General tab, locate the Employee Code field.
- Enter the new code.
- Save the profile.
Zenoti validates uniqueness server-side on save in addition to the real-time check. If a duplicate is detected at save time, the system prevents the record from being updated and displays a validation error.
Worked example: A center has two employees β Alice (code A001) and Bob (code B001). An admin attempts to change Bob's code to A001. Zenoti displays the duplicate-code error immediately and Bob's record is not saved until a unique code is entered, such as B002.
Auto-generated codes
When auto-generation is enabled at the organization level, Zenoti automatically assigns a code to each new employee using a configured seed value, prefix, and numeric format.
How auto-generation works
- When a new employee record is created, Zenoti checks whether auto-generation is active.
- If active, the Employee Code field is pre-filled with the next code in the configured sequence.
- The generated code follows the pattern defined in the organization settings: prefix + incrementing number padded to the configured length.
- You can override the generated code with a manual entry, subject to uniqueness validation.
Configure auto-generation settings
Auto-generation is configured at Configuration > Employee > Essentials. The settings include:
- Auto-generate employee code β Enables or disables automatic code generation.
- Enter the number with which employee codes should begin β Sets the seed value for the numeric portion of the code.
For full configuration steps, see Configure employee settings.
Note: Disabling auto-generation after codes have been issued does not change existing codes. New employees created after disabling must be assigned codes manually.
Code-based lookup
Employee codes serve as stable identifiers across several Zenoti surfaces:
- POS quick access β Identify the provider during checkout when the Enforce employee passcode in POS setting is active.
- Time clock check-in β Employees enter their code at a terminal or kiosk to check in or check out.
- External integrations β The employee code is a stable, organization-wide identifier used when syncing employee data with external systems.
Zenoti retrieves the matching employee record when a code is entered. If the code does not match any active employee, no record is returned.
Editing restrictions
Two independent gates control whether the Employee Code field is editable for a given employee profile.
Consultant flag gate
When an employee profile is flagged as a Consultant and a code has already been assigned, the Employee Code field is locked and cannot be edited β even if you hold the Edit Employee Code permission.
This restriction applies specifically to consultant profiles and is separate from the permission check. Removing the consultant designation from the profile is a prerequisite to editing the code.
Note: An external consultant is not a regular employee. Consultants do not appear in employee schedules or employee reports, and check-in and check-out are not supported for consultant profiles.
Edit Employee Code permission gate
For non-consultant employee profiles, the Edit Employee Code permission controls access to the field. Without this permission, the field is read-only.
Permission: Edit Employee Code (under Other Settings) β Required to edit employee codes on non-consultant profiles. Grant it on the Other Settings row in the Employee Manager section of the security role (Configuration > Security > Security roles > the role > Permissions).
The two gates are independent: holding the Edit Employee Code permission does not unlock the field on a consultant profile whose code is already set.
Tips
- Use a consistent prefix pattern to make codes meaningful at a glance β for example, a center or job abbreviation followed by a number. Auto-generation supports a configurable prefix for this purpose.
- Keep codes short and numeric where possible. Numeric codes are faster to enter at POS terminals and time clocks, reducing checkout and check-in time.
- Do not reuse codes from terminated employees. Although Zenoti enforces uniqueness among active records, reusing a former employee's code can cause confusion in historical reports and external integrations. Assign a fresh code to new employees.
Troubleshooting
The Employee Code field is greyed out for one employee but editable for others.
Check the following in order:
- Check whether the employee is flagged as a Consultant. Open the employee profile and look for the Consultant designation. If the employee has a consultant flag and a code is already assigned, the field is locked regardless of permissions. Removing the consultant designation is a prerequisite to editing the code.
- Verify the Edit Employee Code permission. Navigate to Configuration > Security > Security roles > the role assigned to your account > Permissions. Confirm that Edit Employee Code is enabled under the Other Settings row in the Employee Manager section.
- Confirm that auto-generated codes are not in effect (for non-consultant profiles). If auto-generation is active and the employee was created while it was enabled, the code field may appear locked during creation. You can still override the code by entering a unique value manually before saving the new record.
The system displays "Another user account with the same Employee code exists" when saving.
The code you entered is already assigned to another employee in the organization. Enter a different, unique code. Employee code uniqueness is enforced across the entire organization β codes that are unique within a single center but shared with another center's employee are not valid.
The Employee Code field is not visible on the employee creation form.
If your organization uses a simplified onboarding flow, some fields may be presented differently. Check with your administrator to confirm the onboarding configuration in use at your organization.