Methods to allow unlicensed users to read Confluence Cloud content
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
This article explores various methods to enable a user without a Confluence license to access pages.
What are the possible solutions?
| Option | Pros | Cons |
|---|---|---|
Confluence Group with only View access | Can use IDP groups | Users will consume Confluence licenses |
JSM & KB spacesGive access to unlicensed users from Jira Service Management | If you are using Jira Service Management, all users of type "Customer" accessing the Portal will be able to see/search for the pages from the Confluence Spaces used as Knowledge Base; Does not consume Confluence license. | Site needs to have Jira Service Management (JSM) product; The Use Confluence permission must be enabled at the JSM access tab of the Global Permissions from Confluence. This way, these accounts can access the instance and then, the spaces; The user must be granted site access, but have the product access disabled (Reference: Granting unlicensed (internal) access to Confluence Cloud). |
AnonymousAs of May 2026, Confluence admins can enforce anonymous access across their site, preventing spaces from turning on anonymous access on if it’s off globally. Control whether spaces can turn on anonymous access Make a space public with anonymous access | Grant anonymous access to spaces Does not consume Confluence license. | Pages from the space linked to the Guest user would be public, protected only by page restrictions; It would be tracked by Search Bots. |
Anonymous with allowlist | Grant anonymous access to spaces, but only for specific IPs | Allowlist is only available for Premium license; The IP allow list contains a limit of 500 IP addresses that can be defined (consider using CIDR blocks and reducing the overall number of distinct allowlisted ranges); |
Guest | Can access pages from one space; Can access pages with anonymous access; Admins can define a guest default space. | Guest users need to be added one by one to their space (minimized using Default space configuration); REST/API for Guest maintenance still not available: CONFCLOUD-75248 - Create API to add Confluence Guest User; Only one space per Guest - but it is possible to access pages from other spaces if they are allowed for anonymous; To be part of a non-billable policy, the account cannot be synced (Using SCIM user provisioning) : One of the exceptions for an account not to be considered billable is being part of a non-billable policy; To have a synced account with access to confluence as a user, admin or guest role, the only way to exempt it from being billable for Access is to give access to at least one Enterprise product. If you invite guests manually without syncing by the IdP, they may be added using a default non-billable policy You will have the limitation of sending invites 10 per time; You won't be able to: One internal user already with access to some Confluence Spaces and invited again as guest may cause the error CONFCLOUD-74905-Avoid allowing internal users to be invited as guests. |
Public Link | It is possible to share some specific pages to the public using the Share option. | You can share just one page instead of the entire space; Some third-party macros might not work. If your page contains a lot of these you rather not want to share it with public links. Functionality that’s unavailable in the view-only version: |