Teams
Starting a team, inviting people, what a seat is, and what happens when somebody leaves.
A team is one account with other people attached to it. The person who made it owns it, the plan it is on decides how many people can be attached, and everything the team shares is shared rather than copied.
The three states of /dashboard/team
| What you see | What it means |
|---|---|
| Seats to start a team | The plan includes seats, and none has been used yet |
| A team | A team exists, with its members, its seats and its invitations |
| The plan that brings a team | The current plan includes no seats, so there is nothing to form yet |
That third state is the one that needs explaining to a user, and it should say what it says: teams come with a
plan, and upgrading is what buys the seats. Which plan includes how many seats is the owner's decision in
Money → Plans & pricing.
Running a team
Create it
One click, from the seats state. The account that creates it owns it and cannot be removed from it.
Invite somebody
By address. The invitation is tied to that address, and the person who accepts it gets a seat rather than a copy of anything.
Watch the seats
Seats used against seats available is on the same screen. An invitation that has not been accepted still holds its seat, which is why revoking is a real action rather than tidying up.
Remove somebody, or disband
Removing a person frees their seat. Disbanding the team is available to the owner, and it removes the team rather than the accounts in it: nobody loses their own work.
What the owner sees from the panel
People → Teams & seats is every team on the installation, which plan is paying for it, how many seats it holds
and how many are used. It is read-mostly by design: a team is formed by its owner inside the product, and this is
where you answer "why is this account over its seat count".
Invitations are at People → Invitations, where they can be resent, revoked or extended. An invitation that has
expired while somebody was on holiday is extended rather than recreated, which matters because extending keeps
the same link.
What is shared, and what is not
| Thing | Shared with a team when the plan allows |
|---|---|
| Projects | Yes, when the plan unlocks shared projects |
| Library and folders | Yes, when the plan unlocks a shared library |
| Credits | Yes. The allowance belongs to the plan the team is on |
| Conversations | No. A conversation belongs to the person who had it |
| Memory | No. Memory is personal, by design |
| Account settings | No. Each person has their own |
That last group is deliberate. A shared conversation reads as surveillance, and shared memory would let one person's correction silently change another person's answers.
Entitlements decide what sharing exists
Shared projects and a shared library are two rows in Money → Entitlements. A
plan with seats and without them is a plan whose teams can invite people and
share nothing, which is a perfectly reasonable plan to sell and a confusing
one to sell by accident.
When somebody leaves
Removing a person frees their seat immediately and leaves everything they made where it was, because it belonged
to the team rather than to them. Deleting their account is the other action, it happens in People → Users, and
it is the one with a typed confirmation on it. The two are different on purpose: most departures are a seat, not
a person.