Skip to main content

​
What It Does

Custom policies let you define rules that Monk agents follow across your organization. You write them in Markdown. Monk reads them before every action it takes. No ambiguity. No drift. Every team member gets the same behavior from Monk, every time.

​
How It Works

Admins create instruction files scoped to three levels:
  • Organization — applies to all members and clusters.
  • Environment — applies when deploying to that environment.
  • Cluster — applies when connected to that cluster.
These instructions shape everything Monk does: chat responses, project generation, infrastructure decisions, and deployments. They’re enforced automatically through RBAC — you don’t need to remind anyone to follow them. Instruction files can contain any guidance you’d give a new team member:
  • “Don’t spawn instances larger than t3.large.”
  • “Always use AWS RDS for PostgreSQL. Never self-hosted.”
  • “Require approval before deploying to production.”
  • “No public IPs in production.”
  • “Use the internal container registry only.”

​
Example Instruction File

# Team Deployment Rules

## Instance Sizing
- Use t3.medium for staging, t3.large for production.
- Never use instances larger than t3.xlarge without approval.

## Database
- Always use AWS RDS for PostgreSQL.
- Do not deploy self-hosted databases.

## Secrets
- Never store secrets in environment variables directly.
- Use team-scoped secrets for all credentials.
That’s it. Monk reads this file and applies it to every action it takes within the defined scope. Your standards persist even as the team changes.

​
Availability

Available on the Team plan only.

​
Next Steps

Access Control & Security

Set up RBAC and audit logging to govern who can change policies.

Team Collaboration

Manage your organization and invite members.