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 create an organization

1

First Step

Open the Monk Welcome Screen by clicking the button located in the bottom-left corner of the interface.
2

Second Step

In the Account section, next to Personal, click the drop-down icon.
3

Third Step

A new window titled Select Monk Plan/Context will appear. From the available options, select Create a New Organization.
4

Fourth Step

Enter a name for the organization you are creating and press Enter to confirm.
5

Fifth Step

You will be automatically redirected to monk.io, where you can configure the number of seats for your organization and the name of the organization. After selecting the desired number of seats, click Continue to Checkout to proceed.
6

Sixth Step

During a checkout user will be able to purchase a subscription and finalize a process of organization creation.
7

Seventh Step

After completing the subscription checkout process, you will be redirected back to your IDE. You have created an organization.
Note: This feature is billed on a per-seat basis. The monthly cost will adjust proportionally as additional seats are added.

​
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. Monk Team Features Management

​
How It Works

​
Managing Organizations

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

​
Inviting Team Members

1

First Step

To invite new members to an organization, click the Manage button located under the Account section.
2

Second Step

Within the Organization Management panel, navigate to the Invite section to add team members for project collaboration. To invite a new member:
  • Enter the user’s email address.
  • Click Invite to send the invitation.
Invite new member to organization
3

Third Step

Once an invitation has been sent, the invited user will receive an email notification. By clicking Accept Invitation, the user will join the organization and can begin collaborating with the team.Accept invite to organization

​
Member Roles

Three base roles exist: owner, admin, and member.
  • Owner: Full control over org settings, membership, clusters, environments and projects.
  • Admin: Can manage members (except owners), administer clusters, environments and manage RBAC.
  • Member: Can deploy or create/delete clusters based on org policies.
  • Custom: A user-defined role with tailored permissions designed to meet specific operational requirements (e.g., QA Tester).
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, projects, environments, 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. Monk Roles Management Via chat: 
create a role called staging-deployer with deploy access to /environments/staging/templates/**
→ See Access Control & Security for details.

​
Custom Instructions / Policies

Monk Team Features allow users to define custom instructions at both the environment and project levels.
  • Environment-Level Instructions apply to specific environments such as Development, Staging, or Production. These instructions govern how resources and infrastructure are managed within each environment.
  • Project-Level Instructions apply to a specific project within a shared workspace, ensuring consistent configuration and operational behavior across the team.
  • Organization-level Instructions apply to all organizations, like Clusters, Environments and Projects.
Monk Custom Instructions Team Feature
Create custom instruction at different scopes (organization, project, environment) to guide Monk agents to 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.

​
Cluster Management

The Cluster Management menu enables users to select and manage active clusters within the organization. In the UI: If a solution includes multiple clusters, users can:
  • View the status of each cluster (active, personal and organization clusters)
  • See the environments associated with each cluster
  • Identify projects linked to specific clusters
To manage a cluster, users must use the available action buttons within the Cluster Management interface. As shown in the screenshot below, the available actions include:
  • Add Member to Team
  • Switch Between Clusters
  • Link Cluster to Environment
  • Exit Cluster
  • Delete Cluster
Switch and Exit are used to connect your local machine to cluster and exit from it. Add Member to Team will assign your personal cluster to Organization. These controls provide administrators with centralized oversight and operational flexibility across cluster resources. Monk Team Feature Cluster Management Via Chat: All actions can be triggered through the Monk Chat in a natural language request. Monk Cluster Management via Chat
Personal clusters can be associated with an organization via the “Add to Team” button, which transfers ownership of this cluster to the selected organization and applies RBAC access policies.

​
Environments Management

Within the Environments section, users can view and manage all existing environments within the organization. From this interface, authorized users can:
  • View associated projects
  • Identify the linked cluster
  • Add custom instructions per environment
  • Delete environments when no longer needed
Monk supports both Cloud-Based and On-Premises environments. Environments can be logically separated using tag-based identification, similar to Kubernetes namespaces. This approach enables the deployment of isolated environments per tag, ensuring structured separation within shared infrastructure. For cloud-based setups, Monk provides advanced environment automation capabilities:
  • Creation of feature branches
  • Provisioning of isolated clusters
  • Deployment of the full system
  • Generation of shareable preview URLs
Once the work is completed and merged, Monk automatically cleans up and destroys temporary resources associated with the feature environment. This capability delivers strong operational isolation without requiring dedicated hardware, improving efficiency while maintaining security and separation between workloads. Monk Team Feature Environment Management

​
Workspace Management

The Workspace Management section provides visibility into all shared workspaces within the organization. From this interface, users can:
  • View the workspace name
  • Identify the associated project
  • Check the current status
Within the Workspace Management panel, authorized users can also:
  • Assign additional workspace into a project
  • Delete a workspace when it is no longer required
This centralized management ensures clear project-to-workspace alignment and supports efficient collaboration across teams. Monk Team Feature Workspace Management

​
Projects Management

Within the Projects section, users with Owner or Admin privileges can select a project and share it with team members across the organization. Administrators can also define custom instructions for each project, ensuring that project-specific standards, configurations, and operational guidelines are consistently applied. There is no limit to the number of shared projects within an organization. This flexibility enables teams to switch between projects efficiently without disrupting workflow or losing focus. The Status view provides visibility into:
  • The number of associated environments
  • Linked clusters
  • Connected workspaces
This centralized overview helps administrators monitor project scope and resource allocation effectively. Monk Team Feature Projects Management

​
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. View Logs → 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.