Content Hub

Syndicating users

This page applies to Content Hub 3.2.0 or later.

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.

Managing user syndication behavior

To manage user syndication on a subscriber:

  1. Go to Administration > Configuration > Acquia Content Hub.

  2. Select the Import tab.

    The system displays the Import control section with the following checkboxes:

    • Disable user syndication

    • Disable user role syndication

Disabling user syndication

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.

User syndication behavior overview

The following table provides an overview of user syndication behavior:


User syndication enabled

User syndication disabled, no proxy user selected

User syndication disabled, proxy user selected

Content is imported into subscriber

  • The user of the original author is created if missing.

  • Existing users on the subscriber are updated to match the user entity from the publisher.

  • The user of the original author is created if missing.

  • Updates to existing users are ignored.

Proxy user is assigned as the author of the content.

Author is reassigned to another user on publisher

  • The user of the new author is created if missing.

  • Existing users on the subscriber are updated to match the user entity from the publisher.

  • The user of the new author is created if missing.

  • Updates to existing users are ignored.

Proxy user is assigned as the author of the content.

Any user is deleted on publisher

  • The user is not deleted on the subscriber due to safety reasons.

  • The user is blocked instead.

  • The user is not deleted or blocked.

  • Authored content may be reassigned to another user by the publisher.

The proxy user is not modified.

Any user is modified or blocked on publisher

Changes to the user apply normally.

Changes to the user are ignored.

Changes to the proxy user are ignored even if it was originally imported from the publisher.

Content is deleted on publisher

Changes to content apply normally.

Content is deleted. Author user is not deleted.

Content is deleted. Proxy user is not deleted.

Disabling user role syndication

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.

User role syndication behavior overview

The following table provides an overview of user role syndication behavior:


User role syndication enabled

User role syndication disabled

Content is imported into subscriber

  • The roles assigned to the author’s user are created if missing.

  • Existing roles are updated to match the publisher.

  • Roles are assigned to the author’s user.

  • No roles are imported.

  • No roles are assigned to the author’s user.

Author is reassigned to another user on publisher

  • The roles assigned to the new author’s user are created if missing.

  • Existing roles are updated to match the publisher.

  • Roles are assigned to the new author’s user.

  • No roles are imported.

  • No roles are assigned to the new author’s user.

A user role is modified or deleted on publisher

Changes to the role apply normally.

Changes to the role are ignored.