Skip to main content
Windows only. Registration screenshots are being finalized and will be added in a documentation update.
On first launch the Desktop Agent must register to your company before it starts protecting AI usage. If your administrator pre-baked the Company Access Key into the installer, registration happens automatically and you won’t see this window.

​
What happens during registration

On first launch the Agent makes sure a unique Agent ID exists on your PC — if it’s the very first run, the Agent generates one and stores it permanently in protected local storage. It then sends three things to the server: your Company Access Key, the Agent ID, and a basic hardware fingerprint of the machine. The server validates them and issues an access token, after which the Agent enters its normal operating state. You never see or manage the Agent ID or the token yourself.

​
Registering

1

Open the Agent

The registration window appears on first launch (only if the key wasn’t pre-baked into your installer).
2

Enter the Company Access Key

Paste the key your administrator gave you (issued in Desktop Agent settings).
3

Confirm

Once validated, the Agent is registered to your company. Your administrator then assigns it to a project.

​
If registration is refused

If the server rejects the registration, no token is issued and the Agent never starts protecting (or intercepting) anything — the reason is shown on the registration screen. Common reasons:
  • Your company has reached its limit on the number of Agents.
  • The Desktop Agent feature is disabled for your company.
  • The Agent ID conflicts with another registration (for example, an Agent ID was copied into a cloned machine image).
These require an administrator to resolve (raise the limit, enable the feature). There is no way to bypass a refusal from the PC.

​
Before you’re assigned to a project

A registered Agent that has not yet been assigned to a project blocks every controlled AI endpoint — requests to governed AI services are stopped until an administrator assigns the Agent to a project. This is the default-deny state, not a configurable allow/block toggle. Once your administrator assigns the Agent to a project, that project’s Control Profiles apply automatically and normal protection begins — no action is needed on your PC. See How it works.