How configuration is inherited

Which levels (tenant, centre, doctor, service) apply to each kind of setting, how values combine, and what happens when you save at centre or doctor level.

LeapHealthOS lets you set a rule once for your whole organisation and then change it for one centre or one doctor. Which levels are available depends on the kind of setting: appointment rules can go down to a single doctor or service, billing rules stop at the centre, and journey rules apply to the whole organisation only. This page explains the levels, how values combine, and the pitfalls to avoid. It is for administrators and implementation staff who plan settings.

The levels

Level	Shown on screen as	Covers
Platform default	The values in a form where nothing is saved	Built-in values that apply when nothing is saved
Tenant	Tenant (Global)	Your whole organisation
Centre	Centre	One centre
Department	Department	One department in a centre. Has no effect yet (see below)
Doctor	Doctor	One doctor
Service	No screen	One priced service. Set up by your implementation team

The more specific level wins. For appointment settings the order, from broadest to most specific, is platform default, Tenant, Centre, Doctor, Service.

Which levels each kind of setting uses

Settings	Where you edit them	Tenant	Centre	Doctor	Service
Appointment rules	System Settings > Appointments	Yes	Yes	Yes	Yes (no screen)
Slot rules	System Settings > Slot Engine	Yes	Yes	Some settings	No
Billing	System Settings > Billing	Yes	Yes	No	No
Package policy	No screen (cannot be changed yet)	Yes	Yes	No	No
Journey settings	System Settings > Journeys	Yes	No	No	No
Escalation policies	System Settings > Organisation	Yes (organisation)	Yes	No	No
Follow-up and repeat rules	Doctor Configuration	No	No	Yes	No

Department-level values have no effect for any of these.

Appointment rules

How an appointment setting is chosen

1
Platform default
The built-in value, for example a 10-minute hold.
Outstarting value for every field
2
Tenant
Replaces the platform default for every field saved at Tenant level.
InTenant (Global) save on the Appointments tab
3
Centre
Replaces the tenant value for every field saved for that centre.
Inthe centre of the appointment
4
Doctor
Replaces the centre value for every field saved for that doctor.
Inthe doctor of the appointment
5
Service
Service-level values set by your implementation team. There is no screen for these yet.
Inthe priced service being booked
Outthe rules used for this booking

One exception: Required Patient Fields takes effect at Tenant level only. Centre and doctor values for that field have no effect.

Slot rules

Some Slot Engine settings can be set per doctor. Others apply per centre only.

Slot Engine settings	Levels that take effect
Buffer Between Slots, Default Per Slot, Overbooking Enabled, Overbooking %, Fallback SKU ID	Tenant, Centre, Doctor
Walk-In Reserve, Booking Rules, Sort By, Capacity Check Mode	Tenant, Centre. Doctor values have no effect

Per-patient booking limits appear on both the Slot Engine and Appointments tabs. When an appointment is booked, the Appointments tab value applies, and the Slot Engine value is used only where the Appointments tab field is empty. See Appointment and slot settings.

Billing and package policy

Billing settings take the Tenant value unless the bill's centre has its own. A change applies to bills created afterwards. The package policy (what happens when a package expires or is cancelled) follows the same Tenant and Centre pattern. See Billing and package settings.

Journey settings

Journey settings exist at Tenant level only. When you open the Journeys tab, the level switches to Tenant (Global) and the picker is locked. A journey's own step settings, such as a cooldown on the Start node, take precedence over the tenant default for that journey.

Escalation policies

Escalation policies are saved for the organisation or for one centre on the Organisation tab. A centre's list replaces the organisation list completely. It does not add to it. See Where tasks come from.

Follow-up and repeat rules

The follow-up window, allowed follow-up visits and repeat rules are set per doctor on the Doctor Configuration screen. Your implementation team can also set organisation-wide or centre-wide maximums for these, which cap the doctor's values. There is no screen for the maximums yet. See Doctor onboarding and configuration.

How values combine

Levels combine field by field, not tab by tab:

A field saved at a more specific level replaces the broader value for that field only.
A field left empty at a more specific level keeps the broader value. Leaving a limit empty at Centre level therefore does not remove a Tenant limit.
A list, such as Who Can Cancel or a set of escalation policies, replaces the broader list as a whole.

Saving at centre or doctor level writes a full copy

The Slot Engine, Appointments and Billing tabs save every field on the tab, using what the form shows. At a level where nothing is saved yet, the form shows platform defaults, not the tenant's values. So the first time you save a centre or a doctor, it gets its own value for every field on that tab, and from then on it no longer follows the Tenant level for any of them.

To avoid surprises:

Settle the Tenant values first.
When you open a centre or doctor, re-enter every tenant value you want to keep before you save.
After you change a Tenant value later, check each centre and doctor that has been saved. A centre or doctor cannot be switched back to following the tenant.

The Journeys tab works differently: it saves only the fields you override.

A worked example

Your Tenant saves Buffer Between Slots = 10 minutes and Max Advance Booking = 60 days.

You open Centre City Clinic on the Slot Engine tab. The form shows the platform defaults: Buffer 5, Max Advance Booking 90. You change Buffer to 0 for this busy centre and click Save without touching anything else.
City Clinic now has Buffer 0 and Max Advance Booking 90, along with its own value for every other field.
Patients at City Clinic can book 90 days ahead, not 60.
Next month you change the Tenant's Max Advance Booking to 30 days. Other centres follow. City Clinic still allows 90.

To fix this, open City Clinic, set Max Advance Booking to the tenant value and save.

Department level

Department-level settings have no effect yet

System Settings lets you pick Department and save settings there, but they do not affect bookings, slots or billing yet. Use Centre or Doctor level instead.

Doctor setup and the Doctor level

A doctor's slot settings entered during doctor setup are the same settings you see at Doctor level on the Slot Engine tab. Saving the Slot Engine tab at Doctor level replaces what was entered during doctor setup, and changes made during doctor setup do not appear in Config History. Pick one place to manage a doctor's slot settings and keep to it.

What is not inherited this way

Some settings that look similar follow their own rules:

Appointment length comes from the doctor's service settings, then the centre's service settings, then the doctor profile, then the service's default duration. It is not a System Settings field. See How slot search works.
Working hours belong to each centre. Centre holidays have no screen and do not affect bookings yet. See Centres and clinic configuration.
Notification rules have their own Organisation and Centre tabs, and a centre rule can override, defer to or add to the organisation rule. See Notification rules.
Tenant registries are one list per organisation, with no centre or doctor versions. See Tenant registries reference.

When a change takes effect

A saved change applies to the next booking, slot search, bill or journey step straight away. Appointments that already exist keep the approval, hold duration, who can cancel, reason required and booking limit rules from when they were booked. Refund, reschedule, check-in, no-show and completion rules apply as they are at the time of the action, so they affect existing appointments too.

configurationinheritancehierarchylevelsoverridetenantcentredoctor