Roblox groups and keys

How the studio registers its Roblox groups, why each has exactly one Open Cloud key, and what a key is used for.

Studio / The studio's rules

The studio publishes its games under Roblox groups. An owner registers each group on Admin, Groups together with exactly one Open Cloud API key for it. A group cannot exist in the panel without its key, and a key belongs to one group. The key lets the studio read the group's games, private ones included, and their daily analytics.

What the key is for

  • Registering a game. The key reads the game, private ones included, and proves the group owns it.

  • Refreshing a game from Roblox (name, description, visibility).

  • Owned analytics. The worker reads each studio game's daily numbers (players, retention, revenue, and more) with its group's key once a day.

A game whose group has no registered key cannot be registered, and its analytics show "Not configured".

How a group and its key are registered

  1. Create the key on Roblox

    On the Creator Dashboard, signed in as the studio's holder account, with the group selected, generate the key with the access listed below.

  2. Add the group in the panel

    On Admin, Groups, choose Add group, enter the group id and the key, then Add and check.

  3. Read the result

    The group's card shows the key's state and what it may read.

Every click on Roblox's side is on Admin, Groups.

A group key's path. The studio's holder account creates the key on the Creator Dashboard. An owner pastes it on Admin, Groups. The panel asks Roblox to describe the key and read the group. If a required permission is missing, nothing is stored. Otherwise the key is sealed in the database and used for registering games, refreshing them, and the daily owned analytics.

What a key must allow

These are the permissions a group key needs. Before storing a key, the panel asks Roblox to describe it. It must be enabled, not expired, and hold group:read and universe:read, and it must be able to read the group. Analytics, developer products, game passes and user restrictions are reported if missing but do not block. All permissions are read-only.

group:read

Required. Checking the key against the group.

universe:read

Required. Reading the group's games, private ones included.

universe.analytics:read

Optional. Players, visits, retention, revenue and the rest of owned analytics.

developer-product:read

Optional. Each developer product and its price.

game-pass:read

Optional. Each game pass and its price.

universe.user-restriction:read

Optional. Who is banned from each game and why.

Who holds the keys

Keys are created on the Creator Dashboard by the studio's holder account, with the group selected. Only owners add, check, replace or remove a key. Members see each group's public profile and never a key or its fingerprint. Personal Roblox keys in Settings are retired.

Keys never leak

A key is sealed in the database. It never appears in a response, a log line, an error message, the browser or the assistant. Every add, replace, check and removal is written to the audit log.

Games outside the studio's groups

A game published under a user rather than a group cannot be registered. The studio publishes under groups.

Related: Projects, Admin pages, Admin Groups.

Updated