How Agent Configuration Works
Agent configuration follows a two-level model. You set organisation-level defaults that apply to every workspace, then optionally override those defaults at the workspace level. This gives you centralised control with the flexibility to tailor behaviour for specific teams.Organisation-Level Defaults
Your organisation settings define the baseline configuration for every agent. This includes each agent’s role (Observer or Enforcer) and which individual rules are enabled. These defaults apply to all workspaces unless a workspace explicitly overrides them. Set your organisation defaults to reflect your most common compliance needs. Workspaces that need different treatment can be configured individually.Workspace-Level Overrides
Each workspace can override the organisation defaults using one of three modes.| Mode | Behaviour |
|---|---|
| Inherited | The workspace uses the organisation-level settings exactly as configured. This is the default for all workspaces. |
| Configurable | The workspace defines its own role and rules for the agent, independent of the organisation defaults. |
| Disabled | The agent is turned off entirely for this workspace. No evaluation occurs. |
When to Use Each Mode
- Inherited works for most workspaces. It keeps your configuration centralised and easy to manage.
- Configurable is right when a workspace has unique compliance requirements. A finance workspace might need Enforcer mode on Commercial Advisor while the rest of your organisation uses Observer.
- Disabled is appropriate when an agent’s focus area is genuinely irrelevant to a workspace. A workspace that never handles HR content might disable People Operations.
Toggling Individual Rules
Within each agent, you can enable or disable individual rules. This applies at both the organisation and workspace level.Navigate to the agent's configuration
Open the agent you want to configure from your organisation or workspace settings.
Review available rules
Each agent has a set of rules targeting specific risk areas. You see every available rule along with its current status.
Best Practices for Rollout
A phased rollout reduces disruption and builds confidence in your agent configuration.Start all agents in Observer mode
Deploy every agent as an Observer. This gives you full visibility into what the agents detect without any impact on your team’s workflows. Run Observer mode for at least one to two weeks.
Analyse findings and tune rules
Review the logs to understand your risk landscape. Disable rules that generate false positives or aren’t relevant to your organisation. Enable any rules you initially skipped.
Promote high-value agents to Enforcer
Move agents that surface meaningful findings to Enforcer mode for workspaces where those risks must be prevented. Start with your highest-risk workspaces and expand as your team builds confidence.
Configuration Checklist
Use this checklist when setting up agents for the first time.| Step | Description |
|---|---|
| Set organisation defaults | Choose a role for each agent and enable the rules that match your compliance needs. |
| Identify high-risk workspaces | Determine which workspaces handle sensitive data, HR processes, or commercial information. |
| Configure workspace overrides | Set Configurable mode for workspaces that need stricter or different enforcement. |
| Disable irrelevant agents | Turn off agents that don’t apply to specific workspaces using Disabled mode. |
| Monitor and adjust | Review findings regularly and tune your configuration over time. |
Next Steps
Understanding Agents
Review the available agents and what each one covers.
Roles and Intents
How roles determine agent behaviour.