Teams and permissions
Team administration ensures that members use the appropriate projects, shared assets and permissions. Use individual member accounts so that work remains attributable.
Members and roles
Administrators review members and available role settings in team management. Before working, members should verify the active team, accessible projects and shared libraries. The current administration interface determines the assignable roles.
| Work | Suggested responsibility |
|---|---|
| Script and parsing rules | Writer/director maintains rules; administrator publishes team versions |
| Characters and voices | A designated owner approves main appearances, variants and voices |
| Shot generation | Assign by episode or scene |
| Review and export | A designated reviewer approves selected versions and deliverables |
| Shared assets | Administrators or authorized members maintain naming and sharing scope |
These are production recommendations, not a claim that identical permission-role names exist in the studio.
Publishing custom parsing rules
Members can write and test rules. A team administrator publishes a successfully analyzed version. Review a representative episode and record the rule's intended use before publishing; do not replace a stable version with an unfinished test.
Canvas collaboration
Canvas and 3D Director are enabled by default. Canvas supports real-time work within a team, with editing locks on active nodes. Divide work by region, character or episode to avoid simultaneous changes to a critical asset.
Before deleting assets, merging characters or reanalyzing episodes, coordinate the affected scope and preserve required results. These operations can affect material used by other members.
Investigate access problems
Check the login account, current team, project ownership, member status and visible permissions. To share another person's private material, have its owner place the approved version in an appropriate shared library instead of exchanging login credentials.
Record the project, entry point, time and error for an administrator. Do not include passwords, verification codes or session details in support reports.
Enable member login and team membership
The primary account administrator uses member or subaccount management to:
- Create a production subaccount.
- Authorize that subaccount to sign in.
- Assign it to the intended team, checking both account and team names.
- Have the member sign in with their own account, choose the team and verify access to the expected projects and shared assets.
Login authorization and team membership are separate settings. If the member can sign in but sees no projects, check membership first. If membership exists but sign-in fails, check login authorization and account status.
Assign team administrators
The primary account can create or delete teams, add existing subaccounts and grant a subaccount team-administrator permission. A team administrator can publish the team's custom storyboard parsing rules.
Before deleting a team, determine how its projects and assets will be retained. Deleting a team is not the same as leaving a project. Review account, team, project and asset scope separately. Production assignments such as writer, director and reviewer do not imply additional system roles with those names.