Home / Use cases
USE CASESForceLink in practice —
illustrated scenarios.
Remote work, branch connections, and off-site access — all supported by a company-dedicated cloud relay and an on-site ForceLink BOX. Illustrated scenarios for companies without dedicated IT staff, with a particular focus on professional services and healthcare where data accountability is high.
* The scenarios below are illustrative configuration examples, not records of actual deployments.
Companies without dedicated IT staff
Accounting and admin staff working from home — accessing company files
Staff want to work from home, but the company needs to keep accounting data and internal files off personal networks. There is no secure connection method in place.
Only approved Windows devices connect to the accounting server and file server via the company-dedicated cloud relay. Access to the rest of the internal LAN is denied by design.
- Accounting staff: accounting server — allowed
- Admin staff: file share — allowed
- Rest of internal LAN: denied
① Design-level containment ③ Internal resource and route control
Sales staff checking documents while out of the office
Sales staff need to view quotes and internal documents while on the road. Giving a sales device full access to the internal network is too broad.
The sales device is restricted to the document server only. The accounting server and management server are unreachable.
- Sales: document server — allowed
- Sales: accounting server — denied
- Sales: management server — denied
① Design-level containment ③ Internal resource and route control
Professional services (accounting and legal)
Accounting firm — per-staff access segmentation
The firm wants to restrict which client files and accounting data each staff member can see.
Senior staff reach the accounting server and client documents; administrative staff reach only the internal shared drive. Access is designed by role.
- Senior staff: accounting server / client files — allowed
- Admin staff: internal shared drive — allowed
- Admin staff: accounting server — denied
① Design-level containment ③ Internal resource and route control
Law firm — restricting access to case files
Lawyers need to check documents from off-site, but allowing anyone to browse all case folders is unacceptable.
Lawyers reach their case files; administrative staff reach the admin folder. The management server is denied to everyone. Access is controlled per destination.
- Lawyers: case files — allowed
- Admin staff: admin folder — allowed
- Management server: denied
① Design-level containment ③ Internal resource and route control
Healthcare and clinics
Clinic director and office manager — limited off-site access to clinic systems
The director and office manager need to check bookings and billing from outside, but exposing clinic systems to the internet is not an option.
Approved devices connect through the company-dedicated cloud relay to the booking and billing system only. The rest of the clinic LAN is not exposed.
- Director: booking system — allowed
- Office manager: billing server — allowed
- Rest of clinic LAN: denied
① Design ② Drop-in deployment ③ Internal resource and route control
Branch clinic and visiting staff — accessing only the systems they need at the main clinic
Staff at a branch clinic or on home visits need to connect to the main clinic, but full access to the main LAN is too broad.
The branch clinic reaches the business system; visiting staff reach the file server. The management server is blocked. Connections are limited to what each role needs.
- Branch clinic: business system — allowed
- Visiting staff: file server — allowed
- Management server: denied
① Design-level containment ③ Internal resource and route control
From anywhere — only what each person needs.
Connections from home, off-site, and branch offices are consolidated through a company-dedicated relay. Inside the office, each person reaches only the servers they need.
Good fit for these situations
- You want Windows devices to connect to internal systems securely
- There is no dedicated IT person on staff
- You want to restrict each user to specific destinations
- You work in professional services, healthcare, or another field with strict information accountability
Situations where another solution may fit better
- Mac, iPhone, or Android is the primary device
- MFA or IDaaS integration is a hard requirement (MFA support is under consideration — not currently available)
- You need a full SASE, CASB, or DLP stack in a single product
- You need per-application-name control (ForceLink controls at the destination IP / port / protocol level)
* We aim to be honest about what ForceLink does and does not do today. See the comparison page →
Want to review a configuration for your own environment?
Tell us about your internal servers, number of users, and connection locations. We will propose a ForceLink configuration at no charge.