What is a Collaborator?
A Collaborator is a Transloadit user granted role-based access to a Workspace through an individual login. Depending on permissions, the user may manage Templates, view Assemblies, and belong to multiple Workspaces.
How Collaborators work
A collaborator is the identity-to-Workspace membership that connects an individual Transloadit account with a team environment. The membership carries authorization for Workspace resources and remains separate from ownership of the person’s login. Because one account can participate in more than one Workspace, permissions are evaluated in the active Workspace context. Collaborators appear in governance workflows for invitation, role changes, access review, and removal.
Key facts
- 1Authentication establishes which user signed in, while the collaborator role authorizes actions in a particular Workspace; the two checks should not be treated as interchangeable.
- 2Access to one Workspace does not imply access to another, even for the same account, so integrations and support procedures must preserve the Workspace context.
- 3Offboarding should remove the membership rather than transfer or share the user’s login, preserving the integrity of activity attribution and the user’s other Workspace memberships.
When Collaborators matter
Add a Collaborator when a teammate needs Workspace access without receiving shared account credentials. Grant only the required role, and remove access promptly when responsibilities or organizational membership change.
Common use cases for platform workflows
These examples cover platform workflows broadly, not specifically Collaborators.
- 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 Collaborators.
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.