Content Hub enables syndication from content publishers to content
subscribers. Publishers create content on their websites in their
normal Drupal workflow, and Content Hub syndicates that content
to subscribers along with any dependencies.
By default, the author of the content is included as a dependency.
The author’s user entity is syndicated in full, complete with its
roles and permissions, ensuring that the subscriber has all the
information that it needs to build an exact replica of the content.
However, syndicating user entities may not always be desired.
As of Content Hub 3.2.0, Content Hub allows finer control over
the users and roles imported to subscriber sites.
By default, user entities are syndicated with content they have authored.
Syndication of users can be disabled, preventing situations that would
have otherwise imported them to a subscriber.
When user syndication is disabled, the following are the options to
manage content authors:
Select a proxy user that already exists on your subscriber account. The
proxy user serves as the author of all imported entities on that subscriber.
Acquia recommends creating a new user to serve as the proxy user.
Note
Existing, previously-imported content is not immediately re-authored when
enabling a proxy user. Changes to content authors are only applied through
the syndication process.
When no proxy user is specified, Content Hub creates the user entity of the
original author if it is missing on the subscriber. However, Content Hub does
not syndicate additional updates to that user entity.
By default, user roles and permissions are syndicated with user entities.
Syndicating roles can be disabled, allowing subscribers to have different
roles and permissions from the publisher.
Note
User role syndication can be disabled with or without disabling user syndication.