---
title: "Groups (teams)"
url: /docs/en-us/projects/groups
last_updated: 2026-06-19T03:26:26Z
description: "Explains Roblox groups and how to collaborate with multiple creators on the same experience."
---
# Groups (teams)
A Roblox **group** allows multiple creators to work on the same experience, use the same assets, share profits, and give credit to all contributors.
> **Error:** Group ownership of experiences helps creators collaborate and operate as independent studios. If a conflict arises within a group, Roblox cannot help arbitrate or resolve disagreements.
## Group creation
Creating a group costs 100 Robux. New groups maintain certain capabilities on the legacy [Groups](https://www.roblox.com/communities) pages, but improved workflows and options for [configuring roles/permissions](#roles-and-permissions) and inviting members are only available on the [Creator Dashboard](https://create.roblox.com/dashboard/creations).
> **Warning:** Before creating a group, carefully read through the [rules and expectations](/docs/en-us/projects/group-guidelines.md) for group management.
To create a new group:
1. Navigate to the [Creator Dashboard](https://create.roblox.com/dashboard/creations), expand the account switcher in the upper‑left, and click the **+** button.
2. On the **Create Group** page, upload an image for the group logo and enter the group name.
3. When ready, click the **Purchase** button. Once the group is created, you'll be directed to the group profile page where you can modify the group's details, including adding up to three social links.
## Roles and permissions
Group members can be assigned one or multiple **roles** within a group, and each role has **permissions** which specify the abilities of its members.
> **Warning:** Role configuration is only accessible if you're the group owner or you have permission to create, configure, and assign group roles.
> **Error:** Roles created using the legacy [Groups](https://www.roblox.com/communities) pages will continue to operate on the legacy system and can only be managed through the legacy workflow. If permissions were granted to a legacy role, **the member will continue to have those permissions**, so it's recommended that you revoke permissions/roles in the legacy system and then migrate members to the new system.
1. From the [Creator Dashboard](https://create.roblox.com/dashboard/creations), expand the account switcher in the upper‑left and select the group.
2. Expand the account switcher again, select **Settings** under the group's name, then select **Roles**.
3. For each role, carefully confirm the permissions under the **Permissions** tab.** Group Permissions**| **Add or remove group members** | Members with this role can [invite](#manage-members) and [remove](#member-removal) other members. |
| --- | --- | | **Add or remove [role] role members** | Members with this role can give or remove the role to/from other members in the group. This permission is useful for roles that should have some management permissions but not at the super‑admin level. | | **Configure limited roles** | Members with this role can configure the roles they are assigned and assign permissions to those roles that they themselves have. | | **Administrate all roles** | Members with this role can create, delete, and configure any role in the group. This is a super‑admin permission, as it provides nearly full access. | | **Configure group profile** | Members with this role can update the group's name, description, and other metadata. Does not include transferring ownership, which only the owner can do. | | **View group activity history** | Members with this role can view [group activity history](#group-activity-history). |** Experience Permissions**| **Playtest all group experiences** | Members with this role can play all experiences owned by the group, whether they're private or public. Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). |
| --- | --- | | **Edit all group experiences** | Members with this role can edit all experiences and [assets](/docs/en-us/projects/assets.md) owned by the group and use all features in the [Data Stores Manager](/docs/en-us/cloud-services/data-stores/data-stores-manager.md). Does not include editing an experience outside of a [collaborative](/docs/en-us/projects/collaboration.md) session or saving a place from one experience into another experience. Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). | | **Edit and publish all group experiences** | Members with this role can both edit experiences, as above, and also publish experiences to Roblox. Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). | | **View all analytics for group experiences** | Members with this role can access the [analytics](/docs/en-us/production/analytics.md) of all experiences owned by the group, even if they don't have edit access. Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). | | **Create and configure share links** | Members with this role can create/configure [share links](/docs/en-us/production/promotion/share-links.md). | | **Create and configure experience events** | Members with this role can create/configure [experience events](/docs/en-us/production/promotion/experience-events.md). | | **Configure bans for all group experiences** | Members with this role can ban and manage banned users for all experiences owned by the group. | | **Access read-only chat and configure bans for all group experiences** | Members with this role can view all in-experience chat messages and ban or manage banned users across all experiences owned by the group.
To view in-experience chat messages, enable **Read-only view** in the in-experience settings. | | **Configure monetization for all group experiences** | Members with this role can manage monetization products such as [passes](/docs/en-us/production/monetization/passes.md), [developer products](/docs/en-us/production/monetization/developer-products.md), [subscriptions](/docs/en-us/production/monetization/subscriptions.md), and more. Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). | | **List, create, update, and delete secrets for all group experiences** | Members with this role can see the list of [secrets](/docs/en-us/cloud-services/secrets.md) and can create, update, and delete secrets for all experiences owned by the group. Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). |** Group Revenue**| **View group revenue** | Members with this role can view the group Robux balance, any configured recurring split payouts, and revenue logging features. |
| --- | --- | | **Configure and spend group revenue** | Members with this role can view all group revenue, as above, and also directly manage it. This includes setting up [recurring payouts](#recurring-payouts) and sending [one‑time payouts](#one-time-payouts) to collaborators. | | **Create ad campaigns for the group** | Members with this role can advertise the group. |** Avatar Item Permissions**| **Configure avatar items** | Members with this role can configure avatar items such as clothing. |
| --- | --- | | **Create avatar items** | Members with this role can create avatar items such as clothing. |** Open Cloud Permissions**| **Manage own API keys** | Members with this role can configure and upload their own [Open Cloud API keys](/docs/en-us/cloud/auth/api-keys.md) to the group, but not configure everyone else's. |
| --- | --- | | **Manage all API keys** | Members with this role can upload their own [Open Cloud API keys](/docs/en-us/cloud/auth/api-keys.md) to the group, as well as configure everyone else's. |** Asset Permissions**| **View development items** | Members with this role can view development items owned by the group, for example **Audio**. |
| --- | --- | | **Create and configure development items** | Members with this role can upload and configure asset development items such as **Decals**. | | **Manage development item permissions** | Members with this role can configure permissions of development items, for example audio sharing. |** Data Stores**| **View data stores for all group experiences** | Members with this role can view data stores for all group experiences through the [Data Stores Manager](/docs/en-us/cloud-services/data-stores/data-stores-manager.md), but they cannot delete data. Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). |
| --- | --- | | **Edit data stores for all group experiences** | Members with this role can delete specific keys within data stores for all group experiences through the [Data Stores Manager](/docs/en-us/cloud-services/data-stores/data-stores-manager.md). Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). | | **Delete data stores for all group experiences** | Members with this role can delete entire data stores for all group experiences through the [Data Stores Manager](/docs/en-us/cloud-services/data-stores/data-stores-manager.md). Optionally available as a [per‑experience permission](/docs/en-us/projects/configure-games.md). |
4. **IMPORTANT** Click the **Save Changes** button to apply the permission settings.
5. **OPTIONAL** Click the **Settings** tab and choose a color for the role, then click **Save Changes**.
> **Info:** A role's **Settings** section is also where group owners and members with sufficient permissions can remove a role entirely through the **Delete Role** button.
## Manage members
> **Warning:** Member configuration is only accessible if you're the group owner or you have permission to manage other members and their roles.
Once [roles](#roles-and-permissions) have been configured for the group, members can be invited and assigned from either the **Members** tab within a specific role or from the **Collaboration** ⟩ **Members** page.
_Collaboration ⟩ Roles ⟩ Members tab_
_Collaboration ⟩ Members ⟩ Member tab_
From the add/invite popup, locate a creator by typing their username into the search field. Creators will be notified when invited to your group (a customizable setting within the creator notification system), or you can copy the **group link** and share it with invited creators through other means.
### Manage roles
To assign roles to a member, hover over their name, click the **Add Role** button, and then manage roles from the popup.
To quickly unassign a role from a member, hover over it and click the **×** button.
> **Error:** Currently, roles configured through the legacy [Groups](https://www.roblox.com/communities) pages appear for each member. If permissions were granted to a role through the legacy system, **the member will continue to have those permissions**, so it's recommended that you revoke permissions/roles in the legacy system and then migrate members to the new system.
### Member removal
To remove a member entirely, hover over their name, click the **⋮** button, and then select the removal option. A dialog will appear for you to confirm the action.
 ## Manage payouts
If you're the group owner or you have the correct [permission](#roles-and-permissions) within **Group Revenue**, you'll find a **Payouts** page under **Finances** in the left navigation. Here, you can send one‑time payouts, as well as define percentage splits with other members.
> **Info:** Some groups may not have this page unlocked initially for various reasons, such as the age of the group or insufficient funds to payout.
> **Warning:** Payouts cannot be shared across group members for experiences that charge for [paid access in local currency](/docs/en-us/production/monetization/paid-access-local-currency.md).
### One-time payouts
One-time payouts can be made to members in a batch, selecting a set amount for each. Safety features include 2FA challenges, confirmation dialogues, and checks around the eligibility of members being paid.
Once you click the **Send Robux** button, you can choose payout recipients from the popup or upload a `.csv` spreadsheet file with the columns `userId` and `payoutInRobux`, for example:
| userId | payoutInRobux |
| --- | --- |
| 012345 | 5000 |
| 098765 | 7000 |
### Recurring payouts
Recurring payouts can also be made across the entire group **and** per‑experience, assigning a percentage payout to each member before the remainder enters the group's overall balance.
Consider the following scenario where a group experience **Laser Maze** is split 40%–30%–10% among three members, with a remainder of 20%.
Assuming the experience earns 1000 Robux, the three members receive 400, 300, and 100 Robux respectively (40%–30%–10%).
The remaining 200 Robux (20% of the experience split) passes onward to the **group split** percentages, defined at 20%–20%–10% among the same three members; they receive an additional 40, 40, and 20 Robux respectively.
The remaining 100 Robux (50% of the group split) is placed in the group's overall balance.
> **Warning:** Note that revenue from [private server](/docs/en-us/production/monetization/private-servers.md) subscriptions does not change if you adjust split percentages at a later time, meaning that if a player buys a private server subscription, the split percentages at time of purchase will apply to that particular subscription forever (until it is canceled). This policy may be changed in the future.
## Group activity history
Group members with the **View group activity history** permission can view detailed activity such as role changes and publishing actions from the **Activity History** section under **Collaboration** on the Creator Dashboard. This is also a useful way for group owners to moderate activity that may violate [group guidelines](/docs/en-us/projects/group-guidelines.md).
## Intellectual property protection
Group members with permission to edit all group experiences can enable the [Place Copying](/docs/en-us/projects/configure-games.md#allow-copying) setting for a creation, potentially allowing the entire Roblox community to copy it and use assets within it. To help protect intellectual property in a group, the owner or members with sufficient permissions should:
- Confirm that each member is [assigned the appropriate role](#manage-roles).
- Check that each group role has the correct [permissions](#roles-and-permissions).
- Confirm that the [Place Copying](/docs/en-us/projects/configure-games.md#allow-copying) setting is disabled before private assets are added.