Remote team access
Identify the internal applications and networks your team needs. Define who can connect, from which devices and how access is revoked.
VPN / PRIVATE ACCESS PLANNING
Private VPN access for
your team’s devices.
Give approved devices a defined path to private resources. Review access rules, routing and supported platforms before choosing the configuration your team needs.
Device requirementsIntentional routing
A CLEAR PATH TO YOUR RESOURCES
Approved devicesYour team’s endpoints
Private resourcesOnly the agreed scope
Encrypted tunnel · Defined access · Planned routes
Conceptual diagram. No active VPN connection.
VPN REQUIREMENTS PLANNER
Choose devices, platforms and routing.
Record the devices, platforms and traffic routes needed for remote access or a site connection. Your quote confirms compatibility, locations, protocols and capacity.
Your access requirements
Selected private-resource traffic uses the tunnel. Other traffic follows the device’s normal connection.
Your private-access brief
- Use case
- Remote team access
- Devices
- 8 devices
- Platforms
- Mixed operating systems
- Routing
- Selected private-resource traffic
Planning summary only. No VPN connection is created.
PLAN FOR THE WAY YOU WORK
What will your VPN connect?
Server administration
Separate administrative access from public application traffic. Agree the network paths, endpoint controls and operational responsibilities.
Site connections
Map the networks, addressing and routing needed between sites. Confirm gateway capabilities and any overlapping address ranges before planning a tunnel.
ACCESS WITH A DEFINED SCOPE
Agree who can connect and administer access.
Accounts, devices and access changes
A VPN carries traffic through a configured connection. The surrounding identity, routing and endpoint choices determine what that access allows.
- Identify authorised users, devices and required destinations.
- Define onboarding, credential handling and offboarding.
- Review DNS, IPv4/IPv6 and routing requirements.
- Agree updates, monitoring, support and incident responsibilities.
Confirm before deployment
- Compatible client software and operating systems.
- The destinations and traffic intended to use the VPN.
- Authentication, key management and device revocation.
- Service locations, logging practices, limits and applicable terms.
DEPLOYMENT PLANNING
From access requirements to a tested configuration.
Map users, devices and resources
Document endpoints, private resources, networks and the people who administer them. Confirm the intended use and any organisational policies.
Review the design
Agree the selected protocol, compatible clients, routes, DNS handling and access controls. Confirm capacity and service limitations in writing.
Validate and document
Test approved access and expected traffic paths on the supported devices. Document normal operation, support and removal of access.
A VPN is not an anonymity guarantee.
Device security, account activity, destination services and the selected provider’s practices still matter. A VPN does not remove the need for endpoint protection or compliance with service terms and applicable law.
Device security, account activity, destination services and the selected provider’s practices still matter. A VPN does not remove the need for endpoint protection or compliance with service terms and applicable law.
For one common protocol’s concepts, see the official WireGuard quick start. The supplied protocol and configuration are defined by your service order.
VPN QUESTIONS
VPN questions
Is a VPN the same as anonymous browsing?
No. A VPN creates a configured path for network traffic. It does not make every action anonymous, remove account identifiers or replace the privacy and logging terms of the selected service.
Will all device traffic pass through the VPN?
That depends on the routing design. A split-tunnel setup directs selected traffic through the VPN; a full-tunnel setup plans broader traffic through it. DNS and IPv4/IPv6 behaviour must also be reviewed on supported devices.
Can the VPN replace a firewall or endpoint security?
No. A tunnel is one component of an access design. Firewall rules, device updates, account controls and the security of the connected resources remain important.
Which devices, protocols and locations are included?
Compatibility, supported clients, protocols, locations and capacity are confirmed in the service quote. The requirements planner records your preference; it does not guarantee that every configuration is available.
Can you connect two office networks?
A site-to-site requirement can be scoped, but gateway support, network addressing, routing and access policies need review. Share the network plan without passwords, private keys or other secrets in a general enquiry.
CONNECTED SERVICES
Related infrastructure services
Review your VPN access requirements.
Share the users, devices, networks and private resources involved so the access design and service scope can be reviewed.
