📣 We’re so excited to announce that the single-space guest beta is now available in all paid Confluence Cloud editions: Standard, Premium, and Enterprise.
Take your team's productivity to the next level by making spaces collaboration hubs for both internal and external team members. We know your contractors, partners, and vendors are part of the team that makes work happen, and now they can actually feel like it.
See our support articles for details on what guests can and can’t do within Confluence. In short, Guests can only see and collaborate on content within their designated space or spaces that are open by other means and features like Anonymous Access. They will not see the people directory like a regular user and cannot change permissions within a space. They can, however, create pages, comment, and edit content within that space (with admins retaining full control over those permissions, of course). Guests can also be managed like other regular users easily via the product settings.
Visual guest markers make it easy for internal users to know when they are working with external teammates.
See our support articles for more details on how to get set up within Confluence, but here’s the short version:
For each paid user on a Confluence site, Admins will be able to add up to 5 guests for no additional cost or licenses. Total paid + guest user count cannot exceed the current Confluence site user limit, which, as of publishing, is 35,000 users.
Each guest can only access one space at a time.
|
|
But you can have guests in as many spaces as you’d like. |
|
And, you can have multiple guests in a single space. |
--
How will this work for companies that have integrated Confluence with an Identity Provider (Okta, OneLogin, etc.)? Will Guests be able to access Confluence Spaces if they do not have IdP account?
The same process will exist for Guest role as they do for normal user roles when it comes to IdPs. The IdP will sync a group of users into admin.atlassian.com. The Org admin will go into the group and apply the Confluence Guest role to that group. Any future user sync into that group will grant them the new users a Confluence Guest role. Customers with an IdP can currently grant product access manually to any users inside or outside their IdP (e.g. via a manual invite). The same is true for the Confluence Guest role.
How does this feature work for the users connecting via SSO?
SSO can be applied to any Atlassian Account that has been domain claimed. We only allow users with an Atlassian Account to get access to Confluence via the Guest role. So if they have users on SSO today in JSM, then those same users can get access to Confluence via the Guest role, and also have SSO applied to them. However, just having SSO on JSM clients does not automatically apply to Confluence.
Do guest users have access to individual Spaces despite IP allowlisting?
Guests don't circumvent IP allowlisting, so they have to originate from an allowed IP.
Is there a way to disable this when it rolls out? or is it telling the org admins not to invite people?
While you can’t disable the functionality, only org admins can add a guest. Your org admins can choose not to add any guests to the site.
How do guests and marketplace app access work?
Guests can use marketplace apps for free, however, we are providing app developers with the ability to opt out of providing guests access to their app. They can also request the installation of new apps. They cannot install new apps by themselves.
Note: Customers are responsible for the information that is stored within the marketplace apps and the access of this information.
Will adding a guest user be recorded within the audit logs?
Yes, in the audit log within Atlassian Admin you will see when guests are added and removed from the site, who added them, and the time they were added. The Confluence product audit log within the Confluence settings > Administration section will also show when a new user has been added into the default guest group and which space they were granted access to.
–
*Use of Confluence External Collaboration is a Beta Version subject to Section 14 of the Cloud Terms of Service.
Nidhi Raj
Senior Product Manager, Confluence Permissions
Atlassian
1 accepted answer
20 comments