Use Confluence with Space Privacy for a secure and uncomplicated collaboration experience with partners and customers.
Space Privacy restricts some functions so that they cannot work globally for external users, but rather only for their respective extranet space such as profiles.
You can assign administrators in an extranet space that allows user management in the same space. They do not have to have general Confluence admin rights.
Private Spaces
Effectively work with your customers, partners, and suppliers in specific extranet spaces within a Confluence instance.
Protection of User Data
In extranet spaces, assigned users keep to themselves – that is, they do not have access to other information from fellow user profiles. They do not even know that they exist.
Simple Authorization Concept
Assign users and groups to an extranet space using pre-determined roles. Subsequent roles let you manage an extranet space with other users.
Customer feedback: Asja Hermanns, Manager for Intranet & Knowledge Management at B.Braun
What were your problems before launching Space Privacy?
Was this problem solved with Space Privacy?
"Before launching the Space Privacy Plugin, we had data privacy problems. Our data privacy department pointed out that we could not introduce it because each user would have been able to see the information of the others, and obviously that is a no go. So we could not have introduced the external wikis without the plugin."
"Yes it did, no doubt about it. Now it is so secure for all users, that data privacy is really guaranteed on all levels and we can use everything the way we want."
Comparative and functional overview of Confluence Standard and Space Privacy
Problem ... | Solution in standard Confluence | Solution with Space Privacy | Effects for the User |
|---|---|---|---|
... User data is visible for anyone in the system. That means |
|
| Space Privacy creates so called Extranet spaces. These can be understood as a bubble, that protects the data of the users who collaborate in that space. These users only "know" the other users of that space, anyone else is "invisible". |
| Users can find other users in the system via Quicksearch |
|
| Quicksearch only suggests those users that are with me in one or more Extranet spaces. |
| Users can mention other users in the system |
|
| I can only mention users that are with me in one or more Extranet spaces. Others are not autosuggested. |
| Users can share content with all users in the system and users are autosuggested |
|
| I can only share content with users that are with me in one or more extranet spaces. Others are not autosuggested. |
| User data can be used in Confluence Standard macros |
|
| In Confluence macros I can only access user data for those who are with me in one or more extranet spaces. Others are not autosuggested and I also cannot enter them manually. The following macros are supported: |
| Users can find other users in the system via full text search and their filters |
|
| In full text search only those users are displayed, that are with me in one or more extranet spaces. I cannot find other users - not even in the additional search fields (i.e. contributor, author, etc.) |
| Users can view all users of the system via the user directory |
|
| In the user directory I can only see those users that are with me in one or more extranet spaces. Others are not autosuggested. |
| Users can pull up the profile of all other users in the system |
|
| I can only pull up profiles of those users that are with me in one or more extranet spaces. Others are not autosuggested. |
| Users can follow other users via the network function |
|
| I can only follow users that are with me in one or more extranet spaces. Others are not autosuggested. |
| Users can access all labels in the system and thus make conclusions about other users/companies in the system |
|
| I can only access those labels that are used in the extranet space that I have access to. Others are not suggested in the respective macros. |
| Users can see who has clicked on like on an available page |
|
| If there are general spaces that I have read access to as an external user, i.e. FAQs, help section, etc., pages can be "liked". This action becomes visible to other users, which means they see that the person has clicked on "like". However, it is still not possible to locate the user anywhere else in the system, mention him or her, etc. Access to the profile also remains blocked. |
Confluence Onboarding Apps (Welcome Action) |
|
| We have deactivated this function. |
Makro: Label summary |
|
| We have deactivated this function. |
| Support User Profile App |
|
| Not currently supported. We are working on a solution. |
... only admins and space admins can give access to a space. That means: | Space Privacy offers two new admin roles on space level. Extranet Manager and Extranet User Manager.The Extranet User Manager can add and create new users in his extranet space.The Extranet Manager is also Space admin and can add groups to his extranet space. | ||
| Only admins can create new users. |
|
| The admin can choose whether Extranet (User) Managers can also add new users to the respective extranet space. |
| I have to be at least a Space Admin to give a user rights to his space. |
|
| Extranet (User) Manager can give rights to an extranet space to existing and new users via pre-defined roles, such as reader, commentator, editor-standard, etc. It is no longer necessary to be a Space Admin and access the tab "rights". |
| There is no clear rights structure based on unified roles on space level. |
|
| There are five pre-defined roles, reader, commentator, editor-standard, editor-extended, editor-restricted. The administrator can activate and deactivate these roles independent from each other, as well as adjust the respective rights. These are then also changed for already assigned users. |
