Whether you’re localizing a web app or landing page, lots of people are involved. So today we’re introducing Teams, a new, centralized way to organize and manage your translators, reviewers, and coordinators across all your translation projects. You no longer have to manage the translators of each project separately or use Hub projects. Instead, translators belong to teams which are assigned to one or more projects.
Here’s how projects and teams are organized now compared to before:
To access your teams, click the new Teams tab in your dashboard. There, you can create a team, add the languages you want, and assign the desired projects to it.
If you want a project to be translated by a different team, click the “Move” button. And by clicking on a language of a team, you can add/invite/remove translators just like before.
Note that when you create a new project, you have the option of either assigning the project to an existing team, or creating a new team for it.
Like most people, you probably find yourself communicating with your translators, reviewers, and coordinators constantly. Teams gives you finer control over discussions.
When you start a new discussion, you can select whether the discussion is for all members of a team, or just the collaborators of a language within the team, such as Greek.
To access discussions, click the chat bubble icon.
Sometimes, you need different types of teams for different types of projects. To support this, each team has its own settings.
Clicking the gear icon lets you choose whether to automatically accept requests to join the team, enable a Contributor’s License Agreement (CLA), as well as delete the team.
All projects have been migrated to the new team structure. Normal projects should have received minimal UI changes. You should see a new Teams tab in the organization dashboard, under which admins are now managing people and languages. Translators will be able to see the teams but not edit them.
If you were a member of a hub, here are some changes which you might notice:
There is only one type of projects now. Hubs and Child Projects are no more and projects do not technically have their own teams any more. Instead, teams are now centrally managed under the Organization and projects are simply assigned to them.
To reflect this change, we’re removing the “outsource” field from the Project Creation API call. In its place, we’re introducing a new field called “team” to allow assign a project to a team. This field accepts a team ID, which you can find by navigating to the team (Organization Dashboard → Teams → Select Team) and copying from the end of the URL:
If you’re already using our API to create projects and hubs, you only need to make the following change:
- “outsource”: <project_hub_slug>,
+ “team”: <team_id>,
If you don’t assign a new project to a team, Transifex will automatically create a new team for it.