Collection visibility and granular access control in self-hosted Hoppscotch

Hoppscotch allows users to organize API requests into Collections, which can be shared across teams or made public via shared links. In a self-hosted Docker deployment, the goal is to maintain strict data privacy while still enabling collaboration among specific internal team members.

Currently, the visibility settings for collections often operate on a binary scale: private or public. This creates a challenge when a collection needs to be accessible to a specific group of authenticated users without being open to anyone who possesses the shared link.

Given the current architecture of the community edition, what are the available mechanisms to implement role-based access control (RBAC) for shared collections? Is there a configuration to restrict shared link access to authenticated users only?