Is a Team a nested company under the Organization?

No. The Organization is the company account. A Team is a flat named list of people in it: Estimating, Shop, that GC’s PMs. Not a second login and not a nested company. We don’t call them Groups; that word is markup.

Do I create a Team per Project?

You can, but the point is reuse. Estimating, Shop floor, Hospital PMs: grant the same Team on every Project that needs that cast. Don’t clone a private list on each Project.

Can a guest sit on a Team?

No. Teams are org members only. Invite the guest to the Organization first if they should be on Estimating. A one-bid outsider stays a Project guest.

Can a Team from another Organization be granted?

No. Same-org Teams only. A foreign Team is a miss, not a leak.

If I add someone to a Team, when do they get the Project?

When they next open the Project. Add them to Estimating and they can open every Project that Team is granted on. Remove them from the Team and they lose that path (they may still have an individual grant or inherit).

Who can create a Team?

Org members, unless you later lock creation to admins. Org admins manage the roster. If you created the Team, you can add people too. Full control on a Project uses the Team as a share target; they don’t own a private Team cabinet.

Teams you grant on a Project

A Team is a named list of people already in the Organization. Grant it on a Project once. Guests cannot sit on a Team. Estimating, Shop, that GC’s PMs.

A Team is a named list of people in the Organization.

Not a nested company. Not a second login. Not markup “groups.” Estimating. Shop. That GC’s PMs. You build the list once, then grant it on a Project instead of typing forty emails every bid.

People on a Team already belong to the Organization. Guests cannot sit on a Team.

Where this lives

Organizations → Teams is the directory: create the list, add org members, rename, delete. (You can still invite someone by email to the org or a Project before they have an account. The Team roster is people already in the company.)

Projects → Teams (and Share) is where you grant that list on a Project with a role. You don’t rebuild Estimating on every hospital bid.

Teams are flat. No Team-inside-a-Team.

Create a Team, then grant it

Organizations → Teams → New team. Name it (Estimating, Shop).
Open the Team. Add org members from the directory.
Open the Project → Members, Teams, or Share. Add the Team with a role: View, Comment, Edit, or Full control (Full control only if you already have Full control).

That role is the same four roles as a person grant. Access is the highest of inherit, every Team the user is on for this Project, and their individual grant. We do not take the most-restrictive-of-several-Teams rule. If Estimating is Edit and a review Team is View, they get Edit. Details: who can open a Project.

Remove the Team grant and that path goes away. Delete the Team and its Project grants go with it. Remove a person from the Team and they lose that path. They may still inherit, or still have an individual grant. Removing them from the Organization drops them off every Team in that org: organization members.

Shop vs GC

Shop	GC / large office
You may never create a Team. All members already inherit Edit.	Teams are how departments share without making everyone an org-wide editor.
One “Estimating” Team is still useful the day a guest list appears.	Restricted Project access + Teams + guests. Org admin is not on every bid. Guests stay off Teams.

A commercial precon team uses Teams so a named crew opens this bid without a grant for every email. A one-person desk can skip this page until the second hire. You don’t migrate to a different product.

What we won’t call it

Groups is a markup noun (grouped markups). Team is people. We don’t nest companies under companies. If you needed that, you wanted a second Organization.

Evaluating this

If your bake-off question is “can I share a takeoff with a named crew without a suite of access products,” this is the answer: two org roles, four Project roles, Teams as a list you grant. Seat SKUs and SSO are later. The measuring loop is still how it works. That’s takeoff, not a priced bid: takeoff vs estimating. Measuring the set, with stairs as the worked package: quantities. A measure desk, not another estimating platform: takeoff without a platform. Same Project on every device: cloud sync. No install to start: Browser desk. Two people on the sheet: Working together.

Next: organization members, Project collaborators, Project roles, delete and restore.

Straight answers

Is a Team a nested company under the Organization?: No. The Organization is the company account. A Team is a flat named list of people in it: Estimating, Shop, that GC’s PMs. Not a second login and not a nested company. We don’t call them Groups; that word is markup.
Do I create a Team per Project?: You can, but the point is reuse. Estimating, Shop floor, Hospital PMs: grant the same Team on every Project that needs that cast. Don’t clone a private list on each Project.
Can a guest sit on a Team?: No. Teams are org members only. Invite the guest to the Organization first if they should be on Estimating. A one-bid outsider stays a Project guest.
Can a Team from another Organization be granted?: No. Same-org Teams only. A foreign Team is a miss, not a leak.
If I add someone to a Team, when do they get the Project?: When they next open the Project. Add them to Estimating and they can open every Project that Team is granted on. Remove them from the Team and they lose that path (they may still have an individual grant or inherit).
Who can create a Team?: Org members, unless you later lock creation to admins. Org admins manage the roster. If you created the Team, you can add people too. Full control on a Project uses the Team as a share target; they don’t own a private Team cabinet.