Teams lets you bridge the gap between assigning, a template or setting reviewer to a whole company or just an individual. This article covers what teams are for, how to set them up, and where they show up across the rest of Visibuild.
How teams work
Teams sit between a whole company and a single person. You decide who’s in each team, then assign work to the team or make them reviewers instead of chasing individual names.
What they're for
A team is a named group of members inside a single company on a project, for example "Structures QA" or "Earthworks QA" under Buildfast Co. Instead of assigning a Visi, a template or a review step to one named person, you can assign it to a team, and any member of that team can act on it.
When to use them
For a function that always needs covering, whatever the roster looks like on a given day, such as QA, site management or structures.
For a role that rotates between people over the life of a project.
For jobs that are more defined than the whole company but less defined than a single individual.
When certain actions need only be completed by certain disciplines of your company, e.g., structure team can only complete the concrete pour inspections.
What's changed
The company directory. The directory used to be one long list of every company on the project and all their members together. It's now a directory of companies, each with its own page showing its teams, active members and pending members. Subcontractors only see their own company's page.
Assigning work to more than one person. Assigning a Visi to a named person meant it could stall if that person was away or had left the project. A team absorbs people joining or leaving without anything needing to be reassigned.
How to create and manage a team
Teams live inside a single company on a project, and a member can belong to more than one team within that company.
For your own company
Go to Project setup > Directory, then open your company's page by selecting View company.
Under Members and teams, select + New team and give the team a name.
Open the team and select Add members to add anyone from your company. Remove someone the same way.
A member can be in more than one team. Add them to each team they're part of.
For other companies (head contractors only)
As head contractor, you can set up teams for any subcontractor on the project. Go to Project setup > Directory, select their company, select View company, then Members and teams > + New team.
Subcontractors can only manage teams within their own company.
Assigning teams to work
Anywhere you can set an Assignee or Reviewer, on a Visi or on a task inside a template, you can now pick a company, a team or an individual member. The picker has a tab for each:
Companies assigns the whole company.
Teams assigns a specific team within a company, for example Structures QA under Buildfast Co.
Members assigns one named person, as before.
When a Visi's assignee or reviewer is a team, any member of that team can pick it up, review it or sign it off. The Activity Feed still records which individual took each action and when.
Where teams show up
Once a team is assigned somewhere, the rest of Visibuild understands it. There's nothing extra to configure, the team name is clear to see under the assingee.
Review workflows
A reviewer can be a team rather than a person. Any member of that team can review and sign off.
Your list
Your list shows work assigned to you directly, plus work assigned to any team you belong to. Use the filter tabs to jump straight to one team's work.
Digest emails
Digest emails include a section for your teams' work alongside your own. It's on by default, and each user can turn it off in their notification settings.
Filters
Visis, templates and other lists can be filtered by team as the assignee or reviewer, the same way you'd filter by an individual.
Exports, API and MCP
Wherever assignee or reviewer data appears outside the main product, including exports, the API and the MCP integration, a team is shown the same way an individual would be.
Visi notifications
Notifications for work assigned to a team are sent to every member of that team, so review requests and newly assigned work aren't missed.
Coming soon
You can already set a team as the default assignee or reviewer on individual tasks inside a template. Using teams for a template's own review-and-publish approval step is coming in a later release.