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
- 1Seat count and authorization answer different questions: an available seat permits another membership, while that member’s role determines which Workspace actions are allowed.
- 2Separate identities make audit records and security investigations more useful, because an action can be associated with one teammate instead of a reused login.
- 3Removing 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.
Common use cases for platform workflows
These examples cover platform workflows broadly, not specifically Collaboration Seats.
- Running repeatable upload, import, processing, AI, storage, and notification pipelines.
- Tracking long-running media work independently from an application request.
- Referencing centrally stored credentials by name instead of sending storage secrets with each request.
Working with platform workflows
This guidance covers platform workflows broadly, not just Collaboration Seats.
A client authenticates and submits files or references together with workflow instructions. The platform validates the request, schedules dependent operations, records state transitions, and exposes results through a response, polling endpoint, or notification.
Platform concepts become reliable only when their lifecycle is explicit. Authentication, idempotency, retries, timeouts, observability, quotas, and terminal states should be designed together rather than added after failures occur.
What you gain
- Reusable workflows separate application intent from processing infrastructure.
- Stable job identifiers and lifecycle events improve observability and recovery.
- Managed queues and workers let products scale without embedding every media tool.
What it costs
- Synchronous responses are simple but keep connections open while long work executes.
- Aggressive retries improve recovery from transient faults but can duplicate work or overload a dependency.
- Higher concurrency reduces queue time until resource contention or a downstream limit becomes the bottleneck.
Before production
- 1Define authentication, authorization, idempotency, retries, and terminal error behavior.
- 2Observe queue time, execution time, callbacks, and partial results with stable identifiers.
- 3Exercise malformed, duplicate, interrupted, and unauthorized requests before launch.