Skip to main content
You can use Monk on your own (personal scope) or in an organization that you share with other people. An organization owns projects, clusters and secrets, and decides who can do what with them.

​
Personal and organization scope

  • Personal scope is yours alone. It has no people, and its projects and clusters belong to you.
  • An organization has members, roles and shared clusters. You create one during team onboarding, where you choose seats, invite people and check out. The web dashboard has a switcher between your personal scope and each organization you belong to.
Each workspace on your computer is bound to one scope and one project, so Monk knows where new clusters, environments and secrets belong.

​
People and invites

In the web dashboard, People lists the members of the organization and what each one works on. Owners and admins invite people by email and choose the role each person joins with. Only owners and admins can invite people or change roles.

​
Organization roles

Every member has one organization role:

​
Project roles and custom roles

A member gets access to a project through a role given on that project. You do this in the project’s Access tab.
  • Project admin manages the project’s environments, clusters, secrets and deploys.
  • Project member deploys the project and reads its environments.
Custom roles, under Settings, Roles, list permissions as pairs of an action and a resource path, for example deploy on a project’s environments. The actions are: A custom role can be given across the whole organization or on one project. The system roles (owner, admin, member, cluster-owner, project-admin, project-member) can’t be edited. The checks run in Monk’s tools and on the platform. A request your role doesn’t allow is refused, whether it comes from the dashboard or from a coding agent. You can also manage roles from your coding agent. Changes open an approval in the local dashboard.

​
Cluster policies

Under Settings, an organization sets who can create clusters and who can delete clusters by default. Each cluster’s page in the web dashboard shows who has access to that cluster and who can delete it.

​
Instructions for the agent

Instructions are notes your coding agent reads before it works in a scope. They can be set at three levels:
  • Organization, in Settings
  • Project, in the project’s Settings
  • Environment, on the environment’s page
Use them for team conventions, such as “use managed PostgreSQL in production” or “keep staging on the smallest instance type”. They are guidance for the agent, not enforcement. To actually restrict what someone can do, use roles and cluster policies.

​
Activity

Activity is the audit log. It records the requests that went through Monk, such as deploy reviews, destructive actions, infrastructure changes, new clusters, cluster grows, and secret, credential and certificate requests. Each entry shows who made it, its outcome and its details, grouped into traces. You can filter Activity by project and by person (everyone or only your own).

Web dashboard

Where these settings live

Security

Approvals and secret scopes

Environments and previews

Projects, workspaces and environments

Cost and usage

Billing alerts and usage