Skip to main content

​
What It Does

Team Collaboration in Monk enables multiple users to work together on deployments and infrastructure under shared organizations. Create organizations for your team, invite members, assign roles, and manage shared clusters with fine-grained access control. All team management happens through visual UI panels in your IDE - not via chat.

​
How It Works

​
Managing Organizations

Access the Organization panel from your IDE sidebar (or status bar): What you can do:
  • Switch between organizations (dropdown selector)
  • View organization overview (plan, usage tokens, seats)
  • Manage members and their roles
  • Send invitations to new members
  • Configure cluster policies
  • View organization clusters
UI Layout:
  • Left column: Overview card, Cluster settings
  • Right column: Members table, Invitations section
  • All actions done via buttons, dropdowns, and forms

​
Inviting Team Members

In the Organization panel:
  1. Select your organization from the dropdown at the top
  2. Scroll to the Invites section
  3. Enter team member’s email address
  4. Select role (Member or Admin)
  5. Click Invite button
  6. Invitation token is generated and automatically copied to clipboard
  7. Share the token with your teammate
Invitation process:
  • Invitee receives invitation token
  • They enter token during Monk setup
  • Automatically added to organization
  • Gets access based on assigned role

​
Managing Existing Members

In the Members table:
  • View all organization members
  • See each member’s role (Owner, Admin, Member)
  • Owners can: Change member roles via dropdown, Remove members
  • Admins can: Remove members (except owners)
  • Members can: View only (no management)
Owner badge (green) - Full control Admin badge (blue) - Can manage members Member badge (gray) - Standard access

​
Role-Based Access Control

Three roles with different permissions: Owner:
  • Full control over organization
  • Invite and remove members
  • Manage all clusters
  • Change organization settings
  • Delete organization
  • Configure access policies
Admin:
  • Invite and remove members (except owners)
  • Manage all clusters
  • Deploy to all clusters
  • Configure some organization settings
  • Cannot delete organization
Member:
  • View organization clusters (by default)
  • Deploy based on organization’s deploy policy
  • Create clusters based on create policy
  • Delete based on delete policy

​
Cluster Management

Open the Clusters panel from your IDE sidebar to manage clusters: What you see:
  • Active cluster - Currently connected cluster (if any)
  • Personal clusters - Your individual clusters
  • Organization clusters - Grouped by organization, showing your role
For each cluster:
  • Switch button - Connect to this cluster
  • Users button - View who has access
  • Add to Team button (personal clusters) - Associate with organization
  • Delete button - Remove cluster (if you have permission)
Adding Personal Cluster to Organization:
  1. Find the cluster in “Personal Clusters” section
  2. Click Add to Team button
  3. Select organization from dropdown
  4. See warning about what will happen:
    • All org members get access
    • Cluster becomes visible to org
    • Org deploy policy applies
  5. Click Associate
Organization cluster view: Shows all clusters for each organization with:
  • Organization name and your role
  • Cluster count
  • Create policy and default delete policy
  • Individual cluster cards
Managing delete policies: For organization clusters (if you’re admin/owner):
  • Click edit icon next to delete policy
  • Select new policy from dropdown (owner/admin/member/creator/locked)
  • Click Save

​
Access Policies

Organizations have access policies that control what members can do. Configure these in the Organization panel. In the Cluster Settings card (admins/owners only): Create Policy - Who can create or add clusters:
  • Owners only
  • Owners and admins
  • All members (default)
Select from dropdown and click Save Settings. Default Delete Policy - For new clusters:
  • Owners only
  • Owners and admins
  • All members
  • Creator only
  • Locked (no one can delete)
This applies to newly created clusters. Existing cluster policies can be changed per-cluster in the Clusters panel. Per-Cluster Delete Policy: In the Clusters panel, each organization cluster shows its delete policy. If you’re an admin/owner, click the edit icon to change it:
  • owner
  • admin
  • member
  • creator (only cluster creator can delete)
  • locked (must unlock first)
How policies work:
  • Create policy - Checked when creating new clusters
  • Delete policy - Checked when deleting clusters (per-cluster setting)
  • Violating policy shows “You don’t have permission” error

​
What Makes This Different

Traditional team infrastructure management requires:
  • Setting up IAM users in each cloud provider
  • Managing SSH keys and access credentials
  • Complex permission systems per provider
  • Coordinating deployments across team manually
  • Sharing credentials insecurely
With Monk: Create an organization, invite members, assign roles. Team members get appropriate access automatically across all infrastructure.

​
Key Benefits

For Developers:
  • Work on shared clusters with appropriate permissions
  • No manual credential sharing needed
  • Deploy based on your role
  • Clear visibility into what you can access
For DevOps/Admins:
  • Onboard entire team in minutes
  • Control access with simple policies
  • Complete visibility into team activity
  • No cloud provider IAM complexity
For Organizations:
  • Centralized infrastructure management
  • Consistent access control across clouds
  • Reduced risk of unauthorized changes
  • Single pane of glass for all team infrastructure

​
Managing Your Organization

​
Opening Organization Panel

Access the Organization panel from:
  • Click Monk icon in IDE sidebar
  • Select “Organization Management” from status bar
  • Or use IDE command palette and search “Monk Organization”
Only owners and admins can open the Organization panel (members have read-only access).

​
Organization Overview

The overview card shows:
  • Organization name
  • Plan type (badge at top right)
  • Usage tokens progress bar with remaining/total
  • Bonus tokens (if any)
  • Seats used/total

​
Members Management

The Members table shows all organization members: For each member:
  • Email address
  • Role badge (owner/admin/member)
  • Actions: Remove button (if you have permission)
Owners can:
  • Change member roles (dropdown in role column)
  • Remove any non-owner member
Admins can:
  • Remove members (except owners)
  • Cannot change roles
Members can:
  • View members only

​
Sending Invitations

In the Invites section:
  1. Enter email in the input field
  2. Select role from dropdown (Member or Admin)
  3. Click Invite button
  4. Invitation token appears at top of panel
  5. Token automatically copied to clipboard
  6. Share token with invitee
Pending invites table shows:
  • Email address
  • Role
  • Created date/time
  • Revoke button (to cancel invitation)

​
Cluster Settings

Configure organization-wide policies (admins/owners only): Who can create or add clusters:
  • Dropdown with options: Owners only, Owners and admins, All members
  • Controls who can provision new infrastructure
Default delete policy for new clusters:
  • Dropdown with options: Owners only, Owners and admins, All members, Creator only, Locked
  • Applies to newly created clusters
  • Per-cluster policies can override this
Click Save Settings to apply changes.

​
Coming Soon

Capability-Based Access Control COMING SOON Fine-grained, resource-level permissions:
  • Grant specific capabilities on individual resources
  • “Can deploy to staging-cluster but not production”
  • Different permissions per environment, cluster, or service
  • Capability grants for autonomous agents
→ See Capability-Based Access Control for details