Granular Route Access Control for Cross-Organization Users

Hello guys,

My organization uses Pritunl to segment users by team (Infra, Dev, etc.). Each team is assigned a separate VPN server that routes only its specific subnets.

The challenge is granting granular, single-IP exceptions (e.g., User João from Infra needs one specific portal IP in the Dev network) without forcing him to disconnect and reconnect to a different VPN server.

This cross-access requirement is essential for daily operations. I am looking for the most efficient and scalable solution within the Pritunl ecosystem.

What is the best and most correct practice for implementing highly granular access control when a user requires routes that go beyond the standard scope of their primary VPN connection?

Routes can only be controlled at the server level. Users can connect to multiple servers or additional servers can be created with a different combination of routes.