HQ, the admin console

Where the network is configured. You need view_hq to open it at all.

The four sections

People. Who holds which role, and where. Every assignment carries a scope: the whole network, one group, or one hub. Somebody can run one group without touching another.

Roles. The role editor, built like Discord's and Roblox's so it needs no explaining. A role is a set of permissions; assignments hand a role to a person within a scope.

Groups. Every group on the network, and a way into each one's editing view. Creating a group used to mean writing a row on the server by hand, which is why it is a form now.

Site settings. Network-wide settings.

Scopes are the whole idea

A permission on its own means nothing. A permission plus a scope is a real grant.

manage_docs at network scope edits documentation anywhere. The same permission scoped to one group edits that group's and nothing else. That is what lets group staff run their own page without being able to reach into somebody else's.

An assignment against a scope nobody recognises still shows, with the raw value. It is a real grant either way, and hiding it would be worse than showing something ugly.

Creating a group

The form takes the group's identity and its Roblox group ID. The ID you supply becomes the group's address on the site permanently, so it is worth getting right the first time.

Renaming a group moves that address and leaves a redirect behind, so old links keep working. Deleting one takes everything attached to it and does not come back.

Hiding is the reversible option. Mark a group unlisted and it drops out of the directory, the counts and every picker while staying exactly where it is. Reach for that before you reach for delete.

Other consoles behind the same door

The records archive has its own admin pages for cases, definitions, the audit trail and announcements. Telemetry has a page. Chancery access keys have one. Each checks its own permission rather than assuming that getting into HQ was enough.

It's not working

HQ will not open. You do not hold view_hq. That is separate from any group permission you might have.

A section is empty. You hold nothing at that scope. Most pages show what you can act on rather than everything that exists.

You granted somebody a permission and it did nothing. Check the scope. Network scope and group scope look identical in a list and behave nothing alike.

A group you created is not in the directory. It may have shipped unlisted. Check its settings.

A rename broke somebody's link. It should not have. Renames leave a redirect. If a link genuinely 404s, say which one, because that means a table was missed when the rename ran.