Teams

An organisation is the account: billing, domains, policy, and the people. A team is a group inside it with its own members and its own content.

Bought a Teams licence? Start with Setting up an organisation. The licence, the people and the teams all attach to one.

blueprint:josh/teams-structure

	Organisation	Team
Owns content	Yes	Yes
Has members and roles	Yes	Yes
Billing and licensing	Yes	No, inherits
Custom domain and Atrium	Yes	No
Policies and audit	Yes	Inherits, plus its own settings

When to add a team

Add one when a group needs its own content boundary: a different set of people editing a different set of blueprints. Do not add one per project; that is what portfolios are for, and they cost nothing to create.

Built-in roles

Every membership has one of three built-in roles, and they are strictly ordered: owner > admin > member.

Role	Broadly
Owner	Everything, including billing and deleting the organisation
Admin	Everything operational, short of ownership
Member	Read and contribute according to what they are granted

Owners and admins hold every permission implicitly. Members hold what their custom roles grant.

Setting up an organisation

Create it, license it, invite people, add a team.

Members and invitations

Getting people in, and out.

Roles and permissions

The full permission catalogue.

Policies

Rules that constrain what members may publish.