Restrict access to articles in team-managed service projects

You can restrict access to your knowledge base articles from your service project.

To change who can view articles in a space:

2. Select the Who can view dropdown next to the linked space of your choice.

3. Choose the Only Confluence users option if you want only Confluence users with access to that space to view the articles. Choose the All logged-in users option if you want all logged-in users of your service project (even people without a Confluence license) to view the articles. Remember that choosing All-logged in users will also make these articles visible to all active Atlassian users on Confluence.

To make changes to multiple spaces in one action, select the relevant spaces by checking the box next to the space name, go to the Who can view button above the table and choose from the given options.

Only admins can change these knowledge base permissions.

If you don’t see the option of Only Confluence users or All logged-in users, it may be because the space admin has made the space publicly accessible in Confluence. You can change this in Confluence if you’re a space admin.

To restrict access to your space:

1. Select the Settings button that appears when hovering over that respective row to go to Confluence permissions.

2. Turn off the View permission under Anonymous access.

Use Confluence page restrictions to impose more granular restrictions

If your knowledge base contains articles for both your team and customers, you can use Confluence page restrictions to prevent articles from being viewed by customers.

Learn more about page restrictions in Confluence cloud.

For example, you can create a Confluence group for your team, then restrict internal articles to this group. They won't appear in the help center, but your team can still read them while they work on issues. Articles that are not visible to the customer are marked with a red padlock icon.