Share a template across organisations
Share an existing template with another organisation, then generate a campaign and review the destination-specific setup.
Template sharing exists for one common reason: a campaign that worked well in one organisation should be reused in another without rebuilding it from zero.
Who should use this flow
Use direct template sharing when you have access to both the source and destination organisations. If you do not, fall back to the template ZIP workflow in Templates: export, import, and reuse.
What sharing does and does not solve
Sharing makes the reusable campaign structure available in the destination organisation under Shared Templates. It does not make destination-specific values automatically correct.
After sharing and generating a campaign, you still need to review:
- the new public link
- campaign language
- timezone
- organisation-specific variables
- add-on settings
- any reward or deployment detail tied to the destination organisation
The destination organisation can create campaigns from the shared template, but the source template remains the place where ongoing template maintenance happens.
Main task
Open the source template
Go to Templates in the source organisation and open the template you want to reuse.
Use the Share action
Open View Actions, choose Share, then use the organisation selector in the share dialog (Select Organizations) to choose the destinations that should receive the template.
Open the destination organisation
Switch to the destination organisation and confirm the template is now available in Shared Templates.
Generate a destination campaign
Use the shared template to create a new campaign in the destination organisation, then review the campaign details in the generation modal before you confirm.
Reconcile destination values
Open the generated campaign and review Settings -> Advanced Settings -> Addons, along with dates, language, rewards, and any organisation-level value that should differ from the source campaign.
Why the reconciliation step matters
Every organisation can have its own variables, identifiers, integrations, and scheduling context. That is why a template can be perfectly reusable while still requiring a short destination-specific setup pass.
In practice, the most important checks are:
- the public link is new and correct for the destination campaign
- the language matches the content you intend to serve
- the timezone matches the destination audience
- add-on values use the destination organisation's variables
- rewards and redemption setup still match the destination launch
Related
Templates: export, import, and reuse
Use the ZIP route when direct sharing is not the right option.
Organisations and scope in OmniLab
Understand why templates, users, and campaigns are organisation-scoped.
Validation & publishing
Check the generated campaign before it goes live in the destination organisation.