A team may need several authorized users to follow a documented exit-routing arrangement. Lisar Custom Exit can support eligible routing requirements, but a plan name alone does not prove that every member has the same exit. Confirm the actual configuration of each participating profile.
Eligibility and routing are separate checks
Custom Exit is included in eligible Enterprise and Custom arrangements. Availability still depends on router capability and route availability. Check the profile in the Lisar Panel and compare the plan features. A tailored business design may need review before it is configured.
A plan grants eligibility; the profile and available infrastructure determine the route. Do not assume that buying the same plan automatically links several accounts or makes their exit behavior identical.
Define the requirement before choosing an exit
Write down which users and devices participate, whether they connect individually or through a compatible router, and which routing behavior matters to the team. Distinguish a preferred exit location from a requirement for a particular public address. Custom Exit eligibility does not, by itself, promise a dedicated or static IP.
Keep this record separate from credentials and downloaded profiles. Each person should use their own authorized access. A shared routing requirement is not permission to forward one person's profile file to colleagues.
Verify each participating profile
- Confirm that the selected profile has Custom Exit eligibility.
- Review the entry and exit configuration exposed for that profile.
- For a tailored arrangement, confirm the requested route with Lisar before relying on it.
- Connect each participating device using its appropriate setup guide.
- Check the expected route for the traffic being tested and record any differences.
One public-IP check describes that request, not every app or destination. Device policy, split routing and DNS settings can affect the comparison. If two devices differ, keep the profile, client and network details in the report rather than assuming the arrangement is broken.
Router and individual-device arrangements
A compatible router can establish the tunnel for traffic routed through it. Individual-device clients establish their own tunnels. These are different operational models, with different ownership and troubleshooting needs. Review router compatibility before choosing a shared-network setup.
What to include in a business request
Send the number of users, device types, router model and firmware where relevant, required entry/exit behavior and the reason it matters to Lisar business support. Do not include credentials, private keys or complete profile files.
Custom Exit changes routing. It does not replace company access controls, change account regions or guarantee that a third-party service will accept a connection.
Frequently asked questions
Does the same plan give every colleague the same exit?Not automatically. Eligibility and each profile's configured route must be checked separately.
Is a shared exit the same as a dedicated IP?No. A routing arrangement does not establish a dedicated or fixed public address unless that requirement has been separately confirmed.
Does everyone share one profile file?No. Keep individual access and credentials separate even when the team requests similar routing.
When should we contact Lisar?Before relying on a tailored business route, specific router deployment or requirement that the available profile options do not establish.
Related guidance: VPN Location Choice: When to Use a Nearby Server and When Not To and DNS AdBlock, GeoDNS, and Custom Exit: How VPN Routing Features Work Together.