Teams

A team is a group of people inside your organization. It can be an office, a discipline, a client, or a region. Work can be shared with a team.

Each team has its own page. The page holds what the team uses: projects, checklists, codes, and files.

A team is who you share with. Its page is where the shared things end up. See How access works.

The tree

Your organization is laid out as a tree.

• The organization is at the top.
• A team sits right under the organization.
• Anything under a team is a sub-team. Sub-teams can go as deep as you need.

Each box in the tree has a type. The types are:

• Team
• Client
• Discipline
• Project
• Sub-org
• Region
• Shared item
• Other… (you type your own name)

A discipline is just one of these types. For example, a Structural group under an office is a box of type Discipline: Office > Structural.

Only an org owner (or an admin) can add a box at the top of the tree. A team lead can add boxes under a team they lead.

Getting there

Your teams are in the left rail, under TEAMS:

• Organization is the page for the whole firm.
• Each team you can open is listed under it. Sub-teams open out under their team.
• Browse teams lists every team in your organization, even ones you are not in.

The top of a team page

The top of the page tells you where you stand, in one line. For example:

• "Member. You can use everything here and ask to share into it."
• "Lead. You approve what is shared into this team and the teams inside it."

If you lead the team, View as a member shows the page the way your members see it. Back to your view takes you back.

Include inherited adds what is shared with the teams above this one. Those rows show which team they come from.

What's on a team page

Each tab holds one kind of thing:

Tab	What's in it
Projects	Projects placed in this team, or in a team under it
Checklists	The team's shared checklists
Workflows	Workflows the team uses
Revit workflows	Saved routines for the Revit add-in
Resources	Files for the team, like a CAD standard or a title-block template
Codes	The code books tagged to this team
Members	Who is in the team, and who leads it
Teams	The sub-teams inside this one

Workflows only shows if your organization has Workflows turned on. Checks don't get a tab of their own: each one lives inside its checklist.

Everything on these tabs is there because someone shared it with the team and it was approved. A team page is a shelf someone looks after. It is not a pile of everything anyone made.

Lists are narrowed to items that share one of your labels or carry none. If something is hidden, the bar above the list says how many. Show all brings them back.

Where checklists and codes live

• Checklists are on the Checklists tab of each page: My resources for your own, a team page for a team's, and the Organization page for the whole firm's. Click one to open it.
• Codes live in the code library. Open Codes and Standards in the left rail. A team's Codes tab shows only the code books tagged to that team.

Resources

Resources is a place for the team's own files. Anyone can Download a file.

Anyone in the team can upload:

• A lead's upload goes straight onto the page.
• A member's upload is a request. It shows Awaiting review until a lead says yes.

For team leads

If you lead the team, the page is also where you do your review work.

• What's waiting. A note at the top says how many requests are waiting, and which tab they are on. Requests from teams under this one are listed too. Everything is also in Requests.
• Reviewing. A waiting row shows Pending review, with Approve and Review. Review opens a panel with Approve, Decline…, and a conversation. A decline needs a reason. If an item changes after you approve it, its row says Changed since your review.
• Members. On the Members tab you can add people from your organization and remove members. You can't remove another lead. An org owner can make anyone a lead, or remove them.
• Your own shares into a team you lead go live at once.

A person can be added to the whole team, or only to Specific clients under it. Someone added for specific clients sees only those clients.

Sub-teams

A sub-team works like a team. It has its own page, members, and requests. Its name shows the path to it, like Office / Structural.

Sharing flows down the tree. Something shared with a team can be seen by that team and every team under it. Leads of a team can approve for the teams under it.

An org owner builds the tree on the Organization page's Teams tab. A team lead can add a sub-team from their team's Teams tab, with Add a team. Open in tree shows where the team sits in the tree.

Asking to join a team

If you should be in a team you are not in, open Browse teams and press Request to join. It shows Requested until someone decides. A team lead or an org owner reviews it, and you are told either way.

If someone adds you to the team directly, your request is closed for you.

Where else teams show up

Once your organization uses teams, they also help sort other parts of the platform:

• The code library. A published code book can be tagged to teams, so it shows on those teams' shelves. Tags only sort. They don't stop anyone reading a published book.
• Workflows. Shared workflows are grouped by team.
• The Organization page. Its Overview can be narrowed to one team. See Organization page.
• Projects. A project is placed in a team. That puts it on the team's Projects tab and in its numbers.

Teams give access, labels don't

Two things look like filters. Only one is about access.

Teams control access. Something shared with a team can be seen by its members, the teams under it, and org owners. Nobody else. Other people don't see a locked copy. It just isn't in their lists.

Labels are only a filter. You pick your own labels. Lists show matching items first, and Show all always shows everything. A label never hides something for good, and never gives anyone access. See Labels.

Anything a page or list shows you, you are allowed to see.

A deleted team

If a team is deleted, its page still opens and says "This team has been deleted." You can't share anything new into it. What was already there still works for the people who were members. See How access works.

Setting up teams

Teams appear once your org owner makes the first one, on the Organization page's Teams tab. Until then, team controls stay hidden.

On the legacy layout, teams are on the home page's Teams tab and the rail's Teams list. See The legacy layout.