Open issuesSwitch filter

I had to find out through trial and error what (0060e665be01 added a comment - 03/Aug/2024 3:00 AM) mentioned here.

1. Please document this workaround method.
2. Please add this feature.
3. Please add ability to create a "View only" share link / smartlink that we can share specific pages with other teams that are in our restricted folders/spaces.
   With links, we could at least gather all the links to those pages in a single location for easier access and management.
   It is pointless to use a smartlink to share these pages when we need to open our restricted spaces to non-team members and risk exposing all our restricted content.

My users are looking for such feature because they are disapointed by the "negative" logic of restrictions and would prefer such positiv approach which would be similar to what Microsoft is doing in Onedrive for sharing content.

https://getsupport.atlassian.com/browse/PCS-327234

66bfe2effd45 how many votes does this issue need before the team considers working on it?

The only suggested workaround I've seen is to add all users to the Space of the page that is being shared and restrict all other pages in the space... Following that guidance could result in info-sec violations as it will require users to remember they need to restrict pages when publishing.

I'm sure the permissions team has a large backlog, but this is something that many consider a core functionality and has been open for nearly 18 years.

What's the next escalation point for Confluence Cloud customers to pursue? 

Atlassian, it'd be great to get an official response to this. We're currently debating bteween Notion and Confluence, and with external staff in the future, I certainly don't think I'll be recommending Confluence in the future.

Hi there,

I’m excited to share that we’re in the early stages of developing a new product that could potentially offer valuable support in this area. Introducing Panorama: Your All-in-One Solution for Content Management in Confluence!

I wanted to share our landing page here incase it is of interest to anyone - https://www.kolekti.com/getpanorama

Same as https://jira.atlassian.com/browse/JSDSERVER-11299 and very disapointing such important functionality is not done yet

Please fix this Atlassian! It should be prio1 on your to do list.

Especially when working with more and more external groups and colleagues while scaling, it is a big pain:

You have your grown structure which works well and matches the privileges in 98% of the cases. For new groups and colleagues (e.g. external companies) that should have limited access to only a couple of pages and or their sub trees this means essentially:

• create a new project, while considering to keep the substructure
• link from the original tree to the other project or use the opportunity to include other pages inside a page. You will notice that this is not possible for subtrees.

At the end you have a "structure" of mess where you cannot find your documents using the tree navigation because all pages are spread around projects. Even you have to answer some questions about accessibility and privilege visibility I do not understand how such an essential topic is not covered after year of continual improvements.

It's major bug for our company as well. We have 600 employees, and lack of this obvious function will be a strong point to move from Atlassian to other service.