Publish Templates to Locations
Configuring a template in the Template Control Centre defines the values and the editability rules. Publishing is the separate act that sends those values to the locations you select. Until you publish, no location is affected — the template content sits at the org level only.
Publishing is deliberate by design. It gives you a moment to review exactly what will change at each location, select which locations to include in this rollout, and confirm before any live configuration is touched. You can configure a template over several sessions, preview the diff, and publish only when you are ready.
Who can publish templates: Org Admin, Account Owner.
Before you publish
Confirm the following before starting:
- The template content for each category is correct and reviewed. You can check it in Settings → Templates by selecting each category tab.
- The editability mode for each category is set to the right level for your operation (Locked, Customisable, or Independent). See Use Template Controls.
- You have identified which locations should receive this publish — all locations, a pilot group, or a specific branch.
Publish a template to locations
Switch to the organisation view
Use the location switcher in the top navigation to select the organisation rather than any individual location. The switcher shows your org name — for example, “AutoPrime Group” or “Midas Arabia” — at the top of the list.
If you do not see the organisation option, your account does not have Org Admin or Account Owner permissions.
Go to Settings → Templates
From the main navigation, go to Settings → Templates.
The Template Control Centre opens, displaying all configured categories as tabs.
Select the category you want to publish
Click the tab for the category you are publishing. For example, if you have updated the standard incentive scheme and want to push it to locations, click the Incentives tab.
Within the tab, you will see:
- The current template content
- The editability mode in effect
- A diff summary if the template has been updated since the last publish — this shows exactly what is new or changed
Review the diff before proceeding. If the diff shows unintended changes, navigate to the template editor and correct them now.
Click Publish to Locations
Click the Publish to Locations button at the top-right of the category tab.
A location picker opens. It lists every location in your organisation along with:
- A checkbox to include or exclude this location from the current publish
- The date and version of the last publish to that location
- Any flag indicating that the location has local overrides in this category (for Customisable mode)
Select the target locations
Check the boxes next to the locations that should receive this publish.
To send the template to every location in one action, click Select All at the top of the list. To target specific locations only, check them individually.
If you are publishing to a location that already has local overrides in a Customisable category, a small indicator appears next to the location name showing how many fields differ from the template. Review this — publishing will update the template baseline, and any overridden fields that conflict with the new template values will be reset to the template value. Fields that do not conflict with the update are preserved.
For Locked-mode categories, no override information is shown because local managers cannot make changes. The location will receive the template exactly.
Review the change summary
Before confirming, read through the change summary at the bottom of the picker. This lists:
- How many fields will change at each selected location
- For Customisable locations: how many local overrides will be affected by this publish
- For Locked locations: confirmation that the published values will overwrite the current location configuration
If the summary shows more impact than you expected — for example, a large number of overridden fields being reset at a Customisable location — consider whether those branches should be part of this publish or handled separately with a discussion first.
Confirm and publish
Click Publish. BayWise applies the template to all selected locations simultaneously.
A confirmation toast appears when the publish is complete. Each affected location’s settings are updated immediately — there is no delay or queue.
What happens at each location after publishing
The outcome at each location depends on the editability mode set for the published category.
Locked mode
The location receives the template values exactly. Every field in the category is set to the template value. Any configuration that existed at the location for this category is overwritten.
Location managers at these branches will see a blue banner in their settings panel for this category: “This configuration is managed by [Org Name]. Changes are not permitted at the location level.” All input fields are disabled.
Customisable mode
The template values become the updated baseline at the location. The behaviour for individual fields depends on whether the location has a local override for each field:
- Field has no local override: The location field is updated to the new template value.
- Field has a local override that does not conflict with the change: The local override is preserved. The template baseline is updated in the background but the local value continues to apply.
- Field has a local override that conflicts with the changed template value: The template value takes precedence. The local override is cleared and logged. The location manager receives a notification that one or more of their local settings were updated by a central publish.
Location managers see a grey banner: “This configuration is based on a template from [Org Name]. You can customise individual fields for this location.”
Independent mode
Locations with Independent mode for a given category are not affected by a publish to that category, even if you select them in the location picker. Independent means the template has no authority over that category at that location. The location picker will show Independent locations as greyed-out if you have selected only that category.
Publishing is not retroactive
Publishing a template changes the live configuration at the selected locations going forward. It does not alter historical records, completed jobs, or any incentive calculations already run for closed reporting periods.
If you publish an updated service catalog template, existing jobs booked under the previous catalog entries are unchanged. If you publish a new incentive scheme via the Incentives template, the new formula applies from the next reporting period boundary — the current period continues to run on whatever scheme was active when it started.
This boundary is important for payroll planning: if you intend a new incentive formula to apply from the start of next month, publish it before month-end rather than at the start of the new month.
Selective publishing vs. full rollout
Use “Select All” when rolling out a new incentive scheme to all branches simultaneously — for example, a company-wide rate review at the start of a new financial year. Use selective publishing when trialling a change at one or two locations before committing to a full rollout. This lets you observe the effect at pilot branches, gather location manager feedback, and correct the template if needed before distributing to the wider network.
A common rollout pattern for franchise operators:
- Configure and publish to one or two pilot locations.
- Monitor for two to four weeks — check that the template values work as intended in practice, that no edge cases were missed, and that location managers at the pilot branches have no objections.
- If the pilot is successful, return to the Template Control Centre and publish to the remaining locations with Select All.
- If the pilot reveals issues, update the template content first, then re-publish to the pilot locations to confirm the correction, and only then proceed with the full rollout.
Publish history
Every publish is recorded in the publish history at the bottom of each category tab. The history shows:
| Column | What it records |
|---|---|
| Date and time | When the publish was executed |
| Published by | The user account that performed the publish |
| Locations | How many locations were included |
| Changes | How many fields were updated across all included locations |
The publish history provides an audit trail for compliance reviews and makes it straightforward to identify when a configuration change was distributed and who authorised it.
Common questions
I published to the wrong locations. Can I undo it? There is no automatic rollback. If you published incorrect values, update the template content to the correct state and publish again to the affected locations. If the incorrect publish was to a Locked category, the correction will overwrite the error. If it was to a Customisable category, the correction will update the baseline — any overrides that were cleared by the erroneous publish will need to be reapplied by location managers.
Can I publish one category without affecting the others? Yes. Each category tab has its own Publish button. Publishing Operating Hours does not publish Service Catalog, Incentives, or AI Settings. You control each category independently.
A location manager says they are not seeing the published values in their settings. What should I check? First, confirm the publish completed without error — check the publish history for the category. Second, verify that the location is assigned to the template, not just listed in the publish picker. A location that was checked in the picker but not assigned to the template will not receive the publish. Open the location assignment panel in the relevant category tab and confirm the location has an assigned status.
Does publishing notify location managers automatically? BayWise logs the change to each affected location’s settings history and displays the managed configuration banner where applicable. It does not send email or push notifications to location managers. If your operating practice requires location managers to be informed before configuration changes, communicate this through your own channels before publishing.
Can I schedule a publish for a future date? Not currently. Publishes take effect immediately when you confirm. For time-sensitive configuration changes — such as a new rate structure that should take effect on the first of the month — plan your publish timing accordingly.