Organisations and scope in OmniLab
Understand how the selected organisation, the Global organisation, and organisation-level settings shape what you can see and manage in OmniLab.
Understand why you can see some campaigns and settings but not others, so you always build in the right place. The answer almost always comes down to which organisation you have selected.
What the current organisation controls
The organisation you currently have selected changes the working context across OmniLab Studio.
| Area | What the current organisation changes |
|---|---|
| Campaign creation | New campaigns are created inside the selected organisation and start from that organisation's defaults |
| Settings | General settings, notifications, variables, and domain settings are stored per organisation |
| Access | Users can switch only between organisations that have been assigned to them |
| OmniLab Pages context | Organisation-level values such as variables and domain settings are exposed to OmniLab Pages for that organisation |
Switching organisation context
If you belong to more than one organisation, the sidebar switcher lets you move between your current organisation, the Global organisation, and your other assigned organisations.
The Global organisation versus regular organisations
OmniLab uses a Global organisation for shared governance and separate organisations for local work.
- The Global organisation is used for shared governance and shared settings.
- A regular organisation is where local campaign work, local variables, and local domain settings usually live.
When an admin selects the Global organisation, OmniLab Studio opens the broader General Settings area. When an admin selects a non-global organisation, OmniLab Studio opens Organization Settings for that specific organisation.
What is shared and what stays local
Some organisation settings can be shared from Global. Others stay local to each organisation.
| Area | How it behaves |
|---|---|
| General organisation settings | A non-global organisation can inherit these values from the Global organisation |
| Notification settings | A non-global organisation can also inherit these values from the Global organisation |
| Variables | Stored as a flat key-value map per organisation, without a Variables inheritance toggle |
| Scripts | Configured from General Settings when the Global organisation is selected |
| Domain settings | Managed per organisation as one OmniLab Pages subdomain, or shown as a read-only custom-domain state |
Why you may not see a campaign
If a colleague can see a campaign and you cannot, the most common reason is organisation scope. The campaign may belong to an organisation you cannot access, or you may be viewing a different organisation in OmniLab Studio.
The same logic applies to templates and shared configuration. Scope is not only about permissions. It is also about the currently selected organisation.
What to check before you build
Before you create or publish anything important, confirm that you are in the organisation that should own the live experience.
This avoids common problems such as:
- the wrong campaign ownership
- missing local variables or domain values
- shared defaults from Global that still need local review before publishing
Related
How organisation scope works
See how the Global organisation, other organisations, and limited inheritance work together.
Key concepts glossary
Look up shared terms such as scope, template, and organisation.
Share a template across organisations
See the campaign-side workflow behind cross-organisation template reuse.