Skip to main content

​
What It Does

Project Organization provides structured environment management with cluster assignments, team secret sharing, and isolated deployments. Each environment can have its own cluster, secrets, and access policies.

​
How It Works

​
Environments

Environments represent deployment targets like staging, production, or dev. Each environment:
  • Links to a specific cluster
  • Has its own secrets (when using team scope)
  • Can have environment-scoped RBAC permissions
Create environments in chat: 
create staging and production environments
Monk creates environment configurations and asks which cluster each should use.

​
Cluster Assignment

Each environment links to one cluster. Multiple environments can share a cluster with different tags, or each environment can have its own dedicated cluster. Via chat: When you deploy to an environment, Monk asks which cluster to use if not already linked: 
deploy to staging
Via Clusters panel: Open the Clusters panel to see and manage environment-cluster associations.

​
Team Secret Sharing

Secrets can be scoped to workspace, user, or team. Team secrets are environment-scoped, so staging and production can have different secret values. Team secrets require:
  • An organization context
  • An environment linked to an org cluster
In chat: 
add DATABASE_URL as a team secret for staging
Secrets are stored on the cluster and available to all org members with appropriate permissions.

​
Environment-Scoped RBAC

RBAC permissions can be scoped to specific environments. For example, a role can grant deploy access to staging but not production:
  • /environments/staging/templates/** - staging templates only
  • /environments/*/secrets/** - secrets in all environments
See Access Control & Security for details.

​
Use Cases

Development → Staging → Production: 
create dev, staging, and prod environments
link dev to my-local-cluster
link staging to my-digitalocean-cluster
link prod to my-aws-cluster
deploy to all environments
Environment isolation: Each environment deploys to its designated infrastructure. Team secrets are environment-scoped, so credentials don’t leak between environments. Per-environment permissions: Create roles that grant access to staging but not production, letting junior developers deploy to staging while protecting production.

​
Managing Environments

List environments: 
what environments do I have?
Check cluster link: 
which cluster is linked to staging?
Visual management: Open the Clusters panel to see all environments and their cluster associations.