---
title: "Collaboration"
url: /docs/en-us/projects/collaboration
last_updated: 2026-06-19T03:26:24Z
description: "Studio's built-in collaboration tools let creators contribute independently, or work together with a team."
---

# Collaboration

> **Error:** Starting **June 25, 2026**, you and your collaborators must meet [age-based collaboration requirements](#age-based-collaboration-requirements) to use Studio's built-in collaboration tools.

Creating a high-quality experience demands many skills such as modeling, scripting, user interface design, and audio production. It's unlikely that one person has all of these skills, which makes collaboration between different roles an essential part of the development workflow.

With Studio's **built-in** **collaboration tools**, creators can contribute to experiences independently on their own time, or work together with their team all at the same time.

![Three creators working together in a collaborative session, each with different color markers to demonstrate what objects they're currently editing in the environment.](../assets/studio/collaboration/Collaborative-Session.jpg) ## Age-based collaboration requirements

> **Warning:** This requirement only applies if you're using Studio's collaboration tools with other creators. You can still use these tools by yourself without completing an age check.

To use Studio's collaboration tools with other creators, you must first complete an age check by either [verifying your ID](/docs/en-us/projects/../production/publishing/account-verification.md#verify-through-government-id) or [completing a facial age estimation](https://en.help.roblox.com/hc/en-us/articles/42295385001236-How-does-Roblox-estimate-my-age).

By default, you can only collaborate with creators in compatible age groups. For example, a 16-year-old creator can be in a collaborative session with a creator who is 17 and another who is 21. A creator who is under 13, however, must have parental permission to collaborate with creators who are older than 18.

| Your age group | Can collaborate with | Cannot collaborate with |
| --- | --- | --- |
| Under 9 | Users under 13 | Users 13 and older |
| 9–12 | Users under 16 | Users 16 and older |
| 13–15 | Users aged 9–17 | Users under 9 and 18+ |
| 16–17 | Users 13 and older | Users under 13 |
| 18+ | Users 16 and older | Users under 16 |

If you're **under 13** and your team includes creators outside of your age group, you have two options:

- **Trusted friends.** Add specific collaborators as [trusted friends](https://en.help.roblox.com/hc/en-us/articles/37725513985812-Unlocking-trusted-friends), who can collaborate with each other regardless of age. Trusted friend requests from users under 13 require parental approval.
- **Linked parent account.** Request permission to collaborate with all age groups through a [linked parent account](https://en.help.roblox.com/hc/en-us/articles/30428321333140-Parents-How-to-Link-Your-Child-s-Account). Parental permission to collaborate with all age groups doesn't guarantee access to every collaboration session. If another collaborator has their own permissions restricted to similar age groups or trusted friends only, you won't be able to join their session unless they add you as a trusted friend.

If you're **13 or older** and your team includes creators outside of your age group, you can add those collaborators as [trusted friends](https://en.help.roblox.com/hc/en-us/articles/37725513985812-Unlocking-trusted-friends). Trusted friends can collaborate with each other regardless of age. For larger teams, you can add multiple collaborators as trusted friends at once from Studio.

## Manage collaborators

Collaborators you add to an experience have permission settings that correspond to their level of access to the experience. As follows are the different user permission settings:

| Permission | Description |
| --- | --- |
| **Owner** | User is the owner of the experience and has permission to configure other users' permissions. |
| **Edit** | User has permission to edit the experience. This also grants the user **Play** permission. |
| **Play** | User has permission to play the experience privately. |
| **No Access** | User does not have either **Edit** or **Play** permissions. |

There are some small differences when managing collaborators in [group‑owned experiences](#group-owned-experiences) vs. [user‑owned experiences](#user-owned-experiences).

### Group-owned experiences

For [group](/docs/en-us/projects/groups.md) experiences, only the group owner or members with sufficient permissions can manage the group's roles, either across **all group experiences** or on a **per‑experience** basis. Such users can also add individual collaborators to group‑owned experiences in the same workflow as [user‑owned](#user-owned-experiences) experiences, but only for **Play** access.

#### All group experiences

If you're the group owner or a member with sufficient permissions, you can configure collaboration across **all** group experiences, for example grant **Edit** permission to an "Audio Artist" group role so they can fine-tune audio playback across multiple group experiences.

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. Enable [Edit all group experiences](/docs/en-us/projects/groups.md#roles-and-permissions) for roles that should have editing permission. Remember to click **Save Changes** for each role that you change. In Studio's **Manage Collaborators** window for any group-owned experience, eligible roles display **Edit** permission but are muted to indicate that you can't change the permission level from Studio.![Studio's mezzanine bar with the Collaborate button highlighted.](../assets/studio/general/Toolbar-Manage-Collaborators.png)![Manage Collaborators window showing permission level selection for each group role.](../assets/studio/collaboration/Edit-Permission-All-Group-Experiences.png)

#### Per-experience

If you're the group's owner, you can grant permissions on a per-experience basis to roles that do not have those permissions across all group experiences. For example, you can temporarily grant **Edit** permission to an "FX Artist" group role so they can fine-tune visual effects before an experience's public release.

1. In Studio's **Manage Collaborators** window for any group-owned experience, select **Edit** from the permissions dropdown for the desired roles. Remember that you can only modify roles that do **not** already have edit permission across all group experiences.![Studio's mezzanine bar with the Collaborate button highlighted.](../assets/studio/general/Toolbar-Manage-Collaborators.png)![Manage Collaborators window showing permission level selection for each group role.](../assets/studio/collaboration/Edit-Permission-Per-Experience.png)
2. Click **Save** for your collaboration settings to take effect. All group members within the modified roles should now have **Edit** permission for this experience only; this action won't grant them equal permission to other group experiences.

### User-owned experiences

For user-owned experiences, you can grant **Play** access to any user or [group](/docs/en-us/projects/groups.md), but you can only grant **Edit** permission to Roblox friends.

To give **Edit** permission to a friend for an experience that you own:

1. With the experience open in Studio, click the **Collaborate** button on the right side of the mezzanine bar.![Studio's mezzanine bar with the Collaborate button highlighted.](../assets/studio/general/Toolbar-Collaborate.png)
2. Type into the search bar at the top to search for a collaborator to add. A dropdown appears listing matching collaborators, with friends indicated by the **Friend** label. Select the collaborator to add.![Manage Collaborators window showing search query for a Roblox friend.](../assets/studio/collaboration/Collaborator-Search.png)
3. Select **Edit** from the permissions dropdown for the friend, then click **Save** for your collaboration settings to take effect.

## Access a session

Those who have permission to edit an experience can join a collaborative session as follows:

1. Navigate to the [Creator Dashboard](https://create.roblox.com/dashboard/creations).
2. Locate the experience depending on whether it's [group-owned](#group-owned-experiences) or [user-owned](#user-owned-experiences). #### Group-Owned Experience
  1. Select the group from the upper‑left selector menu.
  2. Make sure **Creations** is selected on the left and **My Experiences** in the main panel.**My Experiences****Shared With Me**#### User-Owned Experience
  1. Select your personal account from the upper‑left selector menu.
  2. Make sure **Creations** is selected on the left and **Shared With Me** in the main panel.**My Experiences****Shared With Me**
3. Hover over the experience's tile and click the **Edit in Studio** button to collaborate.![A close up view of an experience tile with the Edit in Studio button highlighted.](../assets/creator-dashboard/Edit-Button-Experience.png)

### View collaborators

While working in a collaborative session, you can see the current collaborators in the upper-right corner of Studio, each with a unique assigned color that's consistent across all collaborators' devices.

![Studio's menu bar with icons of the current collaborators highlighted.](../assets/studio/general/Toolbar-Current-Collaborators.png)

To view more details on the current collaborators, click on any of the icons to open the **Live Collaborators** window. In this window, you can see whether a user is active or inactive inside Studio, as well as an indication of where the user is working. Users become inactive if they do not use Studio for more than 5 minutes.

![Live Collaborators window with icons of current collaborators, as well as their activity status.](../assets/studio/collaboration/Live-Collaborators-Status.png) ### Selection visualization

By default, selected code in the [Script Editor](/docs/en-us/studio/script-editor.md) and selected objects in the 3D viewport are highlighted with the unique color assigned to each collaborator. Additionally, the [Explorer](/docs/en-us/studio/explorer.md) window marks selected objects with dots in these assigned colors to indicate selection by other collaborators.

![A viewport view of a block part pyramid. The parts near the top of the pyramid are highlighted in green to signify that the collaborator with the green color has the parts selected in their Studio instance.](../assets/studio/collaboration/User-Color-Parts.jpg)

![A close up view of the three block part objects in the Explorer window. There is a green circle near the objects to signify that the collaborator with the green color has the parts selected in their Studio instance.](../assets/studio/collaboration/User-Color-Explorer.png)

To make all collaborators' selections invisible to only you while still seeing their work, uncheck **Show collaborator selections** at the bottom of the [Live Collaborators](#view-collaborators) window.

### Join collaborators

To quickly jump to a location in the workspace or to the exact line in a script that a collaborator is editing, hover over their name in the [Live Collaborators](#view-collaborators) window and click **Join**.

## Comments

Roblox Studio has a **comments** feature that lets you pinpoint an object in the 3D viewport and start a conversation with your collaborators, leave to-do notes, and more. Comments update in real time which lets you and your team receive and respond to feedback without disrupting your workflow in Studio. You can also receive personalized [notifications](#notifications) to help you stay on top of feedback, even when you're not using Studio.

### Workflow

To create a comment, click the **Comment** button on the right side of Studio's mezzanine (keyboard shortcut `C`).

![Studio's mezzanine bar with the Comments button highlighted.](../assets/studio/general/Toolbar-Comments.png)

In the viewport, your cursor turns blue. Click on any object that inherits from `Class.BasePart` (most do, including `Class.Terrain`), type your comment, and click **Submit**.

![Blue comment cursor in the viewport.](../assets/studio/collaboration/Comments-Cursor.jpg)
> **Info:** To **tag** a collaborator in your comment, use the `@username` syntax. You can tag any collaborator in the group for a [group‑owned](#group-owned-experiences) experience or any user with **Play** or **Edit** permissions in a [user‑owned](#user-owned-experiences) experience.

Comments appear in the **Comments** window, accessible from Studio's **Window** ⟩ **Collaboration** menu, with the most recent comments at the top. From within the **Comments** window, you can:

- Single-click on a comment to show the full conversation in the 3D viewport.
- Double-click on a comment to zoom in on it in the viewport.
- Use the **⋯** menu in the upper-right corner to show resolved comments, filter for only the comments that you've been tagged in, or hide comments in the viewport.
- Resolve comments as you and your team address them. After you resolve a comment, it disappears from both the viewport and the main list, but it isn't completely gone; you can always un‑resolve it later.

### Notifications

To help you stay on top of feedback even when you're not using Studio, you'll receive an **email digest** that recaps all recent activity. Each email digest provides a simple overview of comment activity per place, including:

- When someone mentions (tags) you in a comment, for example `@username`.
- When someone comments in a thread that you previously replied to or were mentioned in.
- When someone resolves a thread that you previously replied to or were mentioned in.

From within the email overview, simply click **View in Studio** to go directly to the conversation in Roblox Studio.

> **Info:** You're always in control of both the type and source of comments which make up email digests. Mentions and reply notifications are on by default, while resolution notifications are off. You can also unsubscribe from a specific place or thread if you don't need updates.
## Collaborative scripting

In a collaborative session, you can code together in real time through [live scripting](#live-scripting), or you can [draft](#drafts-mode) scripts in a more focused environment before committing them to a collaborator-shared repository.

### Live scripting

**Live Scripting** lets collaborators code together in real time. In the [Script Editor](/docs/en-us/studio/script-editor.md), each collaborator's cursor color matches their assigned color in the [Live Collaborators](#view-collaborators) window.

![Script Editor window showing cursors for two collaborators, colored according to their assigned color in the Live Collaborators window.](../assets/studio/collaboration/Live-Scripting-Cursors.png)

![Live Collaborators window with icons of current collaborators, as well as their activity status.](../assets/studio/collaboration/Live-Collaborators-Status.png)

While live scripting, edits are auto‑saved every 5 minutes just like place edits, and a collaborator can manually save a script at any time with `Ctrl``S` (`⌘``S`). Saved or auto‑saved versions are logged in the [Script History](#view-script-history) window.

> **Info:** Live Scripting is **enabled** by default. If you and your team prefer to collaborate on scripts in an environment similar to source control, explore [Drafts](#drafts-mode) mode.
### Drafts mode

Through **Drafts** mode, you can independently edit and test scripts without affecting the experience for others. After you finish drafting a script, you can [commit](#commit-drafts) it to the shared repository and use [collaborative testing](/docs/en-us/studio/testing-modes.md#collaborative-testing) to test the committed version with others.

> **Warning:** Drafts Mode is **disabled** by default. To enable it, open Studio's **File** ⟩ **Experience Settings** window, select the **Other** tab, and turn on **Enable Drafts Mode**.
>
> Note that all collaborators will need to exit the session for the change to take effect. Alternatively, you can [disable collaboration](#disable-collaboration) and then reenable it to restart the session.
#### Commit drafts

Once you've edited a script, it appears in the **Drafts** window, a non‑default window which you must add to a [custom tab](/docs/en-us/studio/ui-overview.md#custom-tabs) in Studio's toolbar.

![The Drafts window with two drafted script instances.](../assets/studio/collaboration/Drafts-Window.png)

Drafts are saved to your local file system and persist between Studio sessions on the same machine. To commit your local edits to the repository, left-click a script, or hold `Shift` and left-click to select multiple scripts. Then click **Commit** to commit all selected scripts.

![The Drafts window with the Commit button highlighted.](../assets/studio/collaboration/Drafts-Commit.png) #### Compare and merge changes

If another collaborator commits changes to the same script that you're editing, an icon with a green **⊕** symbol appears in the **Drafts** window. To view their changes, right‑click the script and select **Compare With Server**.

![The Drafts window with the green plus icon highlighted to the left of a changed script, and the right-click popup window showing with the Compare With Server option highlighted.](../assets/studio/collaboration/Drafts-Compare.png)

In the **(Diff)** tab that opens in the [Script Editor](/docs/en-us/studio/script-editor.md), code that other collaborators changed or deleted appears in red, while code that you updated appears in green.

![A close up view of lines that were edited by different collaborators.](../assets/studio/collaboration/Drafts-Diff-Result.png)

To merge their changes into your script:

1. In the **Drafts** window, right‑click the script and select **Merge From Server**.![The Drafts window right-click popup window showing with the Merge From Server option highlighted.](../assets/studio/collaboration/Drafts-Merge.png)
2. In the merge window, you can pick which code to keep, or make manual edits.
  - Check **Draft** to keep your changes, or leave it unchecked to discard them.
  - Check **Server** to merge the committed changes into your draft, or leave it unchecked to ignore them.
  - Check **Other** to manually edit the script and save the changes to your draft.
3. Once you've previewed the merge resolution, click **Merge All** to update your local script.

#### Restore deleted scripts

If a collaborator deletes a script that you're editing, an icon with a red **⊘** symbol appears in the **Drafts** window. To restore the script, right‑click it and select **Restore Script**. Scripts are restored to the place's **Workspace** tree, so you may need to manually re‑parent them back to their original location.

![The Drafts window with the red cross icon highlighted to the left of a deleted script, and the right-click popup window showing with the Restore Script option highlighted.](../assets/studio/collaboration/Drafts-Restore.png) ### View script history

All script changes, whether saved by a collaborator, auto-saved, or committed by a collaborator through [Drafts](#drafts-mode) mode, are logged in the **Version History** window. To access it:

1. Right-click the script in the [Explorer](/docs/en-us/studio/explorer.md) window and select **View Script History**.
2. In the **Version History** window that opens, you'll see all committed versions of the script, the commit date, which collaborator committed, and more. From this window, the following actions are possible: #### Compare With Previous To compare any version (except the oldest) with its previous version, select it and click **Compare With Previous Version**. In the **(Diff)** tab that opens in the [Script Editor](/docs/en-us/studio/script-editor.md), code from the newer version appears in green while code from the older version appears in red. #### Compare Selected To compare any **two** versions, hold `Ctrl` or `⌘` and select both, then click **Compare Selected Versions**. In the **(Diff)** tab that opens in the [Script Editor](/docs/en-us/studio/script-editor.md), code from the newer version appears in green while code from the older version appears in red. #### Open If the version **Comment** indicates just one script was committed, select it and click **Open Script** to open it in the [Script Editor](/docs/en-us/studio/script-editor.md). If the version **Comment** indicates more than one script was committed (commonly the result of an auto‑save on multiple unsaved scripts), you can click **Show** within the version's row to open a popup displaying the script(s) and their respective version. Then, from the version history window, click **Open All Scripts From Batch** to open them in the [Script Editor](/docs/en-us/studio/script-editor.md).

## Save and publish

During a collaborative session, Studio automatically saves the project to the cloud every four minutes.

## Revert to previous versions

The owner of an experience can revert changes made by other editors. See [here](/docs/en-us/projects/configure-games.md#access-version-history) for instructions.

> **Error:** Be careful when reverting changes. If anyone is currently editing the experience in a collaborative session, their changes may still auto‑save and overwrite the revert action. To ensure that nobody else is editing the place when you revert, [disable collaboration](#disable-collaboration).

You might also want to check [Activity History](/docs/en-us/projects/activity-history.md). This view provides a chronological event log that improves team visibility into key experience settings.

## Disable collaboration

**Team Create** is the core Studio feature that enables collaboration. Workflows that involve the [Manage Collaborators](#manage-collaborators) dialog will automatically enable the feature, but you can manually disable it if necessary.

1. If the [Live Collaborators](#view-collaborators) window isn't already open, click on any of the collaborator icons to open it.
2. In the bottom-right corner of the window, click the **⋯** button and select **Disable Team Create**.
3. When prompted, confirm ending the session to reload the place in a non‑collaborative state.