Teams
Share grounds, trees and bugs with your teammates.
Create a team
Create a team from Create a team under Settings → Organization. Enter a team slug (only lowercase letters, digits, hyphens - and underscores _, 3–32 characters) and a team name. Anyone can create a team, and whoever creates it becomes its owner by default.
A team slug is a unique address name, just like a personal account’s handle. So a name already used by another person or team can’t be taken. The owner can change the team’s name and slug later in the team settings.
Roles
There are four roles: Viewer, Reporter, Editor and Owner. Each member has one role and works with it on every ground opened to them. Each role can do the following.
| Viewer | Reporter | Editor | Owner | |
|---|---|---|---|---|
| Read the tree, bugs, history and wiki of the grounds opened to them | ✓ | ✓ | ✓ | ✓ |
| File and update bugs (including status) | ✓ | ✓ | ✓ | |
| Delete bugs, change nodes, connections, seasons and wiki | ✓ | ✓ | ||
| See every ground in the team | ✓ | |||
| Create grounds in the team, edit a ground’s settings, archive, delete, root, move, choose who can see it | ✓ | |||
| Invite members, change roles, remove members, edit the team | ✓ |
A reporter fits someone who files bugs without changing the tree, like a QA tester or a client.
Which grounds members see
Members other than the owner see only the grounds the owner opens to them. Grounds that aren’t opened to them don’t appear in their list at all. So even with several clients in one team, each client sees only their own project’s grounds.
- When creating a ground, pick who can see it under Members.
- For an existing ground, change it under Members in Edit Ground.
- When inviting a member, you can pick the grounds to open to them at the same time.
Members other than the owner see only the owner and the people who share a ground with them in the member list.
Invite members
When the owner invites someone, an email is sent. The owner picks a role (Viewer, Reporter or Editor) and the grounds to open to them when inviting. If no ground is picked, they’ll see no grounds after joining — open some to them later from each ground’s settings.
- If the invitee already has an account, they sign in with the invited address and open the link.
- If they don’t have an account, they sign up with that email address. They join the team automatically the moment they verify their email.
An invitation can only be accepted by the account at the address it was sent to. Opening the link while signed in with a different account won’t accept it. Invitations expire after 7 days, and sending one again to the same address makes the old link invalid.
Editor limit
There’s no limit on inviting viewers and reporters. People who can edit (the owner and editors), however, are limited to 3 during the beta. More seats will become available as the service develops.
Grounds in a team
If you own a team, New Ground shows an Organization field. Choose whether the ground goes into your personal space or the team. To move an existing ground, change its Organization in Edit Ground.
After moving a ground to a team, pick who can see it under Members — those members can then view or edit it according to their role. Moving a ground to another team clears the access given in the old team, so pick members again in the new one. Its slug, URL, the nodes of its tree and its history all stay the same after the move.
Transfer ownership
The owner can hand the team to another member from Transfer ownership in the team settings. You stay on as an editor who can still see every ground in the team, and the new owner takes over the team settings, members and grounds. To undo it, the new owner has to transfer it back.
Delete a team
The owner can delete the team from Delete team in the team settings by typing the team slug once more. A team that still has grounds can’t be deleted — move or delete its grounds first. Members and pending invitations are removed with it.
A deleted team’s slug, and a team’s slug from before it was changed, can’t be used by anyone else for 30 days.
Leaving and removing
Editors, reporters and viewers can leave a team at any time with Leave team, and the owner can change members’ roles or remove them. The owner can’t leave their own team.
The owner of a team that has other members can’t delete their account. Transfer ownership or remove the members first.
Team roles and API tokens
The type of your personal API token and your own role on a team ground are applied conservatively. If your role is Viewer, even a Write token can’t edit the team’s grounds; a Reporter can only file and update bugs even with a Write token; and an Editor with a Read token can still only read. See Generate an API token.