Skip to content

Your studio

Studios, teams and access

Who sees what and who changes what: roles, games and teams — a member writes the issues of their own teams and reads everyone else’s — and what a new account asks for.

Roles

  • The owner and admins see every game and change everything: issues of every team, objectives, settings, members, Discord.
  • Members see the games they were given, and change what their teams own — below.
  • Objectives — milestones, OKRs and SMART goals — are written by the owner and admins. Members read them, check-ins included.

Games

A member sees only the games they were given, in Settings → Members or on the invitation. A game they cannot see does not appear anywhere: not in the sidebar, not in search, not by link.

Teams

A team decides who writes its issues. A member on a team creates, edits, moves, archives and comments on that team's issues, writes their descriptions, and draws on the boards the team and its issues hold.

  • Every other team is open to read. A member opens another team's issue by its link — from a project, a relation, the inbox — and reads all of it: the description, the board, the comments. The issue says, at the top, that it is read-only and why. Writing to it is refused, by the screen and by the server alike.
  • The sidebar shows your teams. A member on no team of a game sees none of its teams there — and writes no issue in that game.
  • The owner and admins are on every team, listed on each roster, and write every team's issues.
  • Who is on a team is set in the game's Settings → Teams, per person in Settings → Members, or on the invitation. Leaving a team takes its issues off your list of things you write.
  • A new document filed under a team starts as Only that team — its roster reads it, the owner and admins included, since they are on every team — and the readers can be widened in Permissions.
  • What a team does not decide: attaching issues to a project and its milestones (the project's), saved views, the game's own boards and documents' boards, and who sees and decides each Community category — set in Settings → Community. Approving a Community report as a team's issue, or linking it to an issue, writes that issue, so it needs that team's roster as well.

Your account

  • Creating an account asks you to agree to the Terms of Service and the Privacy Policy — a box nobody ticks for you. The account keeps when you agreed, and to which versions.
  • Verify your email first. A new account opens on a page asking you to open the link we emailed; nothing in a studio answers until then. Send the link again sends another one, and Sign out is there for a wrong address.
  • Joining by invitation counts as verifying: the invitation only went to that address.