Roles

The two panel roles, owner and member, how each comes from the GitHub organization, and what each may do.

Studio / The studio's rules

The panel has two roles, owner and member, and both come from your role in the BlockoutGames GitHub organization. Nobody edits a role in the panel. On top of the role, being a developer or the lead of a game lets you do more on that game.

GitHub organization rolePanel roleShown as
Owner (GitHub calls it admin)ownerAdmin
MembermemberMember

How a role reaches the panel

Where a role comes from. An owner of the GitHub organization signs in as a panel owner, shown as Admin; a member signs in as a panel member. When a role changes on GitHub, the studio notices within about 5 minutes and ends every session of that person, so their next sign-in carries the new role.

Who can do what

ActionAny memberOn the gameOwner
Read every page outside AdminYesYesYes
Register a projectYesYesYes
Edit and submit a contractNoDeveloperYes
Sign a contractNoDeveloperNo
Buy a shareYesNot a developerYes
Edit a game's details and updates logNoLeadYes
Create or rotate a game's API keyNoDeveloper, leadYes
Set a game's state, remove a gameNoNoYes
Open Admin, register groups and keysNoNoYes

"On the game" means a developer or the lead of that game. An owner who is not a developer on a game buys shares of it like any member, and does not sign its contract.

What every member can do

  • Read every page outside Admin: studio games and their numbers (revenue included), the market, code activity.

  • Register a project and name its developers.

  • Edit, submit and sign the contract of a project they develop. See Contracts.

  • Buy shares of games they did not work on.

  • Keep their own home pages, watchlist, notification settings and sessions.

What only an owner can do

An owner can do everything a member can. These a member cannot do:

  • Open the Admin pages: groups and their keys, members and sessions, the audit log, integrations, data health, system.

  • Register Roblox groups and their keys. See Roblox groups and keys.

  • Set a game's release state and remove a game from the studio.

  • Edit any game's details and updates log.

  • Edit and submit any project's contract. An owner who is not on the project does not sign it.

  • See the collector's run history and each ban's private reason.

  • End another member's sessions.

A member who calls an owners-only route of the API gets 403, and the panel hides what they cannot use.

The game's lead

A game can have a lead, set in its Manage game sheet. The lead may change that game's details (including handing the lead on) and its updates log. See Members, developers and leads.

When a role changes

A change on GitHub ends every session of that person, so the next sign-in carries the new role. The studio checks each signed-in person with GitHub about every 5 minutes. See Sign-in and access.

Updated