RBAC β Default Permissions Back-fill for Existing Organizations
When AI Retention Manager was introduced, organizations already live on Zenoti did not automatically receive the security object and permission actions needed to control access to the dashboard. This article explains how Zenoti's one-time back-fill process adds the AI Retention Manager security object to those organizations and which security roles receive which level of access.
Audience: Zenoti administrators who manage security roles and need to understand how access to AI Retention Manager is established for organizations that were provisioned before the feature was released.
Before you begin
- You must have access to Configuration > Security > Security roles in Zenoti to review or adjust role permissions after the back-fill has run.
- The back-fill runs automatically as part of deployment. You do not trigger it manually.
- Review your organization's security roles before and after deployment if you need to confirm which roles received which permissions.
Permission: AI Retention Manager security object β View to open the dashboard and read it; Edit to create target segments, refresh member lists, and send guests to AI Lead Manager. Set per role at Configuration > Security > Security roles.
Steps
Understand what the back-fill does
The back-fill process adds the AI Retention Manager security object and its two permission actions β View and Edit β to your organization's security configuration if they are not already present.
The two permission actions are:
| Permission action | What it allows |
|---|---|
| View | Open the AI Retention Manager dashboard and read all data shown on it. |
| Edit | Create target segments, refresh member lists, and send guests to AI Lead Manager. |
Understand which roles receive which permissions
When the back-fill runs, it assigns permissions based on each role's characteristics. The following table describes the assignment logic:
| Roles that receive View + Edit | Roles that receive View only |
|---|---|
| Owner | All roles that can open admin pages |
| Marketing Manager | Therapist |
| Administrator | |
| Center Owner | |
| Franchise Manager |
- View + Edit is granted to roles named Owner, Marketing Manager, Administrator, Center Owner, and Franchise Manager.
- View only is granted to every role that has permission to open admin pages, and to the Therapist role.
- Any role that does not fall into either group above receives no automatic grant and retains whatever access an administrator later configures manually.
Note: "Admin pages" refers to roles that are configured to allow opening administration screens in Zenoti. The back-fill uses this characteristic to identify which roles should receive at least View access to the dashboard.
Understand how the back-fill protects existing grants
The back-fill is designed to run exactly once per organization and to never overwrite manual changes you have already made:
- On first execution, the back-fill records a snapshot of any existing rows for the AI Retention Manager security object into a backup table before making any changes.
- On all subsequent deployments, the process detects that the backup table already exists and skips the insert entirely. This means manually cleared permissions are not silently restored on the next deploy.
- The back-fill also skips any individual role that already has a row for the AI Retention Manager security object, so explicit grants you have configured are never overwritten.
Important: If you manually remove a permission from a role after the back-fill has run, that change is permanent. The back-fill will not restore it on future deployments.
Verify and adjust permissions after the back-fill
After deployment, confirm that the access levels match your organization's intended configuration.
- In Zenoti, navigate to Configuration > Security > Security roles.
- Select a role to review.
- Locate the AI Retention Manager security object in the role's permission list.
- Confirm that View and/or Edit are set as expected for that role.
- Adjust the permissions if the default assignment does not match your organization's access policy.
- Select Save changes to apply any adjustments.
Worked example: Your organization has a custom "Front Desk Manager" role that can open admin pages. After the back-fill runs, this role receives View access to AI Retention Manager. You decide that Front Desk Managers should also be able to create target segments, so you navigate to Configuration > Security > Security roles, open the Front Desk Manager role, enable Edit on the AI Retention Manager security object, and select Save changes.
Tips
- Review all roles that received View + Edit access and confirm that the five named roles (Owner, Marketing Manager, Administrator, Center Owner, and Franchise Manager) align with your organization's intended access policy. If any role should not have Edit, remove that action at Configuration > Security > Security roles.
- If you add new security roles after the back-fill has run, those roles will not automatically receive AI Retention Manager permissions. Assign View and/or Edit manually for each new role that requires dashboard access.
- To prevent dashboard visibility for a particular role entirely, remove both View and Edit from that role's AI Retention Manager security object. Removing View also prevents the role from opening the dashboard, regardless of the Edit setting.
Troubleshooting
A role that should have access cannot open the AI Retention Manager dashboard.
The back-fill may have skipped this role because it already had a row for the AI Retention Manager security object with no permissions set, or the role was created after the back-fill ran. Navigate to Configuration > Security > Security roles, select the role, find the AI Retention Manager security object, and enable View. Select Save changes.
A role has Edit access but should only have View access.
The role matched one of the five named profiles (Owner, Marketing Manager, Administrator, Center Owner, or Franchise Manager) and received View + Edit automatically. Navigate to Configuration > Security > Security roles, select the role, remove Edit from the AI Retention Manager security object, and select Save changes.
A permission that was manually removed before deployment was restored after a new deployment.
This should not occur once the back-fill has run at least once, because the backup table prevents subsequent executions from inserting rows again. If permissions appear to have been restored, confirm that the backup table was created during the first deployment by contacting Zenoti Support, who can verify the back-fill execution history for your organization.