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 differnt color markers to demonstrate what objects they're currently editing in the environment.

Managing 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:

OwnerUser is the owner of the experience and has permission to configure other users' permissions.
EditUser has permission to edit the experience. This also grants the user Play permission.
PlayUser has permission to play the experience privately.
No AccessUser does not have either Edit or Play permissions.

There are some small differences when managing collaborators in group‑owned experiences vs. user‑owned experiences.

Group-Owned Experiences

For group experiences, only the group owner can manage permissions through the group's roles, either across all group experiences or on a per‑experience basis. Group owners can also add individual collaborators to group-owned experiences in the same workflow as user-owned experiences, but only for Play access.

If you're the group's owner, you can set permissions across all group experiences, for example to grant Edit permission to an "Audio Artist" group role so they can fine-tune audio playback across all of your experiences.

  1. Navigate to the Groups page and select the group.

  2. Click the button in the upper-right corner and select Configure Group.

    A group's landing page with the ellipis button and Configure Group menu item highlighted.
  3. In the left column of the group configuration page, select the Roles tab.

    A close up view of the left column with the Roles navigation item highlighted.
  4. Select each group role that you want to give editing permission to and enable Create and edit group experiences.

    A close up view of an group role settings. The Create and edit group experiences setting is enabled.

    In Studio's Manage Collaborators window for any group-owned experience, these roles display Edit permission but are muted to indicate that you can't change the permission level from Studio.

    Studio's menu bar with the Collaborate button highlighted. Manage Collaborators window showing permission level selection for each group role.

User-Owned Experiences

For user-owned experiences, you can grant Play access to any user or group, 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 in the upper-right corner.

    Studio's menu bar with the Collaborate button highlighted.
  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 below their name. Select the collaborator to add.

    Manage Collaborators window showing search query for a Roblox friend.
  3. Select Edit from the permissions dropdown for the friend.

    A close up view of a collaborator's tile with the permission dropdown menu highlighted.
  4. Click Save for your collaboration settings to take effect.

Accessing a Session

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

  1. Navigate to the Creator Dashboard.

  2. Locate the experience depending on whether it's group-owned or user-owned.

    Select the group from the upper‑left selector menu. Then, make sure Creations is selected on the left and My Experiences in the main panel.

    A close up view of the Creator Dashboard with the group selected, as well as Creations and My Experiences.
  3. Hover over the experience to collaborate on and click the Edit in Studio button.

    A close up view of an experience icon with the Edit in Studio button highlighted.

Viewing 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.

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.

Selection Visualization

By default, selected code in the Script Editor and selected objects in the 3D viewport are highlighted with the unique color assigned to each collaborator. Additionally, the Explorer 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.
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.

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 window.

Joining 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 window and click Join.

Chatting with Collaborators

To chat with collaborators during a session:

  1. In the View tab, click Team Chat.

    Studio's View tab with the Team Chat button highlighted.
  2. Click in the input text field, type your message, and press Enter to send it.

Collaborative Scripting

In a collaborative session, you can code together in real-time through live scripting, or you can draft 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, each collaborator's cursor color matches their assigned color in the Live Collaborators window.

Script Editor window showing cursors for two collaborators, colored according to their assigned color in the Live Collaborators window.
Live Collaborators window with icons of current collaborators, as well as their activity status.

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 CtrlS (S). Saved or auto‑saved versions are logged in the Script History window.

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 it to the shared repository and Team Test the committed version with collaborators.

Committing Drafts

Once you've edited a script, it appears in the Drafts window, accessible from the View tab. Drafts are saved to your local file system and persist between Studio sessions on the same machine.

Studio's View tab with the Drafts button highlighted. The Drafts window with two drafted script instances.

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.

Comparing and Merging 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.

In the (Diff) tab that opens in the Script Editor, 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.

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.
  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.

Restoring 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.

Viewing Script History

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

  1. Right-click the script in the Explorer 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:

    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, code from the newer version appears in green while code from the older version appears in red.

Saving and Publishing

During a collaborative session, Studio automatically saves the project to the cloud every five minutes. The Output window shows the place name and save location after the save is successful.

The Output window with an auto-save message.

Reverting to Previous Versions

The owner of an experience can revert changes made by other editors. See here for instructions.

Disabling Collaboration

Team Create is the core Studio feature that enables collaboration. Workflows that involve the Manage Collaborators dialog will automatically enable the feature, but you can manually disable it if necessary.

  1. If the Live 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.