Core concepts
Together’s IAM is built around five concepts that work together:How it all fits together
The key principle: Projects are the collaboration boundary. Collaborators get access to a project, and that gives them access to everything inside it (clusters, models, endpoints, etc.). Access decisions happen at the project level, not on individual resources.Resources
A resource is anything you create or provision on Together:- GPU clusters: Clusters for training and inference.
- Fine-tuned models: Models you’ve customized with your data.
- Dedicated model inference: Always-on inference endpoints.
- Evaluations: Model evaluation runs.
- Files: Training data, datasets, and other uploads.
Organization members and project collaborators
Together uses different terminology at each level:- Organization members are users who belong to your organization. They are invited via email or provisioned through single sign-on (SSO). Each member is assigned an admin or developer role at the organization level.
- Project collaborators are users who have been granted access to a specific project. Collaborators can be organization members or external collaborators who participate in a project without belonging to the parent organization.
Product-specific access guides
Together’s IAM model applies consistently across all products. These guides cover product-specific workflows:GPU clusters
Add and remove collaborators from GPU cluster projects, and understand in-cluster Kubernetes permissions.
Next steps
Organizations
Set up your organization and manage membership.
Projects
Create workspaces and scope resources.
Roles and permissions
See what each organization and project role can do.
API keys
Create and manage project-scoped credentials.
Single sign-on
Connect your identity provider.