Quick start

This guide takes you from a fresh Airentect workspace to a first enrolled endpoint. The console tracks your progress for you, so you can stop at any point and pick up where you left off.

Before you start

You need three things:

• Admin access to the Airentect console at console.airentect.com.
• Access to whatever manages your browsers, such as Google Workspace, Intune, GPO, or an MDM. For a first trial you can skip this and use a per-user install link instead.
• HTTPS access from endpoints to gateway.airentect.com. If you run a proxy or web filter, allow this host now so enrolment does not fail silently later.

The setup checklist

The Overview page shows a "Get set up" checklist. It is computed live from your actual configuration, not ticked off by hand, so an item only shows as done when the underlying thing really exists. There are five steps:

1. Configure your detection profile. Tell the classifier your country, industry, and regulations so it knows what counts as sensitive for you. Country and industry pre-fill sensible baselines. See configuring detection.
2. Set policy enforcement actions. Choose what happens when sensitive content is detected: audit, warn, redact, or block, per risk category. See configuring policies.
3. Create a deploy token and roll out the extension. Generate a reusable deploy token under Endpoints, then push the extension through Google Workspace, Intune, GPO, or your MDM. See the managed rollout guide. For a small trial, use per-user install links instead.
4. First endpoint checks in. This one completes automatically. Once a managed browser enrols, the device appears under Endpoints, usually within about a minute of policy sync.
5. Invite a teammate. Bring in another admin or reviewer from the organisation page.

Do the steps in order. Detection and policy come before rollout deliberately: the extension enforces whatever is configured at the moment a prompt is sent, so you want your profile and actions in place before real traffic arrives. Both have a Test tab, so you can prove the configuration behaves the way you expect before a single endpoint is enrolled.

Guided tours

The console includes two replayable walkthroughs alongside the checklist:

• Welcome tour. A short orientation of the console, offered on first sign-in.
• Configure and deploy walkthrough. A spotlight tour that walks through detection, policy, and the deploy page in sequence.

Both can be replayed at any time from Support, under Guides. They are useful when you invite a teammate in step five: rather than writing your own handover notes, point them at the welcome tour.

Confirm it worked

After your first device enrols, open an AI chat tool in the managed browser and send a harmless test prompt. Within about a minute you should see the event in the console. If the endpoint never appears or the event does not arrive, the troubleshooting guide lists the common causes.