# Per-user access to specific IPs/routes within the same server

**URL:** https://forum.pritunl.com/t/per-user-access-to-specific-ips-routes-within-the-same-server/3825
**Category:** Pritunl VPN
**Tags:** pritunl
**Created:** [July 26, 2026, 2:11pm UTC](https://forum.pritunl.com/t/per-user-access-to-specific-ips-routes-within-the-same-server/3825 "2026-07-26T14:11:39Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![varun](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/v/e9bcb4/32.png) [@varun](https://forum.pritunl.com/u/varun)
#### Post date: [July 26, 2026, 2:11pm UTC](https://forum.pritunl.com/t/per-user-access-to-specific-ips-routes-within-the-same-server/3825/1 "2026-07-26T14:11:39Z")

</div>

Hi, we’re using Pritunl with one server per environment ( **Organizations → Servers → Routes** ), and we’ve run into a limitation.

Today, access control appears to be at the server level, so users can access all routes attached to a server. We need to restrict production users to only specific IPs/hosts within the same server, without creating separate servers for every IP combination.

Is there a supported way Enterprise to achieve per-user, per-IP route access within a single server? If not, what’s the recommended approach, and is this on the roadmap?

Pritunl Org:  
│  
├── Server: Staging (Group: staging)  
│ └── Routes: full staging subnet(s) → all resources granted  
│  
├── Server: Non-Prod (Group: non-prod)  
│ └── Routes: full non-prod subnet(s) → all resources granted  
│  
└── Server: Production (Group: production)  
└── Routes: full prod subnet  
└── ❓ need: per-user grant to only specific IPs within this route  
e.g. user A → 10.x.x.11 only  
user B → 10.x.x.11, 10.x.x.25  
(not the whole prod subnet)

---

<div class="post-metadata">

### Author: ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)
#### Post date: [July 29, 2026, 3:21pm UTC](https://forum.pritunl.com/t/per-user-access-to-specific-ips-routes-within-the-same-server/3825/2 "2026-07-29T15:21:41Z")

</div>

Routes can only be controlled at the server. This may change in the future but currently there isn’t any plans on changing it.