I want to create a public subspace inside a private one only been accessible by users on the parent space. It is working like expected, but the issue is than any authenticated user can see that subspace on the list under 'Public Spaces' on the taskbar on the left by the home icon.
Would it be possible to hide that subspace from been seen except from people been member of the parent private space?

Comments

mpotter’s picture

mpotter commented

Currently this is not possible to create a Public space within a Private space with the architecture of the Organic Groups og_subgroups module. This kind of use case is highly NOT recommended. It's confusing to users and also very difficult to ensure proper data privacy. If a Space is Private, all of the subspaces under that parent space really need to be private also.

But it doesn't sound like thats what you are doing. You say "only accessible to users of the parent space". Well, then it's not a Public space, is it? A Public Space is a space accessible by *everybody* on the site. If you have any access restrictions, then it's a Private space.

So for your use case, just mark the subspace as private and it will only be accessible by members of the parent space. Members are inherited from the parent space into sub-spaces by default.

ramiro.alba’s picture

ramiro.alba commented

Hi, Mike. Thanks for your answer,

Probably I did not explain myself cleanly.
What I want to do is to create a top parent space holding every content, but NOT inheriting users.
Then, within this top space, I will create subspaces, mostly private, with their specific members and permissions, but some of these subspaces, will be set as public so as members of the top space can see theirs contents (think of site documentation or other thinks of common interest to the staff), but people NOT been members of the top space (external users) will not bee able to access their contents.
This is working properly. People not been a member of the top space is denied the access to the 'public' subspace .
The only problem is that at the bar menu (Spaces) on the left, you can see the name of that subspace under the list of 'Public Spaces' , though you can not actually access to it if you try:

Access Denied
You are not authorized to access this page.

This is confusing

I could see that this issue is related to new users, not having any space membership. So the can see all the spaces that are set as 'public' instead of only the public spaces which are really public and not within private spaces. How can I change this?

mpotter’s picture

mpotter commented

Ahh, ok, now I understand. Does going into the Admin->Open Atrium->Plugin Settings page and enabling the toolbar option "Only show top-level spaces" fix this?

ramiro.alba’s picture

ramiro.alba commented

Mike,

"Only show top-level spaces" is set by default no Yes, which is the option you usually would want.
The issue is seen when a user has no space membership, so he can only see a list of 'Public Spaces' instead of a list of 'Subscribed Spaces'. That list of 'Public Spaces' shows not only real public spaces accesible to that user, but also public spaces within private spaces and consecuently not accesible to that user.
In my opinion, the only problem problem is that the 'Public Spaces' menu list is generated not taking into account that a public space been within a private one is not accesible and so it should not be included in that list when "Only show top-level spaces" is set to Yes.
If "Only show top-level spaces" was set to NO, it should check if the user you are generating the list for, is allowed to access.

mpotter’s picture

mpotter commented

OK, now I understand. I've added this to the list.

Argus’s picture

Argus commented

Who will close this one when it is solved?

mpotter’s picture

mpotter commented
Version: 7.x-2.13 » 7.x-2.23
Priority: Normal » Major

This is still an issue. Linked to local OA-733 JIRA issue for tracking. Marking this as major since it allows anonymous users to see the existence of a subspace that they do not have access to.

mpotter’s picture

mpotter commented
Status: Active » Fixed

Fixed in cf6bafd commit to oa_core

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.