Skip to main content
An organization is your company’s account on Together. It’s the top-level container for everything: projects, members, resources, and billing. Every Together account belongs to one organization. Manage your organization from Organization Settings in the Together dashboard.

​
Organization membership

Members join your organization using either single sign-on (SSO) or invitation-based (OAuth) authentication. These methods are mutually exclusive — you must choose one or the other.

​
Single sign-on (SSO)

If your company uses an Identity Provider (Okta, Google Workspace, Microsoft Entra, JumpCloud) with SSO configured, members authenticate through your IdP and are automatically provisioned into your organization. See Single Sign-On (SSO) for setup instructions.

​
Invitation-based (OAuth)

Admins in paid tier organizations can invite members by email. Here is how:
  1. Go to Organization > Member Settings.
  2. Select Invite Member.
  3. Enter the user’s email address.
  4. Select Send Invitation.
Invitations expire after 7 days. The recipient receives an email with a link that opens the Invitations page, where they can accept or decline. Clicking the link never accepts on its own. New users create a Together account when they sign in from the link. Existing users can accept directly, or switch organizations if they already belong to one.

​
Switching organizations

You can only belong to one organization at a time, so accepting an invitation moves you out of your current organization. What that takes depends on your relationship to it:
  • If you are not its billing owner: You can accept right away. Your current organization continues without you.
  • If you are its billing owner and only member: Accepting deletes your current organization. Before you can accept, the organization must have no outstanding balance and no remaining prepaid credits. Use or transfer any remaining credits first.
  • If you are its billing owner and it has other members: Contact support to transfer billing ownership before you can move.
The Invitations page tells you which of these applies.

​
Removing members

Admins can remove members at any time:
  1. Go to Organization > Member Settings.
  2. Find the member you want to remove.
  3. Select the three-dot menu next to their name.
  4. Select Remove Member.
Removing a member revokes their access to all projects and resources in the organization. Resources they created (models, endpoints, files) remain in the project.
If your organization uses SSO, a removed member may be re-provisioned automatically the next time they authenticate through your IdP. To fully revoke access, remove or deactivate the user in your Identity Provider.

​
Roles

Organizations support two roles: admin and developer. For a full breakdown of what each role can do across the platform, see Roles & Permissions.
Roles and permissions are being progressively rolled out across products and services. Today, the primary distinction is that admins can manage infrastructure and team membership, while developers can use resources but not modify them. See Roles & Permissions for details.

​
Projects

Projects are isolated workspaces within your organization. They scope resources, API keys, and membership so teams can work independently. Every organization starts with a default project. All members are automatically added to it when they join. Create additional projects to separate resources by team, environment, or workload. For full details on creating and managing projects, see Projects.

​
Privacy

Privacy toggles for prompt history, training opt-in, and passthrough models are on the main Organization Settings page. Only organization admins can change them. See Privacy and security for what each toggle controls.

​
Billing

Billing is consolidated at the organization level. All usage across all projects and members rolls up to a single bill. Individual members are not billed separately. Members can jointly purchase and spend credits. For details, see Credits & Billing.