Administration

Users and roles

Three roles: Admin, Operator and Viewer. A Viewer reads; an Operator can enrol hosts and run investigations; only an Admin can raise a host’s execution policy, move a host between workspaces, or change deployment settings. Roles are assigned per user under Admin → Users.

Workspaces

A workspace scopes hosts, threads, skills and the dashboard to one team. The workspace switcher in the console changes which slice of the fleet you see; moving a host from one workspace to another is an Admin-only action.

Models

Under Settings → Models, connect an OpenAI-compatible endpoint, Anthropic, Ollama, Azure OpenAI, or Cloudflare AI Gateway. A Cloudflare AI Gateway connection takes an account ID, a gateway ID and an upstream — Workers AI, OpenAI, Anthropic, Groq, Mistral, DeepSeek or OpenRouter — and proxies through it. Test a connection before making it the default; keys are envelope-encrypted at rest.

Bring your own model — OpenAI-compatible endpoints, Ollama, Anthropic, or Cloudflare AI Gateway / Workers AI — with keys envelope-encrypted at rest.

Deployment settings

The public addresses this deployment hands to agents — the Control API URL and the Gateway URL — and the address the console itself is reached at, are runtime settings, not build-time ones. Changing them under Settings → Deployment reaches every enrolled agent within one heartbeat interval; nothing is redeployed and no host is re-enrolled. Only an Admin can change them, and a new Control API URL is dialed and confirmed reachable before it becomes live, to guard against stranding the fleet on a typo.

The execution policy: read-only vs. full

Read-only execution policy is the default on every enrolled host; the full policy is an explicit, per-host choice.

Changing a host's execution policy from read-only to full is an administrator-only action.

A newly enrolled host starts on the read-only policy: an allowlist of inspection commands, with a deny list for credential paths. Raising a host to the full policy — every command on the service account’s PATH, no allowlist — is a deliberate, per-host choice an Admin makes from the Hosts page, never something an agent does for itself.

Administrative actions — such as raising a host's execution policy or moving a host between workspaces — are recorded to an audit log with the actor, the action, the subject and the values before and after the change.