Skip to content

Teams & assignments

Two tools split the work of a growing organization: teams grant a group of people the same project access in one move, and assignments hand a specific slice of a project (a book, some chapters, a lane) to a specific person.

Open Teams in the organization sidebar. The page’s own summary is the whole idea: “Group members and grant project access together.” New team asks for a name and an optional description; each team then has three sections:

  • Members: org members on the team. “People on this team inherit its project grants at their org role.”
  • Projects: projects attached to the team, each with the role the attachment grants. Attach project picks a project and a role from the standard role ladder.
  • Overview: the team at a glance (as of today it unlocks once the team has activity).
A team page for Spanish reviewers with Projects, Members, and Overview tabs; the Projects tab lists Mark — Spanish Draft granted at the Reviewer role, with an Attach project button
One attachment, whole team: everyone on Spanish reviewers can now review the Mark project.

The mechanics to keep in mind:

  • A team grant is one of the paths access can arrive by, next to direct invites and org-wide roles. When someone holds more than one grant, the highest wins, exactly as on Roles & permissions.
  • Attaching a project at Reviewer does not demote a member who already has Contributor directly; it only raises people below that level.
  • Creating and managing teams needs Maintainer access or above in the organization. Team settings (the gear on a team’s page) renames the team, edits its description, and holds the Danger zone for deleting it.

Assignments answer “who is translating what, by when”. They live in two places: each project’s Team card on its overview page, and the organization-wide Assigned to me page in the sidebar, where every member sees their own queue as a table of assignment, file, project, progress, and due date.

To hand out work, open a project’s overview and use Assign… on the Team card. The form asks for:

  • an Assignee (any project member),
  • a Book (one of the project’s files),
  • Chapters, when the file has them: check specific chapters, or leave “Whole book (none checked)”,
  • an optional Deadline.
The Assign work form on a project's Team card: sofia-alvarez selected as assignee, mark.usfm as the book, the MRK 1 chapter checked, an optional deadline field, and Assign and Cancel buttons
A whole book or just the chapters you check: the assignment lands in the assignee's own queue.

Once assigned, the Team card tracks each person’s open work and progress, with an Activity link per assignee, and the work appears in the assignee’s Assigned to me page. Assignments are direction, not enforcement: they don’t restrict what anyone can edit, they record what each person should be doing.

By default only leads and maintainers assign work. An organization can also let members claim work for themselves: the Allow self-assignment switch in organization settings lets a Contributor or above “claim a book/chapter/take for themselves from the assign-work picker — they still can’t assign work to anyone else.”

For staffing a person onto a target-language lane rather than a file, see Inviting people.