Why Per-Team Routing Matters
Different teams have different connectivity needs:
- **Engineering** needs access to US-based cloud infrastructure
- **Sales** needs EU presence for client-facing tools
- **Support** should route through the nearest region for latency
- **Finance** must stay within Australian jurisdiction for compliance
VynVPN's routing engine lets you define these policies centrally.
Step 1: Access the Routing Panel
Log into your VynVPN admin dashboard at `admin.vynvpn.com`. Navigate to Settings → Routing Rules.
Step 2: Create Team Groups
Before setting routing rules, ensure your teams are defined:
- Go to **Teams → Manage**
- Create groups: Engineering, Sales, Support, Finance
- Assign users to their respective teams
Step 3: Define Routing Rules
For each team, specify:
- **Exit Location:** Which region traffic should route through
- **Split Tunneling:** Whether personal traffic bypasses the VPN
- **Fallback:** What happens if the primary location is unavailable
Example Configuration
Rule 1: Engineering → US West (us-west-2)
Split tunnel: Enabled (only work domains through VPN)
Fallback: US East (us-east-1)
Rule 2: Sales → EU Frankfurt (eu-central-1)
Split tunnel: Disabled (all traffic through VPN)
Fallback: EU London (eu-west-2)
Rule 3: Support → AU Sydney (ap-southeast-2)
Split tunnel: Enabled
Fallback: AU Melbourne (ap-southeast-4)
Rule 4: Finance → AU Sydney (ap-southeast-2)
Split tunnel: Disabled
Fallback: None (disconnect if unavailable)Step 4: Apply and Monitor
Once saved, rules apply immediately to all connected users in each team. Monitor compliance from the Usage → By Team dashboard.
Advanced: Domain-Based Routing
For granular control, you can route specific domains through specific locations:
- `*.aws.amazon.com` → US West
- `*.salesforce.com` → EU Frankfurt
- `*.xero.com` → AU Sydney
Tips
- Test rules with a single user before rolling out to entire teams
- Use the "Simulate" button to preview traffic flow before applying
- Set up alerts for routing failures so you catch issues quickly