Set up network access
Plan approved office and VPN connections for your organisation.
Network access is recommended for organisations with managed office connections or a company VPN. It adds a network requirement alongside sign-in, multi-factor authentication and account permissions.
Before you enable it
Ask your IT provider for the static public IP addresses or ranges used by each office and your company VPN. These are internet exit addresses, rather than Wi-Fi names or local device addresses. Plan how remote staff will connect before enabling restrictions.
Set up your approved networks
An organisation administrator can open Organisation → Security → Network access. Add and name each office or company VPN network. Include the connection you are currently using, then enable Require an approved network and review the confirmation.
Security changes may require you to verify your identity again. The policy applies across the organisation and its linked dealerships, including administrators. People already signed in are blocked on their next protected request if their network is not approved.
What it protects
An approved IP does not sign someone in or grant permissions. It adds another requirement: the connection must come from an approved network. Missing or invalid IP information denies access when restrictions are enabled.
Network access does not identify individual devices or prove a person’s physical location. Keep strong account authentication and your office and VPN security in place.
Keep access working
Update the approved networks when your IT provider changes your public addresses. Keep an approved connection available while changing the policy. If everyone is locked out, follow Restore access after a network change.
Add an approved network
Check Your current IP while connected to the office network or VPN you plan to approve. Select Add network, or Use current IP to fill in your current address. Enter a Network name and its Public IP address or range, then select Save network.
Autopilot supports IPv4, IPv6 and CIDR ranges. Private, reserved and example addresses are rejected. Address validation checks format and suitability; ask your IT provider to confirm the addresses belong to your intended connection.
You can store up to 50 networks. Duplicate networks and ranges that approve every address are rejected.
To enable restrictions, turn on Require an approved network, review the warning, then select Enable restrictions. Autopilot prevents you from enabling restrictions with a list that excludes your current IP.
Keep the approved list up to date
Edit a saved network’s name or address. Valid changes save after you pause typing; check the Saving… or Saved status. Remove networks that are no longer used, while keeping your current connection approved when restrictions are enabled.
If identity verification is required, complete it and check that the change shows Saved when you return. If verification is interrupted, the change remains unsaved. Invalid input is not saved. Changes are recorded in security activity. If another administrator changes the policy while you are editing or verifying, reload the latest settings and review your changes.
Turn off Require an approved network to allow access from other networks again. Sign-in and account permissions continue to apply.
Remove addresses your organisation no longer uses
Review the approved list when an office closes, a site is removed, your internet provider changes your public IP, or your company VPN rotates or retires an exit address. Remove old addresses and ranges once your organisation no longer uses or controls them. Do not leave them approved as a backup.
Public IP addresses can be reassigned to other customers after they are released. An old address left on your list could let its new user satisfy your network requirement. They would still need valid sign-in details and account permissions, but the address would no longer represent an approved business connection.
For a planned change, confirm the replacement address with your IT provider, add it, and check that staff can connect through it. Then remove the old entry, ideally before the old address is released. Keep an approved administrator connection available throughout the change. If the old address has already changed and nobody can connect, follow Restore access after a network change.
Review approved ranges too: keep them limited to addresses your organisation needs and controls. Include this check when closing a site or retiring a VPN, and review the list periodically with your IT provider.
Understand the boundary
These rules protect authenticated organisation and linked dealership access. Public sharing links are separate. Information already displayed or downloaded cannot be recalled, and a request already in progress may finish.