Skip to main content

​
What It Does

Team Collaboration lets multiple people work on shared infrastructure under a single organization. You can invite members, assign roles, associate clusters with the org, share secrets, and control access with RBAC. Organization and cluster management live in the IDE panels, while day-to-day operations, secrets, and RBAC can be handled through chat.

​
How to Access

Organization panel: Open from the Monk Dashboard (click the org/team button) or run Monk: Manage Organization from the command palette. Clusters panel: Open from the Monk Dashboard (click the clusters button) or run Monk: Manage Clusters from the command palette. Both panels are also accessible from the Welcome screen when logged in.

​
How It Works

​
Managing Organizations

The Organization panel shows the org overview (plan, tokens, seats), a members table, pending invites, RBAC role assignment, and cluster policy settings. Use the org selector at the top to switch between personal and organization contexts.

​
Inviting Team Members

In the Invites section, enter an email, pick a role, and click Invite. Monk generates a token and copies it to your clipboard. The invitee enters that token during setup to join the org.

​
Member Roles

Three base roles exist: owner, admin, and member.
  • Owner: Full control over org settings, membership, and clusters.
  • Admin: Can manage members (except owners), administer clusters, and manage RBAC.
  • Member: Can deploy or create/delete clusters based on org policies.
Owners can change roles and remove members. Admins can remove members except owners.

​
RBAC

RBAC extends the base roles with custom roles and fine-grained permissions. Create roles with specific access to resources like templates, secrets, clusters, and audit logs. Permissions can be scoped to specific environments. In the UI: Click Manage Roles in the Organization panel to create, edit, and assign roles. Via chat: 
create a role called staging-deployer with deploy access to /environments/staging/templates/**
→ See Access Control & Security for details.

​
Cluster Management

The Clusters panel displays your active cluster, personal clusters, and organization clusters. Personal clusters can be associated with an org via the Add to Team button, which makes the cluster visible to all org members and syncs org membership to cluster users.

​
Access Policies

Configure policies in the Organization panel under Cluster Policies:
  • Create policy: Controls who can create or add clusters.
  • Default delete policy: Applies to newly created clusters.
Per-cluster delete policies can be adjusted from each cluster card in the Clusters panel.

​
Shared Secrets

Secrets can be scoped to workspace, user, or team. Team secrets require an organization context and an environment linked to an org cluster. In chat, ask Monk to add or list secrets and specify the team scope: 
add my-api-key as a team secret
Team secrets are stored on the cluster and available to all org members with appropriate permissions.

​
Audit Log

The audit log records organization actions: builds, deployments, cluster operations, and secret changes. View recent events in the Welcome screen or the Activity panel. Owners and admins see team-wide activity; members see their own. → See Access Control & Security for more on audit logging.

​
What Makes This Different

Traditional team infrastructure management requires IAM users per cloud, SSH key distribution, and manual coordination. With Monk, you create an organization, invite members, and assign roles. Team members get appropriate access automatically across all infrastructure.

​
Coming Soon

Custom Instructions / Policies COMING SOON Create instruction files at different scopes (organization, environment, cluster) so Monk agents follow team-specific rules. Include playbooks, do-and-don’t rules, and preferred defaults like “do not spawn large instances” or “always use a specific database provider.” Available on the Team plan only. → See Custom Knowledge for details.