Note: This is a premium feature or service. This article only applies to your community if your Firstup contract includes this premium functionality. Please contact your Customer Success Manager with any questions about feature availability for your community.

Overview

For organizations with multiple communities, managing content that should appear in multiple communites is simple with our enterprise connection Cross Community Content Management. With Cross Community Content Management, instantly replicate all content types across multiple communities upon Save or Publish of a piece of content.

• Reduced workload: a piece of content can be created and updated in a single source community, and those changes are replicated in one or more target communities as defined in a "workflow".
• Full content type support: Properly support all content types available to communicators (including video and notes). In comparison, Community Content RSS Feeds cannot pass video posts from one community to another.
• Real-time replication: Copy content between communities immediately, instead of having to wait up to an hour for an RSS feed to synchronize.
• Maintain content layout and appearance: Content will look the same in the target community(s) as it does in the source.
• Single source of truth: Content in the target community(s) can stay synchronized to the source community (or not - your choice!). Any updates including edits to the image/video, title, description, body, and publishing settings (shareable, featured, etc.) can be replicated upon Save/Publish of the changes.

If you are interested in implementing Cross Community Content Management for your organization, please reach out to your Customer Success Manager to discuss further.

Workflow Definitions

In essence, you define a source community and topic(s) for Firstup to "listen" to and define how that content is replicated to a target community. All workflows define a source community/topic and a target community/topic, and the content only flows from the source to the target.

Collaborate with your Customer Success Manager to define the desired workflows. The workflows cannot be edited or modified for specific pieces of content - once configured, they apply to all content as defined in the workflow.

Required For All Workflows

• Workflow Mode - choose one
• Content Sync - the card in the source community is the single source of truth and content in the target(s) will stay in sync with the source. Updates to any source content attributes or metadata will be replicated. This is true regardless of publication state or of changes on the target. The card in the source community is always the source of truth.
• Content Broadcast - when a card is Published on the source community, it is copied as-is to the target community and never updated again. Unlike Content Sync, the card on the target is not kept up to date with changes on the source card when this option is used.
• Source Community
• Source Topic(s) - at least one topic per source community required
• Target Community
• Target Topic(s) - at least one topic per target community required
  

Optional Settings for Workflows

• Ignore Drafts - if the card on the source community is a Draft, ignore the card in the target community (only applicable with Content Sync).
• Review First - if the card on the source community is Published, put the card on the target community as Needs Review.
• Source Content Featured Only - only look at source content that is Featured.
• Source Content Keywords - only look at source content with certain Keywords.
• Target Template Fixed - the default is to match the template of the source content, optionally configure to always use a specific template from the target community.
• Target Content Featured Always/Never - the default is to match the source content, optionally configure for target content to always (or never) be Featured.
• Target Content Shareable Always/Never -the default is to match the source content, optionally configure for target content to always (or never) be Shareable (if available for the content type).

Examples

Minimalist Workflow (Required Settings Only)

Based on the COMMunity -> Nextup workflow above, any content saved or published to COMMunity's topic "Known Product Issues" would be replicated to Nextup's topic "COMMunity Product Issues" the moment the content is saved or published - new content should appear nearly instantly. As this configuration is fairly simple, the replication will simply copy all metadata (including the publishing settings, template, etc.). With Content Sync, any edits that are resaved/republished will be updated in the replicated card almost instantly as well.

Advanced Workflow (Required and Optional Settings)

Based on the advanced workflow above, any content published to COMMunity's topic "Updates and New Functionality" will appear in Nextup's as needing review. This gives a Community Manager in Nextup the chance to review the content before it is published (perhaps to schedule a push notification to go out with the card). The content will always come through with Shareable set to OFF, the Community Manager can edit this to ON.

Mode Details

With all configurations, the workflow will only replicate the card when it meets all "source community" definitions including topic(s).

Content Sync

The card source community and target community are synchronized at all stages of draft, scheduling, and publishing.

Workflow:

Content Sync with Review First ON

Adding Review First ON to Content Sync affects how a post behaves when it is published. Saving as a draft or scheduling is unaffected.

Workflow:

Content Sync with Ignore Drafts ON

Adding Ignore Drafts ON to Content Sync affects how a post behaves when it is saved as a draft. Scheduling, publishing, and archiving is unaffected.

Workflow:

Content Broadcast

The post in the target community is created when the source post is published. The post in the target community is not updated with subsequent saves or publishing.

Workflow:

Content Broadcast with Review First ON

The post in the target community is created as needs review when the source post is published. The post in the target community is not updated with subsequent saves or publishing.

Workflow:

Other Functionality Notes

Topic Configurations

Cross Community Content Management does not impact topic configurations in any way. Topic settings such as name, description, image, targeted users, hidden/visible are not connected across Community A and Community B. You must manage the Source Topic settings in Community A while signed in to Community A. And you must manage your Target Topic settings in Community B while signed in to Community B. 

For example, the topic setting "auto-publish" only applies to content submitted by users to that topic. This setting has no impact on Cross Community Content Management (CPCM). If you would like the CPCM content to be set to need review in the target community, please define that requirement in the CPCM workflow using the setting "Review First".

Hidden Topics

Note, Cross Community Content Management is compatible with Hidden topics. You can configure the workflow to pull from a Hidden topic in Community A and publish that content in a Visible topic in Community B.

Selecting Multiple Topics

Consider when adding multiple Topics to a Campaign whether more than one of those Topics is used by Cross Community Content Management (CPCM). A separate post will be created by CPCM on each Target Topic. Members following more than one of these Topics will see a duplicate in their feed.

Archiving Source Posts

Archiving the source post will, as a result, automatically archive the target post.