Answer: Give AI the minimum permissions needed for the workflow, separate permission from autonomy, protect credentials, log actions and require approval at consequential external boundaries.

What this means in practice

Least Privilege

Map every data source and action the AI could use, then reduce privileges until only what the workflow needs remains.

Separate Identities

Run the AI under a dedicated service identity, not a staff member’s login, so its actions can be traced and its access revoked on its own.

Scoped Api Access

Connect through access scoped to specific read, draft or write actions, and keep credentials and secrets out of prompts and documents.

Approval Gates

Require a person to approve contractual, financial, safety-critical and authoritative-record actions before they happen.

Receipts And Logs

Log inputs, decisions and actions so you can reconstruct what the AI did, when and on whose authority.

Kill Switch And Recovery

Make sure access can be disabled quickly and that there is a tested path back to the manual process.

A practical construction test

  1. Define the business outcome.
  2. Measure how the workflow performs today.
  3. Identify what AI is being asked to interpret or decide.
  4. Define what remains under human authority.
  5. Test with real examples and acceptance criteria.
  6. Measure results before expanding scale or autonomy.

Where governance fits

The AI model can change. The company’s operating rules should not change silently with it. Catha’s Governance Cage is designed to preserve the business authority layer above the model and workflow.