Reference
Capability scope
Your signed scope identifies the capabilities included for your organisation. Integrations, configuration and rollout are agreed before work begins.
How to read this page
Use the table to see which decisions belong in the engagement scope. Your onboarding plan records the agreed setup, responsible people and review process.
Capability arrangements
| Capability | How it is agreed |
|---|---|
| One gateway (MCP) | Connection scope agreed during onboarding |
| Roles from your directory | Directory and group mappings agreed for your organisation |
| Per-tool and per-action permissions | Defined for named roles, tools and actions |
| Read-first connectors | Starting read scope defined in the connector specification |
| Human approval for writes | Approvers and permitted writes defined in the workflow |
| Approval channels | Routing chosen for the agreed workflow and technical requirements |
| Maker-checker | A second approver included where the agreed policy requires it |
| Audit trail | Fields, reviewer access and retention documented in the agreement and DPA |
| Audit export | Review and export method agreed with your organisation |
| Custom connectors | Systems, actions, testing and acceptance defined in the statement of work |
| Shadow AI assessment | Sources, assessment method and deliverables agreed in the scope |
| Continuous discovery | Ongoing monitoring, where included, scoped separately |