Teams and Members
Team roles and their exact permissions, inviting people, changing roles, transferring ownership, and removing access.
A team is a workspace with its own data source, regions, alerts, optimization runs, and reports. Team membership is what actually grants access to caseload data.
Manage a team's roster at /home/<team>/members.
The two team roles
| Owner | Member | |
|---|---|---|
| View monitoring, map, runs, reports | Yes | Yes |
| Use Willow | Yes | Yes |
| Send and revoke invitations | Yes | Yes |
| Change team settings | Yes | Yes |
| Change the data source and vendor credentials | Yes | Yes |
| Change another member's role | Yes | No |
| Manage billing | Yes | No |
| Transfer ownership | Yes | No |
Configuring the team's data source is gated on the same permission that covers team settings, and members hold that permission. An ordinary member can therefore open /home/<team>/integrations, reconnect the team to a different source, and enter or replace vendor credentials.
If that is not what you want, keep team membership limited to people who should be able to do it, and give everyone else visibility through an organization viewer role instead. There is no per-team setting that separates the two today.
Viewing the monitoring dashboard and reports requires only that you are a member of the team in some capacity.
Inviting people
From /home/<team>/members, invite by email address and choose the role.
- Invitations expire after 7 days.
- One pending invitation per email address per team.
- You cannot invite someone to a role above your own.
- Pending invitations are listed alongside the roster and can be revoked.
The invitee receives an email; the link takes them to /join where they accept. If they do not have an account, they create one at that point.
Changing a role
Only a team owner can change roles, and only to a role at or below their own. The primary owner's role cannot be changed by anyone else — to move it, use ownership transfer.
Transferring ownership
Team Settings (/home/<team>/settings) has a transfer ownership action. It is confirmation-gated because it is not reversible from the new owner's side — after the transfer, you are a member and they are the owner.
Do this before an owner leaves the company, not after.
Removing people
Removing a member from /home/<team>/members revokes their access to that team's data immediately. It does not remove them from your organization — for that, use Manage Tenant → Members.
A member can also leave a team themselves.
To fully offboard someone:
- Remove their access in Microsoft Entra if you use single sign-on. This stops them signing in at all.
- Remove them from each team.
- Remove them from the organization in Manage Tenant.
Deleting a team
Team deletion is available from team Settings when it is enabled for your deployment. It removes the team's data source configuration, regions, alerts, runs, and reports. It is not reversible.
A note on the two levels
Organization roles and team roles are separate systems. Granting someone organization admin does not let them open any team; adding them to a team does not give them Manage Tenant. Most people need both. See Administration.