This part of the workshop covers the scenarios and settings for implementing an extranet in Confluence.
What to consider when working with Confluence as an extranet
From which user directory do the internal and external users come from?
Can external/internal users be added locally in Confluence?
If so, can the space administrator add external users?
Are there any existing spaces that need to be migrated to an extranet?
Who manages the external spaces?
Reader (default): Purely read-only permissions.
Commenter: Lets the user write comments and upload attachments.
External editor: May also create and edit pages, but may not delete pages or attachments.
Internal editor: May also delete pages or attachments.
Space administrator: May additionally manage the space, i.e. add users, adjust permissions and export the space.
Create a new extranet space using a wizard.
Add new or existing extranet users to a space with a selection mask.
Assign a space administrator to an extranet, who can add extranet users without needing full Confluence administrator rights (optional)
On this page
Features of Space Privacy
Restrict macros (inside extranet spaces - not in general (intranet) spaces)
Content by Label
Recently Updated (Dashboard)
Restrict the share function
Restrict the user directory
Restrict the full-text search
Restrict the quick search
Restrict profile access via an URL
Collaborate with users only within their extranet spaces
All internal employees have access
All internal employees can view and contact all extranet users
Your extranet spaces
This content was last updated on 12/01/2021.
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
email@example.com if you are
in doubt, have a question, suggestion, or want changes from us.