Skip navigation

Restrict visibility of users in a B2B or B2C environment

score 30
You have not voted. Active



imagine three different kinds of simple business environments using Jive SBS:


  • A lawyer, who is using Jive SBS as an community to work together and communicate with his clients = B2C
  • A engineering company, which is using the community to communicate with its development partners (third parties), who have nothing to do with each other but only with the engineering company = B2B
  • A global intranet with people speaking 20 languages and working independant on the same Jive SBS community = B2E

In all three cases it should not be possible that in the people directory or in the spotlight search all people could find each other:


B2C = In normal internet forums like Nike, Adidas or Apple it is okay, but if it is about confidentiality, two clients should not find each other on a regular basis: Jive SBS does not work for these communities.

B2B = A no brainer: Same like B2C, but additionally: in some countries in the world it is not even allowed by law that the employees of two companies see each if they not agree on that aspect.

B2E = Imagine a real intranet, with 40.000 people, with 200 "John Does"... in this case it is okay that people search each other, still it is very inconvenient, because finding people becomes more and more difficult (we already had that in our pilot community)...... not to mention the whole Betriebsrat issues with the people directory.


In all three domains there is no problem with content itself: If people see each others content, they must have a business connection.


There are three solutions (one easier to implement than the other, and I am sure there are many more):

  1. Connect groups to other groups in the admin and use these relationships as filter
  2. Use an organisation model and create visibility rules (more hard, because Jive misses organisation as an business object)
  3. Using something like a client model


Moved from DACH User Group

Category: Core Platform (both Jive-n & Jive-x)
Your software version:
If Hosted or On-Premise, which version number: Not applicable


Vote history

Introducing Tracks on the Jive Community
Configure your Jive Community experience by selecting a track. We'll use this track on the homepage to show you relevant content and help you find resources quickly. You can change your track easily from the homepage or your profile.
As a community manager, you're an ambassador for your Jive community as you build places, curate content and engage with fellow community members. To help you go further with your site, we'll share success stories and other resources.
Whether considering a new purchase or working on an upgrade, technology managers need insight on the best ways to implement a community and learn more about the various upgrades in software releases.
An effective community starts with sound business strategy. As your community matures, you'll want to learn and share best practices for implementation and continued success.
Whether you're a developer, system administrator or a designer, you need insight on building a great user experience for your Jive community. Get the scoop on theming, API's, upgrades and more.
We've got a special area for partners to get essential information and best practices they need for describing and selling Jive to potential customers.
Whether or not you have a specific role in your Jive community, this track highlights areas of interest to Jive users such as training materials, community best practices and an opportunity to network with other customers.
save and close