Solution
Day-one access, before the networks merge.
Two companies, two directories, two networks that must not touch yet. Inlinea publishes the applications each side needs into one Workspace, signs people in with their own identity provider, and grants reach per resource, so integration can proceed without a flat network.
Before and after
What changes
Today
- Months of network integration before anyone can work together
- Duplicate accounts and a second VPN for the acquired company
- Overlapping address ranges that block a flat merge
- No visibility across the two estates
With Inlinea
- Applications from both sides in one Workspace on day one
- Each person signs in with their own directory
- Routing devices reach each estate; overlapping ranges never meet
- One set of logs across both
What solves it
The capabilities behind it
- ZERAApplications published as cards; no network merge needed to use them.
- Multiple identity providersBoth directories sign people in; Directory Sync brings their groups.
- Routing devicesOne in each estate; routes granted by rule, so address overlap is a non-issue.
- Access DiagnosticsExplain access across both estates during the messy middle.
A scenario
How a day goes
- 1Signing dayA routing device is installed in the acquired company's data center. Its finance and HR applications become cards in your Workspace for the integration team.
- 2Week twoThe acquired company's staff sign in with their own directory and see the group collaboration tools you chose for them.
- 3Month sixNetworks are merged, or never are. Access was never waiting on it.
Questions buyers ask
Do we have to merge directories?
No. Inlinea signs people in with either provider and keeps the groups it needs from each. Merge later, or not at all.
What about overlapping address ranges?
Routing devices reach each estate separately and routes are granted by rule, so the two ranges never need to meet on one network.