Welcome to the HCL Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events, please visit our HCL Connections page.
got it, thank you. I will investigate with the team
This was a file Shared with community. The file was public, the community wasn't. When the file was openend from the files app within the community the URL is community specific and will give an error when send to anyone not in that community. If the same exact file was opened from for instance the personal files and the URL was copied then they can open it.
It was not a 'copied to community file'
In this use case, was the file "Shared with Community" or created as a new file in the Community via "Give Copy to Community"?
Generally speaking Communities are a container that manages access to all assets in the Community based on membership, so the right behaviour for any content existing only within the Community is to only allow members view/edit rights for all content.
If the file was shared with the Community the broader access right beyond the Community (i.e. in your case Public) should still be valid.