Guidance Request on Client Access Management in Confluence Cloud

[Veena Panicker]

I am seeking advice on using Confluence Cloud for client-facing documentation with sensitive information. We aim to share pertinent documents with clients while ensuring strict access control and data security.

Our challenges are:

1. Granting guest access to clients without exposing irrelevant or sensitive data.
2. Independently managing internal and client user permissions within Confluence.

Could you please provide recommendations on:

• Setting up secure, client-specific access in Confluence.
• Best practices for controlling content visibility and user permissions.

Your guidance on these matters would be greatly appreciated.

I appreciate your support.

[Trudy Claspill]

Hello @Veena Panicker 

Welcome to the Atlassian community.

Do all your clients need access to all the same pages, or do different clients need access to different pages?

How many clients need access (rough estimate)?

How many pages do the clients need to access (rough estimate)?

What type of access do your clients need? Do they only need to view content? Do they need to be able to comment on pages? Do they need to be able to update or create pages?

Do you intend to give your client users full Confluence licenses, or are you trying to avoid impacting the cost of your product licenses?

Is it feasible for you to segregate the pages to which the clients need access into one or more separate Spaces from the pages that your internal users access?