Managing Shared Configuration Across Tenants
Which settings can be pushed from a parent organization down to every tenant in a constellation, and which stay local.
Some settings make sense to standardize across every tenant in a constellation — branding, default modules, and security policies like minimum password length are common examples. Others, like a clinic's opening hours or local billing contacts, should always stay per-tenant.
From Settings > Organization > Shared Config, the parent organization can mark specific settings as constellation-managed. Once marked, that setting is pushed to every member tenant and locked from local editing — an individual tenant admin will see the value but not a way to change it, with a note explaining it's managed at the organization level.
This is opt-in per setting, not all-or-nothing. Most organizations start by locking just branding and security defaults, then expand the list only as they find real cases where inconsistency across tenants caused a problem.
Was this helpful?