One team want to make their confluence space private (accessible to team members only), with only a few pages open to anonymous users. I searched community and found some workaround: * create a new space with "anonymous access" and move any public page over; * If only one space is preferred, categorize space pages under 2 different parent page under root: one is to inherit the anonymous access, the other is restricted to team members. This is better to restrict each of the private pages. Question: * for #2, in Confluence Data Center, is there a way to restrict page to be "view and edit" only by "space members"? I know we can restrict page by users or groups, but can we restrict page view/edit to assigned "space members" only. * Generally speaking, is there any other workaround? plug-in is not preferred unless you think it is the only long-term solution. Thanks in advance for any feedback.

when you enable "page restriction", everyone possibly except the enabler won't be able to view/edit. then the enabler need to add everyone else permissioned in the space members to the allowed list, right?

But that's what they already have. You're asking for something that is already there.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to setup a confluence space with only a few pages public (anonymous)

Lucy_h4il2d

One team want to make their confluence space private (accessible to team members only), with only a few pages open to anonymous users.

I searched community and found some workaround:

create a new space with "anonymous access" and move any public page over;
If only one space is preferred, categorize space pages under 2 different parent page under root: one is to inherit the anonymous access, the other is restricted to team members. This is better to restrict each of the private pages.

Question:

for #2, in Confluence Data Center, is there a way to restrict page to be "view and edit" only by "space members"? I know we can restrict page by users or groups, but can we restrict page view/edit to assigned "space members" only.
Generally speaking, is there any other workaround? plug-in is not preferred unless you think it is the only long-term solution.

Thanks in advance for any feedback.

Accepted answers

All comments

Nic Brough -Adaptavist-

Your point 2 is the best approach here, it's using the restrictions as designed and expected. So to your two questions:

Yes, because your "space members" are defined by being in a group or a named individual
here's no "workaround" here, because there is no blocker to work around. Some apps can give different views by user, but yes, you do need an app, and they need to restructure your pages to match what you do with either option 1 or 2 you describe above.

Lucy_h4il2d

Thanks for your feedback.

about 2), our space members are defined mostly by individual users. As most of the space pages need to be restricted to team members, and this space has about 30-50 users, adding individual users for those restricted page(s) are not a very sustainable for the space admin considering space users changes constantly. Is there a way to setup page restriction to allow any/all "space members" to view and edit a page? in that case, space users are managed at site level, and page restrictions can inherit this, allowing no need to update page restrictions when space users added or deleted.

Nic Brough -Adaptavist-

Ok, I think we're missing something here.

You have said "space members" a couple of times. What do you think that means?

The reason I question it is that I would define "space member" as "someone who has access to see the space after they log in". That is controlled by being in a group, or being an individual names in the permissions.

So what you appear to be asking is for a third way to define a "space member", but I can't work out what you're trying to use to define it. Without knowing what your definition is, there's no way I can suggest anything to plumb into permissions and restrictions.

Lucy_h4il2d

Yes, space members is either some group(s) or some individual names.

To control page access or restriction, I want to know if there is a way to allow "all current space members" can view or edit confluence page, just like in Jira, the board or filter can be shared with "project" team members or groups or users.

For this confluence space, user want to make only some pages accessible by anonymous users while most other pages only limit to "space members". using page restriction (#2), I know space admin can add all individual users from the space members to the page's allow list. The challenges are: this is a large team and team members constantly change. When that happen, the space admin will need to a) update the space permissions; and also b) update the allowed user list for all of the controlled pages; that's error-prone.

We have a group called "confluence-users", but that includes all users not only from that specific team. We tried not to create too many customized user group for different teams, as managing the users in those customized user groups is a challenge.

therefore I am asking if there is a way for space admin to configure pages access restricted to "all current team members" while their space has anonymous access enabled, in that case all "space members" will automatically be able to view or edit most of the pages in this space, and when users change, space admin only need to update the user's space permission - just like the Jira board or filter sharing setting

Lucy_h4il2d

Any other suggestion on how to manage "restricted page" permissions - in a "anonymous access" enabled space (i.e. everyone can view) - to a group of member who are the space members and need to keep synced? Allowing viewing permission to list of individual users or creating a user group for this is not preferred. Thanks for helpful feedback.

If a confluence space can be set to be limited to team members only, but also allow some limited pages within to be "public", that will be easier.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server