Sign-in and access

Who can sign in to the panel, how sign-in with GitHub works, and how long a session lasts.

Get started / Quick start

The panel is private. Only active members of the BlockoutGames GitHub organization can sign in, and they sign in with GitHub. There is no other way in: the old Roblox login is retired.

Who can sign in

  • An active member of the BlockoutGames organization. GitHub must say the membership is active.

  • Not someone with a pending invitation, an outside collaborator, or a member of another organization.

Membership is managed on GitHub, not in the panel. To give someone access, invite them to the organization; to remove it, remove them there.

Getting in with GitHub, step by step

  1. Accept the organization's invitation

    On GitHub, accept the invitation to BlockoutGames. Until you do, sign-in is refused.

  2. Open the studio

    Open studio.blockoutgames.com. Without a session, it sends you through the account site, account.blockoutgames.com, straight to GitHub.

  3. Authorize the app on GitHub

    Once only, GitHub asks you to authorize the studio's app. It asks only to read your organization memberships (read:org).

  4. Land back where you started

    GitHub returns you to the address you opened, signed in.

Signing in with GitHub. You open the panel without a session and the studio sends you to GitHub. You authorize the app, and GitHub sends you back with a one-time code. The studio asks GitHub whether you are an active member of the BlockoutGames organization. If not, you are sent to the public website and no session is made. If you are, the studio makes a new session and returns you where you were.

One account for every site

You sign in once, at account.blockoutgames.com, and you are signed in on the studio, the docs, the website and the status page: each shows you in its account menu at the end of its top bar. Sign out in any of them signs you out of all of them on that browser, and so does Sign out everywhere in Settings, on every browser. If you were signed in before 27 October 2026, sign in once more: the old sign-in no longer counts.

Sign in in any site's top bar goes straight to GitHub and back to the page you were on, with nothing to choose in between. If sign-in does not complete, the account site says why, at account.blockoutgames.com/sign-in/error, with Try again, which goes straight back to GitHub.

Your name, login and avatar are taken from GitHub at every sign-in. GitHub's organization owners sign in as panel owners; everyone else as members. See Roles.

What happens to people outside the organization

Someone who is not a member is sent to the public website with a notice that studio access is for members of the Blockout Games GitHub organization. No session is created.

Other errors on the way in

Other failures land on the panel's sign-in screen with a reason and a button to retry. It never starts another sign-in by itself.

GitHub unavailable

GitHub could not be reached to confirm your membership. Nothing is wrong with your account; retry in a moment.

Not trusted

The sign-in did not come back the way it left, so it was not trusted. Start over.

Interrupted

It took longer than ten minutes, or another sign-in started in this browser meanwhile. Start over.

Cancelled

You cancelled on GitHub, so nothing changed.

Too many attempts

More than 20 sign-in attempts from your network in a minute. Wait a minute.

How long a session lasts

How long until you sign in again depends on your session, which lasts at most 90 days:

  • A session lasts 30 days from its last extension, is extended at most once an hour, and never lasts more than 90 days from sign-in.

  • Every sign-in starts a new session and ends the one the browser held before.

  • You can end one session, all others, or sign out everywhere from Settings, Sessions & security.

  • An owner can end a member's sessions from Members & access.

How a session is kept safe

The session is a random token in a cookie that scripts cannot read, signed by the studio and sent only to the panel's own address. The database keeps only a hash of it, so a copy of the database opens nothing. Signing out deletes the session and clears the cookie.

When access changes

The studio checks each signed-in person's membership with GitHub in the background about every 5 minutes; no page waits on it.

  • Removed from the organization, or revoked the app on GitHub: every session ends at once.

  • Promoted or demoted: every session ends, so the next sign-in carries the new role.

  • GitHub unreachable: the last confirmation stands for 30 minutes. After that the panel asks you to sign in again until GitHub answers.

Keeping membership current. About every 5 minutes the studio asks GitHub about each signed-in person. Still a member: nothing changes. Removed or the app revoked: every session ends. Role changed: every session ends and the next sign-in carries the new role. GitHub unreachable: the last confirmation stands for 30 minutes, then the panel asks you to sign in again.

A removal reaches every session within about 6 minutes: the 5-minute interval and a minute for the background sweep.

Two-factor authentication

The studio does not require GitHub two-factor authentication today. Turning on the organization's requirement is a founder's decision.

Updated