Bulk Security Role Permission Update
This article explains how to apply permission changes to multiple security roles at once using the bulk security role permission update procedure in Zenoti.
Important: This procedure operates at the organization level and modifies permission bits across all specified security roles in a single operation. Review your selections carefully before proceeding β changes take effect immediately and apply to all affected roles.
Audience: Organization administrators who manage security roles and need to apply consistent permission changes across multiple roles simultaneously.
On this page
Before you begin
- You must have access to the Security settings area in Zenoti.
- Confirm that the security roles you want to update belong to your organization. Roles from other organizations or voided roles are excluded from processing and returned as invalid.
- Identify whether you are adding or removing a permission. The operation type determines how the update is applied:
- Add β grants the permission to roles that do not yet have it.
- Remove β revokes the permission from roles that currently have it.
- Verify the list of security role IDs you intend to update before initiating the procedure. Invalid or voided role IDs are not processed and are returned in the result set for your review.
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. Admin path: Configuration icon > Security > Security roles β organization scope only. The Security sub-menu does not appear when the scope selector is set to a center.
Steps
Understand how bulk permission updates work
The bulk security role permission update applies a single ADD or REMOVE operation to one or more security roles across your organization in a single atomic transaction. This means either all valid roles are updated successfully, or none are β there is no partial update.
The operation works as follows:
ADD operation β For each security role in your selection:
- If the role does not yet have a permission record for the specified security object, a new record is created with the permission granted.
- If the role already has a permission record but the specific permission bit is not set, the bit is set.
- If the role already has the permission, no change is made.
REMOVE operation β For each security role in your selection:
- If the role has the specified permission bit set, the bit is cleared.
- If the role does not have the permission, no change is made.
After the operation completes, the system returns a list of any security role IDs that were not processed. A role is excluded from processing β and returned as invalid β if it does not belong to your organization or has been voided.
Note: The bulk update applies to all security roles you specify. It does not affect roles outside your organization, even if their IDs are included in the request.
Apply a bulk permission update
- Click the Configuration icon in the main navigation.
- In the search field, type Security roles and select it from the results.
- Review the list of security roles in your organization.
- Identify the roles you want to update and note their role IDs.
- Determine the operation type β Add or Remove β and the specific permission you want to apply or revoke.
- Submit the bulk update by specifying:
- The list of security role IDs to update.
- The security object and permission pair to modify.
- The operation type: Add or Remove.
- After the operation completes, review the result set for any invalid security role IDs that were not processed.
Important: Place warnings before destructive actions. If you are removing a permission that affects front-desk staff or providers across multiple roles, verify the impact on daily operations before proceeding. Removing a permission takes effect immediately for all affected roles.
Review invalid security profile results
After a bulk update, the system returns a result set listing any security role IDs that were excluded from processing. A role appears in this list if:
- The role ID does not belong to your organization.
- The role has been voided.
For each invalid role ID returned:
- Verify the role ID is correct and belongs to your organization.
- Check whether the role has been voided by navigating to Configuration icon > Security > Security roles and searching for the role.
- If the role is voided and you need to apply the permission, restore the role first or create a new role with the appropriate permissions.
- If the role ID is incorrect, update your list and resubmit the bulk update for the corrected IDs.
Note: Invalid role IDs are returned for informational purposes only. The operation still completes successfully for all valid roles in your selection.
Worked example: Your organization has five security roles: Front Desk, Manager, Provider, Admin, and Owner. You submit a bulk ADD operation for the Add Loyalty Points permission across all five roles. The Owner role was voided last month. The system processes the four active roles β Front Desk, Manager, Provider, and Admin β and returns the Owner role ID in the invalid results list. You review the list, confirm the Owner role is voided, and decide no further action is needed.
Tips
- Audit before you update. Before running a bulk permission update, export your current security role settings so you have a reference point if you need to reverse any changes.
- Use ADD and REMOVE separately. If you need to both add one permission and remove another across the same set of roles, run two separate operations β one ADD and one REMOVE β to keep the changes clear and auditable.
- Check for voided roles first. If you know some roles in your list may be voided, review the Security roles page before submitting the bulk update to avoid unexpected entries in the invalid results list.
- Verify role ownership. Only roles belonging to your organization are processed. If you manage multiple organizations, confirm you are operating in the correct organization context before submitting.
Troubleshooting
Some role IDs appear in the invalid results list even though the roles exist.
The roles may belong to a different organization or may have been voided. Navigate to Configuration icon > Security > Security roles and search for each role by name or ID. If the role is voided, it will not appear in the active list. Restore the role or create a replacement before resubmitting.
The bulk update did not apply to any roles.
This can occur if all role IDs in your selection are invalid β either they do not belong to your organization or they are all voided. Review the invalid results list returned by the operation, correct your role ID list, and resubmit.
A permission I added is not visible on the Security roles page.
Changes take effect immediately, but the page may need to be refreshed. Navigate away from the Security roles page and return to reload the current state. If the permission still does not appear, verify that the ADD operation completed without errors and that the correct security object and permission pair were specified.