Skip to main content
When more than one person deploys the same app, someone needs to decide who can deploy, who can delete and who can see what happened. Monk gives you organizations, roles and an audit log, checked in the tools your coding agents use.

​
What you can do

​
Work in an organization

An organization owns projects, clusters and secrets that its members share. You create one by choosing the Team plan. How: in the web dashboard. See Teams and access.

​
Invite people and give them roles

Owners and admins invite people by email and choose the role each joins with. Organization roles are owner, admin and member. On a project, people are project admins or project members. How: in the web dashboard (People, and a project’s Access tab). See Teams and access.

​
Define custom roles

Custom roles grant actions (read, deploy, delete, manage) on resource paths, across the organization or on one project. How: in the web dashboard (Settings, Roles), or ask Monk and approve the change in the local dashboard. See Teams and access.

​
Ask who can do what

Ask why someone can’t deploy, or what a role allows. How: Ask Monk. See Teams and access.

​
Give your agents instructions

Write conventions once, such as “use managed PostgreSQL in production”, at organization, project or environment level. Coding agents read them before working there. How: in the web dashboard. See Teams and access.

​
Review what happened

Activity records requests that went through Monk, such as deploy reviews, destructive actions, new clusters and secret requests, with who made each one and its outcome. Filter by project and person. How: in the web dashboard (Activity). See Web dashboard.

​
Share clusters and secrets

Organization secrets reach the organization’s clusters, for members with permission. Each cluster’s page shows who has access to it and who can delete it. How: Ask Monk to add a secret at organization scope and approve it in the local dashboard; see cluster access in the web dashboard. See Secrets and configuration.

​
Try it

​
Good to know

  • Instructions for agents are guidance, not enforcement. Roles and cluster policies are what restrict actions.
  • Monk has no single sign-on and no team analytics.
  • Personal scope has no people. Teams need an organization.

Teams and access

Roles, instructions and Activity

Web dashboard

People, Activity and Settings

Approvals and secrets

What needs your approval