Team & Organization Management
Taia is designed for collaboration. Whether you're a localization manager, project owner, or internal reviewer, you can work together efficiently with shared access, permissions, and billing.
This guide explains how teams and organizations work inside Taia.
π’ What Are Organizations and Teams?β
- An organization represents your company or department.
- A team is a working group inside that organization β usually tied to a product, region, or function.
- Users belong to one or more teams and have access to all projects within those teams.
This structure lets you:
- Keep projects organized
- Share glossaries and translation memories
- Manage user roles and access
- Assign tasks and projects cleanly
π₯ Inviting Usersβ
To add a user to a team:
- Go to your Team Settings
- Click βInvite Memberβ
- Enter their email and assign a role
- The user will receive a link to join (with email pre-filled)
You can invite both new users and existing Taia users.
π Role-Based Accessβ
Each user has roles that control what they can see and do.
Organization-Level Rolesβ
Role | Permissions |
---|---|
Organization Manager | Add/remove teams, invite users, manage billing |
Team-Level Rolesβ
Role | Permissions |
---|---|
Team Manager | Add members, assign tasks, manage team projects |
Editor | Edit translations, complete tasks |
Viewer | View projects and comments, but cannot edit content |
You can mix and match β e.g., someone can be a Team Manager in one team and a Viewer in another.
π§Ύ Shared Resourcesβ
- Glossaries: Teams can share termbases across projects
- Translation Memory: Reuse past translations across all team jobs
- Style Guides: Ensure consistent tone across users and languages
π³ Team Billingβ
Each team can be linked to a billing account:
- Subscriptions are shared across the team
- Word usage is pooled
- Invoices are consolidated for easier accounting
Admins can reassign billing relationships at any time.
π Task Managementβ
In team projects, you can:
- Assign translation, editing, or review tasks to members
- Track progress of each task
- Notify users when tasks are ready
- Create workflows (e.g. MTPE β Revision β Proofreading)
See: Professional Services and CAT Editor
β¨ Tipsβ
- Use teams to group projects by product, region, or language
- Donβt invite vendors to your entire org β assign them to a specific team or project
- Team managers canβt manage billing β thatβs an org-level permission
Need help structuring your teams and roles?
Contact support β weβll help you get set up.