-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Many people (non admins) unwittingly share content with recipients who do not have the permissions to see that content. It is confusing for the person doing the sharing as they cannot tell what is viewable to others and what is not. We have tried to make this as clear as possible through training and naming spaces a certain way to make this more clear (example "All Company Share" space, etc), but this is a brittle method and one that has limited success despite our efforts to keep throwing training at this. Is there any relief in sight on this? It really makes people frustrated when on rollout of Confluence we boasted about how Confluence increases collaboration and makes it easy, then it just makes it hard when people attempt to share and run into these problems where they are blind to everyone's access level for the content they need to share. It's really tough to manage being the administrator who has to deal with all of these snags.
The solution I have in mind is to write the sql needed to make this happen on my own and create a user macro to make this available to others (this has been done for Oracle but not Postgres from what I can see), but I'd rather see if there is a cleaner solution before wiring that in.
- duplicates
-
- Closed
- relates to
-
- Closed
[CONFSERVER-21661] Ability for users who are not space admins to see space permissions
Stephan Haslinger
added a comment - There is a User Macro as a workaround. Sandro posted it here: https://answers.atlassian.com/questions/22091/how-can-i-show-the-page-permissions-in-the-page-itself-confluence
Stephan Haslinger
added a comment - There is a User Macro as a workaround. Sandro posted it here: https://answers.atlassian.com/questions/22091/how-can-i-show-the-page-permissions-in-the-page-itself-confluence Stephan Haslinger
added a comment - A non-admin user wants to know, who can see a page that has no restrictions.
i.e. to lookup the space-permissions page (read-only).
If the space permissions were set correctly, then there would be no cause to define page-level restrictions.
If the user does not know the space permissions, he would set restrictions redundant to the space-permissions in some cases.
Another use-case would be to lookup the space admins in order to contact on space-level problems.
Stephan Haslinger
added a comment - A non-admin user wants to know, who can see a page that has no restrictions.
i.e. to lookup the space-permissions page (read-only).
If the space permissions were set correctly, then there would be no cause to define page-level restrictions.
If the user does not know the space permissions, he would set restrictions redundant to the space-permissions in some cases.
Another use-case would be to lookup the space admins in order to contact on space-level problems. Many people (non admins) unwittingly share content with recipients who do not have the permissions to see that content. It is confusing for the person doing the sharing as they cannot tell what is viewable to others and what is not.
A couple questions about your use case...are your users using the new Share button (introduced in 3.5) to share pages? Are these permissions usually set a the space level or is the problem that people are applying restrictions to pages?
Stephan Haslinger
added a comment - Hi,
we have several spaces with special permissions set. The users who add pages with confidential information to those spaces want to be aware of their readers. They could set restrictions for each page. But they won't need to do that if the space's permissions are set up correctly.
Now, before adding confidential information, the users may want to review the space's permissions.
For page restrictions there is already a feature like "who can read this page?". It should include the users/groups of the space's permissions.
Stephan Haslinger
added a comment - Hi,
we have several spaces with special permissions set. The users who add pages with confidential information to those spaces want to be aware of their readers. They could set restrictions for each page. But they won't need to do that if the space's permissions are set up correctly.
Now, before adding confidential information, the users may want to review the space's permissions.
For page restrictions there is already a feature like "who can read this page?". It should include the users/groups of the space's permissions. 
Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.