Summary
Allow community owners to share selected community-owned files and folders with one or more other communities while retaining ownership and storage quota in the source community. Support read-only folder sharing without exposing the rest of the source community's file library.
Problem
The original request from MAHLE describes reliance on personal files to share content with multiple communities. This creates dependence on an individual's account and risks loss of access when that person leaves. Copying files into each community creates duplicate storage and makes updates difficult to maintain.
The additional DRV Bund request extends this need to selected community-owned folders. Moving content into personal folders to share it with other communities consumes personal storage and detaches content from the project community, undermining community storage governance.
Requested capability
Share community-owned files and folders with one or more other communities without moving content into personal storage or creating separate copies.
Allow owners to share a selected folder as read-only, with the source community retaining content ownership and storage quota.
Share different folders with different communities, leaving the rest of the source library private.
Make shared content discoverable in the destination community's file library and make the sharing destinations visible.
Preserve the original use case of explicitly sharing selected content from a restricted community with a public community without opening the entire source community.
DRV Bund example
A project community collaborates with five departments and needs to share a specific folder read-only with each department's community. For example, a "Public documentation" folder can be shared with a partner community without exposing other project files. This capability has been requested frequently by multiple teams at DRV Bund.
Limitations of share by link
The original request notes that share by link does not fully meet the need: it does not show which communities have access, does not list the shared file in the destination community library, and sharing ends when the link is removed.
Business value
Enable cross-department collaboration without fragmenting content ownership, relying on personal storage, or maintaining duplicate files. Keep project content governed by the source community while granting partner communities access only to selected content.
While we can see the use case for this, the difficulty in handling Community and personal permissions makes this something we are unlikely to add to Connections.
Since 6.0 CR4 you can share files by an additional link. Still this would result into a link (bookmark) without a preview. Maybe the design team can consider to have file symbolic links and a preview for these files in other places such as other community or even in personal file repositories.