Connecting communities with bridges

When you connect two communities with a bridge, people can see activity taking place in a community that's separate from the one they're currently using.

For each user, visibility into another community relies on their having a user account in both communities. Bridged communities use web services to communicate with one another.

Note: This is an optional feature available as a module. For more information, ask your Jive account representative.

One-way or two-way visibility

Administrators from communities at both ends of a bridge decide whether the bridge should support content visibility one way or both. An administrator managing or configuring an internal-facing community (one designed to serve a closed audience, such as a company's employees) might see value in requesting a bridge to an external-facing community (such as a support site for the company). Content from the external community visible to employees internally could offer an easy way for employees to see external content from customers. But going the other way—internal content visible to external community members—is often not as valuable.

When setting up a bridge, administrators from both ends decide whether, and how much, content should be visible from their own community to the other. Bridge settings at both ends provide the ability to enable or disable these features.

Bridged features

With bridged communities, users of the local community can:
  • See a list of the bridged communities.
  • Log in to a bridged community from the local community.
  • Receive results from the bridged community as part of their searches.