Question 1

Why content inheritance matters?

Accepted Answer

As organizations scale, content naturally fragments:
Global brand content lives in multiple places
Updates are copied manually
Local teams drift out of sync
Fixes take weeks instead of minutes

Content inheritance and propagation solve this — without turning everything into a rigid template.

Question 2

What is content inheritance in Webiny?

Accepted Answer

Content inheritance means allowing one tenant to share content with other tenants, while still keeping each tenant isolated and in control.

In practice:
A “root” or global tenant owns shared content
Other tenants inherit that content automatically
Local teams can extend or override where allowed
Changes remain traceable and predictable

Nothing is duplicated unless you explicitly choose to.

Question 3

How does content propagation work?

Accepted Answer

Propagation is rule-driven and explicit.

Using code and lifecycle events, you can:
Push updates from a global tenant to all or selected tenants
Trigger propagation automatically on publish
Apply different rules per content type
Skip tenants that have local overrides
Control timing and approval requirements

Propagation becomes a controlled process — not a risky bulk action.

Question 4

Can local teams customize inherited content?

Accepted Answer

Yes — and this is the key balance.

You decide:
Which fields are locked globally
Which fields can be localized or overridden
Whether overrides break future propagation
How conflicts are resolved

Global consistency and local autonomy can coexist.

Question 5

How does this work in multi-brand or global setups?

Accepted Answer

This feature is built exactly for those scenarios.

Common use cases include:
Global brand pages with regional adaptations
Shared legal or compliance content
Central product content with local pricing or messaging
Multi-country marketing sites
Franchise or partner networks

You manage one platform — not dozens of disconnected sites.

Question 6

How is this different from copying content?

Accepted Answer

Copying content manually creates divergence immediately.

Inheritance keeps a living relationship:
Global updates can propagate automatically
Local overrides don’t break the link
Rules determine what can and can’t change
You always know where content originates

This avoids the “copy-paste forever” problem.

Question 7

Is this safe at scale?

Accepted Answer

Yes — safety is the entire point.

Webiny ensures:
Tenants remain isolated
Propagation rules are enforced consistently
All changes are versioned and auditable
Rollbacks are possible if plans change

This makes it suitable for enterprise and regulated environments.

Question 8

Who is this designed for?

Accepted Answer

Content inheritance & propagation is ideal for:
Global enterprises with regional teams
Multi-brand organizations
SaaS platforms with shared content models
Agencies managing many similar client sites
Any team tired of syncing content manually

If consistency matters and flexibility is required, this is essential.

Loading...

Share content globally. Adapt it locally.

Control without bottlenecks. This isn’t about centralizing power — it’s about removing friction.

Frequently Asked Questions

Want to manage global content without losing local flexibility?