Tenant settings that change behaviour
Heysen runs several agencies on one platform. Anything that differs between them — who is licensed, how policies are attributed, whether a data feed is enabled — is a tenant setting, not a separate deployment.
Where settings live
Section titled “Where settings live”| Surface | Reach |
|---|---|
| SaaS Admin | settings for your own agency |
| Platform Admin | the same settings, across tenants, for Heysen platform operations |
Platform operations can see and change a tenant’s settings from the tenant list. Agency administrators see their own. Both write to the same place, so a change made in one surface shows up in the other.
The switches worth knowing
Section titled “The switches worth knowing”| Setting | Scope | What it does |
|---|---|---|
| Insurance data feed | tenant | Master switch for the agency’s data-feed section: menus, pages, and sync endpoints. With no stored value, the section is off. |
| Manual policy-agent mapping | tenant | When on, newly imported policies wait for a human to confirm the producing agent instead of importing directly. With no stored value, this is off. |
Two properties are worth internalising:
- Absence means off. A tenant with no stored value for a switch is running with it off. This is not the same as a switch whose value could not be read — see below.
- Switches are not retroactive. Turning a switch off stops new work from flowing through it; it does not undo or release work that is already waiting. Queue items stay queued until somebody decides them.
When a switch cannot be read
Section titled “When a switch cannot be read”If the platform fails to read a switch value, the page shows the state as unknown and the control is disabled rather than defaulting to “off”. A default of “off” would be worse than a visible failure: one click could silently remove a protection from a tenant that actually had it on, and nothing in the UI would say so.
If you see the unknown state, refresh and try again. If it persists, it is a platform-side problem, not a setting you should work around.
Turning the feed off
Section titled “Turning the feed off”Before switching the data-feed section off for a tenant, confirm nothing is mid-flight. Turning the master switch off while an import is running removes the pages and endpoints from under it, and the tenant’s operators lose visibility of the run rather than seeing it stop cleanly.
A note on permissions
Section titled “A note on permissions”Operator capabilities are split into separate permissions rather than one “admin” flag: viewing a page, changing a switch, and each kind of decision are granted independently. This is why a colleague can open the mapping queue and still not be able to confirm an item.
When something is missing from the UI, check the permission before assuming the feature is broken. A control you lack permission for is generally absent, whereas a control that is disabled is telling you something about state.