Skip to main content

​
Two Levels of Configuration

Agent configuration follows a simple model. You set organisation-level defaults that apply everywhere, then optionally override them for specific workspaces. This gives you central control with the flexibility to treat some teams differently.

​
Organisation Defaults

Your organisation settings define the baseline for each agent: its role, and what it acts on. For Gatekeeper that is your default rule and exceptions. For Data Protector that is the categories you enable and any instructions you assign. These defaults apply to every workspace unless a workspace overrides them. Set your defaults to reflect your most common needs. Workspaces that need different treatment can be configured on their own.

​
Workspace Overrides

Each workspace handles an agent in one of three ways.
Keeps your configuration central and easy to manage.
A workspace handling sensitive customer data might run Data Protector as an Enforcer while the rest of the organisation observes.
Turn an agent off for a workspace where its focus is genuinely irrelevant.

​
Rolling Out

A phased rollout reduces disruption and builds confidence.

Start in Observer

Run both agents as Observers. You get full visibility into what they catch, with no impact on your team. Stay here for a week or two.

Review and tune

Look through Assessments to understand your usage. Set your Gatekeeper policy, enable the Data Protector categories that matter, and add instructions for the specific cases.

Promote to Enforcer

Move agents to Enforcer for the workspaces where the risk justifies it. Begin with your highest-risk workspaces and expand as confidence grows.

Override where needed

Once your defaults are stable, set workspace overrides. Stricter enforcement for high-risk teams, lighter touch elsewhere.

​
Setup Checklist

Understanding agents

Roles, outcomes, and how verdicts are decided.

Instructions

Add your own rules for specific scenarios.