Confluence guests: one-space access and external collaboration

A guest is a distinct access arrangement

Confluence guests are intended for external collaboration and have access to one assigned space at a time. Atlassian’s guest capability guidance distinguishes this role from a regular user and lists permissions guests cannot receive, including space administration and space export.

Start with the work the outsider needs to do. An agency reviewing campaign drafts and a consultant maintaining material across several departments may need different arrangements. A guest label should follow the legitimate collaboration scope, rather than being used as a general substitute for internal user access.

An invitation and a space assignment are different steps

Atlassian’s assignment instructions explain that a guest without space access cannot use Confluence. They also note that anonymous access is a separate route: a guest may still see spaces made available to anonymous users.

When somebody reports an empty workspace, check invitation status, the assigned space and the intended page permissions. Do not make internal content public merely to clear an access problem. Have the responsible administrator review what the guest actually needs.

Design a contractor area around a handover

Imagine a fictional external writer delivering a set of customer guides. Put the approved brief, working drafts, review notes and final handover in a deliberately scoped area. Identify which internal person accepts the work and which materials should never be visible to the writer.

Keep the project’s internal budget and unrelated customer notes outside the proposed collaboration scope. A page tree that mixes external drafts with internal records creates a permissions problem that a friendly space name does not solve. Review attachments and linked content as well as page text.

Record the intended access boundary

These are proposed checks, not observed permissions. Use a test page and an authorised external participant before copying real client material into the area. Keep the result with the project’s access owner.

Plan the end of the engagement at the start

Name the person who reviews access at handover. Record which finished pages remain, who maintains them and whether the contractor has any continuing responsibility. Check separately whether shared links, exports or material in another application need a review; closing one role does not describe every copy already delivered.

Use the Confluence profile alongside the team knowledge guide. The goal is a usable, maintained body of work with a clear audience. Adding a guest successfully is only the first part of that workflow.

Frequently asked questions