7.2Members, roles, and access

Three organization roles, plus per-project membership on top of them.

Section 2 of 5 in this chapter

Access is two layers. An organization role says what you can administer; project membership says what you can open.

Owners and admins reach every project in the organization. A plain member reaches a project only once they have been added to it.

That second layer is what makes it safe to keep an unannounced title in the same organization as everything else, and it is what lets you bring in a contractor for one project without handing them the studio.

  ORGANIZATION  My Studio
  ├─ Sarah    owner    ──────────── every project
  ├─ Marcus   admin    ──────────── every project
  ├─ Yuki     member   ──┐
  └─ Alex     member   ──┼──┐
                         │  │
     PROJECTS            │  │
     ├─ MyGame      ◄────┘  │
     ├─ SpaceGame   ◄───────┘
     └─ Unannounced      (Sarah and Marcus only)

Figure 7-1. Two layers of access: the role you hold, and the projects you are in.

Seats

A user is anyone with access to at least one project. Your seat count follows your member count automatically — adding someone adds a seat, removing them removes it — so there is no separate licence pool to reconcile and no way to end up paying for seats nobody is using.

Was this helpful?