Organise a team
Assign preparation, creation and review with clear responsibilities.
Before you begin
- List the people who produce, approve and administer access.
- Check the collaborative features and seat count included in your plan.
Step by step
- 01
Define responsibilities
Assign a project owner and final reviewer. Product role names may vary; choose permissions according to actions actually needed.
- 02
Centralise references
Keep the brief, brand assets and naming rules together. For every correction, specify version, timestamp and expected result.
- 03
Manage team changes
Review access when someone joins or leaves a project. Transfer responsibilities and remove permissions no longer needed.
Practical example
Useful comment: “v02, 00:18: replace ‘15’ with ‘50’ in the subtitle; the speaker says fifty.”
Review checklist
- Every person uses an individual account.
- A final reviewer is identified.
- Former collaborators’ access has been reviewed.
Troubleshooting
Someone cannot see a project
Check the account, workspace and assigned permissions. Do not share passwords to work around the issue.
The team is using two versions
Designate the reference version and consolidate corrections there before resuming exports.
Keep exploring
Still missing an answer?
Prepare a question for the team