Sign in

Find your organisation

Every organisation has its own Inlinea address. Type the first word of yours, or the whole address, and we will take you there.

Take the tourBook a demo

Product tour

Six chapters. Nothing to install.

Each chapter is a working piece of the platform you can operate here. Start anywhere.

Chapter 1

Two doors, one policy

SaraManaged laptop · Inlinea AgentA contractorPersonal laptop · browserZERA gatewayOne policyIdentityGroupTrust CheckAccess RuleFinance appBuild server (SSH)HR portal
Sara's managed laptop reaches resources over the encrypted private network with the Inlinea Agent. A contractor's personal laptop reaches them through ZERA in a browser. Both pass the same identity, group, Trust Check and Access Rule. The contractor is refused the build server, and the reason is shown.
  • Two ways inA managed laptop through the agent and a contractor's browser through ZERA.
  • One decisionIdentity, group, Trust Check and Access Rule tick in turn; only a passed decision lights in Control Cyan.
  • Replay a pathSwitch the device or the resource and watch the policy decide again.

Chapter 2

Publish, make it yours, secure the browser

Add a private application, a Windows server and a SaaS bookmark; change the preset and language; turn on a watermark and remove the extension.

apps.organisation.example
  1. Add a private web application, a Windows server as a Secure Session and a SaaS bookmark. Each lands in the Workspace, behind your sign-in and your Access Rules.

Chapter 3

The front door, per group

Finance sees six cards.

apps.organisation.example
  • Visibility per groupFinance sees six cards, contractors see two, engineering sees five.
  • Three kinds of cardProtected Services, Secure Sessions and Bookmarks in one catalogue.

Chapter 4

A Secure Session, with evidence

finance-desktop.example.com
Ledger
Accounts payable214 items
Approvals waiting12
Last closing30 Sep

Establishing a secure session

Inlinea is verifying your access and connecting you to the resource.

  • Managed credentialThe gateway signs in; the person never sees the password.
  • Controls that holdA watermark names the person; a paste is blocked before data reaches the browser.
  • Session EvidenceRecorded on the server, replayed with keystroke markers, ended by an administrator.

Chapter 5

Ask why

Access Diagnostics evaluates the real rules and simulates a change without saving it.

Try these questions
Not allowedMaya can't reach Grafana: no Access Rule allows it.
maya-mbamacOS · 100.64.8.15Not allowed
  1. This is what blocks accessNo Access Rule allows itNo enabled rule has a source group of maya-mba and a destination that includes Grafana.Access Rules

Sample organisation: people, devices, rules and Trust Checks from the Control Center's own example data.

Chapter 6

Browser Security: turn a control on and watch the page change

Browser Security policy · Finance staff

Apply a preset

6 of 10 controls on

Clipboard
Transfer
Capture

What this does

  • Only a browser with a current attestation opens this page; the gateway checks on every request.
  • 6 in-page controls are enforced, and every blocked attempt lands in the Browser Security Log.
  • A watermark names the person and the time across the page.
erp.example.comBrowser attested

erp.example.com · Finance

Quarterly forecast

Revenue
41.2 M
Operating cost
28.7 M
Margin
30.3%
Try the buttons on the page, then pull the extension.

Admission, decided by the server, is the security control. In-page controls are containment with an audit trail: a determined device owner can work around them, and every attempt is logged.

Chapter 7

Brand the Workspace

Change the preset, the colour, the mode and the language; the contrast chip runs the checks Studio runs before publishing.

StudioReady to publish · lowest text contrast 6.2:1
Preset
Brand colour

Applied exactly as chosen, the way the Colors editor applies it.

Appearance
Language
apps.organisation.exampleLive preview
A sample Workspace re-rendered live from the real Studio presets. The contrast chip runs the same checks Studio runs before publishing: text below 4.5:1 blocks publishing.

Seen enough? See it on your own applications.