Admin pages

The owners-only Admin section - its seven screens, who can open them, and the Members & access and System screens in full.

Panel

The Admin section is for organization owners only (see Roles). The API refuses every admin request from anyone else too. None of these pages sends a request to Roblox; they read what the platform already stored.

Who can open the Admin pages

Only owners of the BlockoutGames GitHub organization see Admin in the rail. A member who opens an /admin address anyway sees "Administration is for organization owners" and a Back to Home button. Someone signed out is sent to sign in first. The one exception is the Collector page: it sits in the Admin rail, but members can open it at /collector and see everything except the run history and the raw errors.

The Admin screens

The rail, in order:

  • Groups

    The studio's Roblox groups and their one key each: add, check, replace, remove.

  • Members & access

    Everyone who has signed in, their GitHub standing and sessions; end a member's sessions.

  • Audit log and Data health

    Who did what and when; whether the stored data can be trusted.

  • Integrations

    Each studio game's daily analytics read, and the GitHub organization connection.

  • Collector

    The process that reads Roblox: status, tiers, jobs, requests, run history.

  • System

    Each service, the worker's job queues and the API's read cache.

Every Admin screen has the same shape: a header, a row of headline tiles (two to a row on a phone), then cards. Tables keep their most important columns on a phone, hide the rest, and scroll sideways when they still do not fit.

Groups (/admin/groups)

The studio's Roblox groups, each with its one Open Cloud key shown by fingerprint. Owners add a group with its key, check a key, replace it, or remove the group. Full page: Admin Groups.

Members & access

The Members & access screen lists everyone who has ever signed in to the panel: their role, their GitHub membership, when they last signed in and how many live sessions they hold. Roles are not edited here: they come from the GitHub organization (see Roles).

Tiles on Members & access

Signed in nowpeople

The accent tile: people with at least one live session, "of" everyone listed.

Live sessionssessions

Every live session across every device, added up.

Ownerspeople

People who own the GitHub organization.

Need a lookpeople

People whose GitHub membership has ended or is not confirmed.

The people table on Members & access

Owners first, then by name. Columns:

Member

Avatar, name and @login. A member without a GitHub login shows "Retired Roblox sign-in". The name opens the member's page.

Role

Owner or Member.

GitHub membership

Confirmed, Not confirmed, Membership ended or No GitHub account, with when GitHub was last asked ("Asked 20 minutes ago", or "Not asked yet"). Hidden on a phone (shown from 768 pixels wide).

Last sign-in

How long ago. Hidden below 640 pixels.

Sessionssessions

Live sessions now.

How often GitHub membership is checked on Members & access

GitHub membership is rechecked every minute for people whose last confirmation is more than 5 minutes old. The API asks with each person's own GitHub sign-in while they have a live session. No page waits for the answer. What GitHub says decides what happens:

Still a member, same role

The confirmation moves forward.

Removed from the organization, or the app's access revoked

Every session of theirs ends at once, and the audit log records "GitHub membership ended".

Promoted or demoted on GitHub

Every session ends, so the next sign-in starts with the new role; the audit log records "Role changed on GitHub".

No answer

Nothing changes for 30 minutes after the last confirmation. After that the member shows Not confirmed, counts under Need a look, and the API refuses their requests (without signing them out) until GitHub answers again.

How GitHub membership is kept current. Every minute the API finds people with a live session whose membership was last confirmed more than five minutes ago and asks GitHub about each. A confirmed member's confirmation moves forward. A member removed from the organization, or whose role changed, has every session ended and an audit entry written. When GitHub does not answer, nothing changes for thirty minutes; after that the member is refused until GitHub answers.

The 5 and 30 minutes are the platform's defaults (AUTH_MEMBERSHIP_INTERVAL_MINUTES and AUTH_MEMBERSHIP_GRACE_MINUTES). More on sign-in: Sign-in and access.

A person's page on Members & access

/admin/members/<id>, opened from the table. The header shows the avatar, name, login, role and membership, with Every member to go back. Tiles:

Live sessionssessions

The accent tile.

Last sign-in

How long ago, with the date and time under it.

GitHub confirmed

When GitHub last confirmed the membership ("No" if never), and when it was last asked.

Role

Owner or Member, "Set by the GitHub organization".

Then two cards: Sessions and Recent activity, the last 8 audit log entries about this member (event and when), with Audit log to open the full log filtered to them.

How to end someone's sessions on Members & access

The Sessions card lists every device signed in as the member, newest first: Device (the browser and system, worked out from the browser's own description) with its address under it, Started (hidden below 640 pixels), Last used, and End. Your own session is marked Yours.

  1. Open the member

    On Admin, Members & access, choose the member's name.

  2. End one device

    Choose End on the device's row. That device is signed out at once.

  3. Or end every device

    Choose End all of (name)'s sessions under the table.

Each ending is written to the audit log as "Session ended" or "Sessions ended", naming the member. Ending a session does not stop the member signing in again: while they are in the GitHub organization, they can. Ending your own session signs you out and takes you to the public website.

Audit log (/admin/audit)

One timeline of sign-ins, sessions, group keys, games, game API keys, projects, contracts and shares, newest first, 50 a page, filtered by person, kind and days. Full page: Audit log and Data health.

Integrations (/admin/integrations)

The Integrations page shows whether the studio's outside connections work: for each studio game, which group key covers it and whether its daily owned-analytics read from Roblox worked; and the GitHub organization connection with its last collection run (requests, unchanged answers, seconds). Owners verify the GitHub token or save a GitHub App there. Full page: Admin Integrations.

Collector (/collector)

The collector's status, last snapshot, overdue games, tracked games by tier, jobs in the last hour, requests to Roblox per endpoint, and for owners the run history with its errors. Full page: Collector page.

Data health (/admin/data)

The database's invariant checks (run once a day) worst first, how fresh each source is against its schedule, and the last dead-game cleanup report. Full page: Audit log and Data health.

System (/admin/system)

The System screen says whether each part of the platform answers right now, as this API sees it: the services, the worker's job queues and the API's read cache.

System tiles

Services up

The accent tile: how many of the services answer, such as "5 of 5", with "Everything answers" or "See which below".

Jobs waitingjobs

Jobs waiting or delayed, across the worker's queues.

Failed jobs keptjobs

Failed jobs the queues still hold. BullMQ keeps the latest 2,000.

Cache hit rate%

The share of reads served from the read cache, for this API replica since it started.

A dash means the API has no Redis to count in.

The services on System

The Services card, asked by the API just now. Each row has a state (Up, Behind, Down or Not configured) and a sentence:

API

"This replica answered", or Behind with "This replica is stopping" during a restart.

Postgres

Answered within 2 seconds, or did not.

Redis

Answered; or not configured or not answering, in which case reads go to Postgres (and, when not configured, limits are not counted).

Worker

Read from the heartbeat the worker writes to Redis every 15 seconds. Up when the heartbeat is under a minute old; Behind when it is older; Down when there has been none for two minutes (the heartbeat expires from Redis after 120 seconds).

AI app

The assistant's service. Up when it answers with a model; otherwise "Not configured, not reachable, or without a model".

The worker's job queues on System

The Job queues card counts each of the worker's three queues in Redis: collector (the Roblox collector and its scheduled jobs), github-organization (the GitHub collection) and owned-analytics (the daily studio-game analytics read). Columns: Waiting, Active, Delayed, Failed and Done, last hour. Roblox's rate-limit budget lives in the collector's memory, not in Redis, so it is not shown here; the Collector page has each endpoint's requests and refusals.

The read cache and its hit rate on System

The Read cache card (and the Cache hit rate tile, the share of reads answered from it) is this API replica's cache of reads since it started: Hits, Served while refreshing (an old answer given while a fresh one is read), Joined a read under way (a request that waited for the same read instead of starting another), Misses and Redis errors. Without Redis it says "No cache": every read goes to Postgres. With more than one API replica, each counts its own.

What is not in Admin

There is no game catalog editor or Teams page: members register games themselves, and an owner sets a game's release state on the game's own page. See Games and releases. Game API keys are managed on each game's Developer tab, not here.

Related: Roblox groups and keys, Collector and data freshness.

Updated