...
For organizations with several channels and multiple publication channels (multi-channel publishing) it is often essential to be able to manage content from a central location and to re-use reuse it in multiple places. This means not only content but also web users, forms etc. In a default installation with more than one channel, all content is strictly separated. Content sharing is not done automatically, so if you want to do this you have to configure it. Most of these configuration properties involve assigning different read/write permissions for different channels. Editors of the various channels must explicitly allow one another to read content and to re-use reuse content. By explicitly specifying what can be read per channel, everything can be set up in a safe and flexible manner.
An important feature of shared content is that shared content it can only be read on another channel. For example, when an article is created in channel A then it can be displayed on channel B, but it can never be modified on channel B. This ensures that the rights of the author remain with the author. When different editors are allowed to edit content on different channels, their user accounts have to be shared as well. Editor X on channel A must be shared and granted permission to work on channel B as well.
...
| Note |
|---|
In the following sections, the term "content" is used in a broader context and is used as a synonym for content types, model types, settings, web users, etc. Language labels don't belong to this form of content. Language labels are maintained in a single object pool that is valid for all channels (see Language Labels). |
Sharing and Accepting
In order to share content between channel A and channel B, the configuration has to be changed to be able to expose (share) the content of one channel with another as well as to receive (accept) content from another channel. Sharing content is configured in three steps. For each channel, specify the following:
...
Model Type | Comment |
Application integration: filter definitions | |
Applications | |
| Content Repository | Always the The entire Content Repository is always shared and not individual content types |
Form resources | Form resources and form steps |
Form models | |
Form rules (all handlers) | |
| Forms | |
Languages | |
Page section labels | |
Personalization | Both personalization expressions as well as personalization models |
Presentations | Only presentations and no presentation variants |
Queries | |
| User groups | |
Web users | Always all All web users are always shared and not individual web users |
...