Hi Proton team,

I’d like to propose a single feature that would improve Proton Drive:

Idea: Make virtual Topic Maps inherit the most restrictive sharing permissions of the items they contain, with an optional override to set separate permissions for the collection itself.

Why it matters:

• Guarantees that a virtual collection never exposes a file to a broader audience than the file’s original sharing settings.
• Allows teams to create a “read‑only” view of a project while keeping the underlying assets private.
• Aligns with Proton’s zero‑knowledge model – permissions are enforced client‑side.

Suggested implementation (high‑level):

• When a Topic Map is rendered, compute the intersection of all member permissions.
• Show the resulting effective permission badge in the UI.
• Provide a “Override permissions” toggle for power users who need a different sharing model.

Thank you for reviewing this.

Best,
Mat Huppertz

(Part of a series of related suggestions – see #0101, #0102, #0103, #0104, #0105, #0106, #0107)