Skip to main content
A Project is an isolated workspace within your Organization. Resources, API keys, and Collaborator membership are all scoped to Projects. Think of a Project as the collaboration boundary: when you give someone access to a Project, they can use everything inside it.
Multi-Project support is in early access. All Organizations have a default Project. Contact support to enable additional Projects.

​
How Projects Work

Organization
  Project A
    Cluster 1
    Cluster 2
    Fine-tuned Model
    Volume (shared storage)
  Project B
    Cluster 3
    Endpoint
    Evaluation
Each Project contains its own set of resources. Collaborators of Project A cannot see or access anything in Project B, and vice versa. This lets you separate work by team, environment (dev/staging/prod), workload type, or customer.

​
Project Resources

Resources belong to a Project and are accessible to all Project Collaborators (subject to their role), including:
  • GPU Clusters — Instant clusters for training and inference
  • Volumes — Shared and local storage attached to clusters
  • Fine-tuned Models — Custom models trained on your data
  • Dedicated Endpoints — Always-on inference endpoints
  • Evaluations — Model evaluation runs
  • Files — Training data and uploads

​
Default Project

Every Organization has a Default Project. A few things to know about it:
  • All Organization Members are automatically granted access to the Default Project
  • All historical account usage and resources that pre-date Projects are attributed to this Project (work in progress)
  • All Playground usage is attributed to this Project
  • It has an “Organization Default Key” that is only accessible to the Organization Owner (see API Keys & Authentication)
  • Because all Organization Members have access, do not use the Default Project for sensitive resources. Create a separate Project for those.

​
Managing Project Collaborators

You can manage Project Collaborators from Settings > Project > Collaborators.

​
Adding Collaborators

  1. Go to Settings > Project > Collaborators
  2. Click Add Collaborator
  3. Enter the user’s email address
  4. Click Confirm
The target user must already have a Together account. The Collaborator is added immediately upon confirmation. New Collaborators are added with the Member role by default, unless they are an Organization Admin (who are Admins for every Project by default). An Admin can change their role after they have been added.
The user must already belong to your Organization, unless they are being added as an External Collaborator.

​
Removing Collaborators

  1. Go to Settings > Project > Collaborators
  2. Find the Collaborator you want to remove
  3. Click the three-dot menu next to their name
  4. Select Remove User
  5. Confirm the removal
Removing a Collaborator revokes their access to all resources in the Project, including clusters, volumes, SSH access, and management capabilities. This takes effect within minutes.

​
Project API Keys

Each Project has its own API keys. These keys authenticate API requests and are scoped to the Project’s resources. For details on creating, managing, and rotating API keys, see API Keys & Authentication.

​
Common Project Structures

Teams organize Projects differently depending on their needs:
StrategyExampleBest for
By teamml-research, platform-eng, applied-aiLarge Organizations with distinct teams
By environmentdevelopment, staging, productionTeams that want resource isolation across environments
By workloadtraining, inference, evaluationTeams that want to separate compute budgets
By customercustomer-a, customer-bService providers managing multiple clients

​
Next Steps

Roles & Permissions

What Admins and Members can do within a Project

API Keys

Create Project-scoped credentials

Cluster Access

Product-specific guide for managing cluster access