Information Barriers for Hubs

Items within hubs respect limitations introduced through information barriers. When you create an information barrier, you can specify the users and hubs that belong to specific segments. Information is available on how to add hubs to existing information barriers.

​

End user experience

When information barriers are enabled, end users:

• Cannot share hubs if it violates a segment restriction.
• Cannot access a hub with a public shared link.
• Cannot upload content to a hub outside their information barrier segment.

End users can join and access hubs that do not belong to any information barrier segment, as well as hubs whose segment is permitted to interact with their own. When creating a hub, it is automatically added to the user’s information barrier segment if they belong to one.

​

Information barrier restriction requirements

Collaboration with hubs in an information barrier: Collaborations are blocked or removed if a user belongs to a segment that does not have access to the hub’s segment. Group collaborations are blocked or removed if any user in the group belongs to a segment that does not have access to the hub’s segment. Shared links to hubs: Users accessing hubs with a shared link go through a live information barrier check. If they do not have access, they are blocked from viewing the hub and its content. Anonymous users are exempt from this check because they do not belong to a segment. Item association to hubs:

• For a hub in a segment, an item can only be added if the item owner:
  • Is in the same segment as the hub, or
  • Is not in any segment
• If the hub is not in a segment, only items owned by users who are not in any segment can be added. Otherwise, the item cannot be added or will be removed.

​

Violations of the information barrier

When information barriers are enabled, collaborations that cause a violation are automatically removed. For example:

• The hub belongs to Segment A and is shared with User B. User B belongs to Segment B. If the segments cannot interact, User B is removed from the hub.
• The hub belongs to Segment A and is shared with Group B. Group B includes a user from Segment B. If the segments cannot interact, Group B is removed from the hub.

If content in a hub violates information barrier rules, it is removed. For example:

• The hub does not belong to a segment but contains content that belongs to a segment. That content is removed.
• The hub belongs to Segment A but contains content owned by a user from Segment B. If the segments cannot interact, that content is removed.

When content ownership changes from a non-segmented user to a segmented user, any violating collaborations are automatically removed. This does not apply to hubs, as hubs do not have owners. Any changes to a hub’s segment require a manual change in segments.

​

View violations of the information barrier setup

1. Navigate to the Admin Console.
2. Select Shield.
3. Select the Information Barrier tab.
4. Click Run Collaboration Report.

More information about this report is available in Collaboration Reports. An error message appears next to each row if a hub was deleted and no longer exists.

​

Add hubs to existing information barriers

Information on adding hubs to information barriers is available in creating an information barrier user segment.

​

View the number of hubs

1. Navigate to the Admin Console.
2. Select Shield.
3. Select the Information Barrier tab.
4. Click View Details.
5. The segment name and number of items are displayed.
6. Hover over the i next to Items to see the number of hubs.