Name the jobs before the roles
Write down who edits episodes, approves releases, reviews reports, manages team members and pays the bill. One person may hold several responsibilities, but that does not mean every collaborator needs the same access. Start from the actual work rather than granting broad permissions because the narrow role is unfamiliar. The point is to enable a clear job, not to make ordinary publishing needlessly difficult.
Match the documented role
Transistor documents distinct owner, administrator, member and analytics access. Check the current capabilities against your responsibility list rather than inferring them from the role names. In particular, access to episode work is not automatically access to billing or team administration. Use a non-sensitive demonstration to confirm the intended person can finish their task without exposing another client’s work or unrelated account settings.
Keep approvals understandable
Technical permission and editorial permission are different. A producer may be able to publish while your organization still requires a reviewer’s approval. Record that routine in the working process and avoid pretending that the hosting role enforces a policy it does not actually implement. Conversely, do not make every minor edit depend on an owner if the agreed workflow safely permits a delegated role.
Review access at meaningful changes
Check roles when a person joins, leaves or changes responsibilities and when a show changes owner. Preserve useful work before removing access and do not delete content merely to tidy the team list. Keep individual account use where supported instead of distributing one shared password. A good access model remains understandable to the next administrator and gives the team a supported recovery route when somebody is unavailable. For example, a client receiving reporting may need analytics access rather than permission to alter episode descriptions. Verify that distinction in the current role documentation before granting access.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Transistor team roles — Merchant documentation · transistor.fm · Merchant-controlled · checked 2026-09-19