Child pages
  • Confluence use case: Extranet
Skip to end of metadata
Go to start of metadata

In contrast to an intranet, collaboration within an extranet is characterized tremendously by the separation of individual users and/or groups. You want to grant different users access to your data, but at the same time you must separate the individual external parties in such a way that no one can see the information belonging to other users/companies.

Recommended apps

SPACE PRIVACY - EXTRANET

 More information

Work with different external users in protected spaces, with built-in user separation using a simple authorization concept to protect individual user data.

> More about Space Privacy - Extranet

  • No labels

This content was last updated on 11/14/2017.

This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete. Please click this link if you want us to update this page. Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with content@seibert-media.net if you are in doubt, have a question, suggestion, or want changes from us.