Organisation settings (general defaults)
Review the General tab fields on an organisation and decide when to keep local values or inherit from Global.
This page covers the organisation-level settings you manage in OmniLab, especially the General tab and the inheritance behaviour that affects General and Notifications.
Prerequisites
- You have admin access to the selected organisation.
- You have confirmed that you are editing the correct organisation in the switcher.
- You know whether this organisation should use local values or inherit from Global where supported.
Where these settings live in Studio
The settings surface depends on which organisation is currently selected:
| Selected organisation | Settings surface |
|---|---|
| Global organisation | General Settings |
| Regular organisation | Organization Settings |
Both surfaces expose organisation-level tabs, but inheritance is available only in some sections.
What the General tab controls
The General tab includes these fields:
| Field | What it controls |
|---|---|
Enterprise Name | The organisation name reused across organisation-level configuration |
Notification Email | The default organisation email value |
Enterprise Timezone | The default timezone for the organisation |
Enterprise Language | The default language for the organisation |
Show Group Information in Campaigns | Whether the organisation information block is shown in supported Pages contexts |
Show Group Top Header | Whether the organisation top header is enabled in supported Pages contexts |
Address | The organisation address field |
| Social links | The Facebook Link, Instagram Link, Tiktok Link, and Twitter Link fields |
| CTA fields | The Group CTA Label and Group CTA Link fields |
Use the built-in fields first
If a value already has a dedicated field in General, store it there. Use Variables at organisation level for extra organisation-specific values that do not fit one of the built-in fields.
When to keep local values instead of inheriting
Use local values when a child organisation genuinely needs its own:
| Situation | Better choice |
|---|---|
| Local address, social links, or CTA destination differ by venue or brand | Keep local values on that organisation |
| All child organisations should reuse the same identity defaults | Inherit from Global |
| One country or venue needs a different timezone or language | Keep local values on that organisation |
| A regional rollout should stay aligned everywhere | Inherit from Global where supported |
What inheritance actually covers
Inheritance exists, but it is limited.
| Area | Current behaviour |
|---|---|
| General tab | A regular organisation can inherit the General tab values from Global |
| Notifications tab | A regular organisation can separately inherit sender, header, and footer settings from Global |
| Variables | Managed locally per organisation |
| Domain settings | Managed locally per organisation |
| Scripts | Managed from the Global organisation settings surface |
When a regular organisation inherits the General or Notifications values from Global, those inherited fields become read-only until local editing is restored.
Update organisation settings
Open the correct settings screen
Switch to the organisation you want to edit. Open General Settings if the current organisation is Global, or Organization Settings if it is not.
Review the General tab
Update the fields that define the organisation's defaults and presentation, especially timezone, language, address, social links, and CTA values.
Decide whether to inherit from Global
For a regular organisation, use inheritance when you want the General tab to reuse Global values instead of maintaining a separate local copy.
Review Notifications separately
If the organisation needs its own notification sender, reply-to values, header, or footer, review the Notifications tab as well. That tab has its own inheritance toggle.
Save and review downstream impact
Save the changes, then test any Pages or notification output that relies on these organisation defaults.
Timezone and campaign validation
Campaigns keep their own dates, but the organisation timezone still matters for validation. Two common validation messages are:
| Message | What it means | Fix |
|---|---|---|
Campaign timezone ({{campaign_timezone}}) differs from organization timezone ({{organization_timezone}}) | The campaign uses a different timezone than the organisation default. | Go to Build > General > Dates to align with organization timezone ({{organization_timezone}}) or keep current setting if targeting a different region |
Organization timezone '{{invalid_timezone}}' is not recognized | The organisation default timezone is invalid and cannot be used as the comparison reference. | Configure a valid organization timezone in General Settings > General Tab > Enterprise Timezone |
Related
Create an organisation
Create the organisation first, then return here to refine its local defaults.
Variables at organisation level
Store the shared values that templates, add-ons, and Pages scripts should reuse.
Organisation domain settings
Review the Pages subdomain settings that stay local to each organisation.