Products
A workspace does not arrive with a tab for everything. It arrives with five, and you add the rest when somebody decides they are needed. Two rules keep that safe: switching a product off never stops the record underneath it, and you can only add a product you could already open.
What you start with
A new workspace has exactly five products switched on: Ranking, Members, Staff, Roles and Payouts. They are the parts a Roblox group needs to be run at all: change a rank, see who is in the group, keep a record of your team, decide what that team may do, and pay them.
on for a new workspace
ranking ranking.view
members members.view
staff staff.view
roles staff.view
payouts payouts.viewThose five are not privileged after the first day. Every one of them can be removed, and a group that pays nobody should not carry a Payouts tab forever. There is no floor: a workspace may end up with none of them switched on.
Never chosen is not the same as chosen empty
Adding a product
The Add a product button sits at the bottom of the sidebar, under the products you already have and under Settings. It opens the catalogue: categories down the left, with a count of how many in each are on, and the products in the chosen category on the right. Adding is one click, and so is removing.
Reading the catalogue needs members.view. Actually adding or removing one needs workspace.manage, because it changes what the whole team sees rather than what one person sees, and the picker says so rather than silently doing nothing. Both directions are written to the audit log, as workspace.module_enabled and workspace.module_disabled, with the name of whoever clicked.
Switching one off
Switching a product off hides its surface and nothing else. The entry leaves the sidebar and its page answers with a short notice instead of its contents. What is underneath keeps running.
The audit log is still written for every privileged action whether or not the Audit log page is on: switching it off hides the view, never the evidence. The hourly sweep still runs with Reconciliation off, still mirrors ranks and still detects drift. Game servers keep reporting with Activity off, so nothing is lost while it is off and the numbers are there when you turn it back on.
Why it works this way
Only what you can open
Every entry in the catalogue names the permission its own page requires, and you can only add a product you could already open. Enabling is therefore never a way to widen your own access: the most it can do is put a door in the sidebar that you already had the key to.
A product you lack the permission for is still listed, shown locked with the permission named, so the answer is needs activity.view rather than a gap where a product used to be. The check is not only in the browser: the server refuses the same request and says which permission it was missing.
Removing is not held to the same test. Taking away a page you cannot see is still tidying up, and workspace.manage was already required to be in the picker at all.
The full catalogue
Every product, the category it appears under, the permission its page requires, and whether a new workspace starts with it.
| Product | Category | Permission | On by default |
|---|---|---|---|
| Ranking | Run the group | ranking.view | Yes |
| Members | Run the group | members.view | Yes |
| Staff | Run the group | staff.view | Yes |
| Roles | Run the group | staff.view | Yes |
| Activity | Work tracking | activity.view | No |
| Sessions | Work tracking | sessions.view | No |
| Quotas | Work tracking | activity.view | No |
| Time off | Work tracking | timeoff.request | No |
| Payouts | Money | payouts.view | Yes |
| Payroll | Money | payouts.view | No |
| Feed | Community | members.view | No |
| Handbook | Community | knowledge.view | No |
| Promotions | Community | promotions.recommend | No |
| Conduct | Community | discipline.view | No |
| Moderation | Community | moderation.ban | No |
| Audit log | Oversight | audit.view | No |
| Reconciliation | Oversight | members.view | No |
