Transloadit

What are Collaboration Seats?

Collaboration Seats allow people with separate email addresses and logins to work with the same Transloadit Workspace Templates and Assemblies. They avoid sharing the primary account credentials.

How Collaboration Seats work

A seat is an account-level allocation for an additional human identity, not a shared credential or a unit of processing capacity. Each assigned person authenticates separately and acts inside the Workspace according to the role attached to that membership. This lets template edits and assembly inspection be attributed to a specific login. In an operational workflow, seats are provisioned during onboarding, reviewed as duties change, and reclaimed during offboarding.

Key facts

  1. Seat count and authorization answer different questions: an available seat permits another membership, while that member’s role determines which Workspace actions are allowed.
  2. Separate identities make audit records and security investigations more useful, because an action can be associated with one teammate instead of a reused login.
  3. Removing a person’s Workspace access should be paired with review of API keys and external integrations they controlled; a seat change does not rotate machine credentials.

When Collaboration Seats matter

Assign separate seats when several developers must create Templates or inspect Assemblies in one Transloadit Workspace. Individual access improves accountability, but seat availability and permissions must match each role.

Turn media knowledge into a working pipeline

Connect uploads, processing, AI, storage, and delivery through one declarative API — with the encoding stack, scaling, and format churn handled for you.

Try Transloadit for free