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.
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:
| 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 vs. user‑owned experiences.
Group-Owned Experiences
For group 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 experiences, but only for Play access.
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.
From the Creator Dashboard, select the group from the View As dropdown menu and navigate to Collaboration ⟩ Roles.
Enable Edit all group experiences 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.
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:
With the experience open in Studio, click the Collaborate button in the upper-right corner.
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.
Select Edit from the permissions dropdown for the friend.
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:
Navigate to the Creator Dashboard.
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.
Hover over the experience to collaborate on and click the Edit in Studio button.
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.
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.
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.
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:
In the View tab, click Team Chat.
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.
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.
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 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 it to the shared repository and Team Test the committed version with collaborators.
Drafts Mode is disabled by default. To enable it, open the Game 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 and then reenable it to restart the session.
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.
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.
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.
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.
To merge their changes into your script:
In the Drafts window, right‑click the script and select Merge From Server.
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.
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.
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:
Right-click the script in the Explorer window and select View Script History.
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 four minutes.
Reverting to Previous Versions
The owner of an experience can revert changes made by other editors. See here for instructions.
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.
You might also want to check Activity History. This view provides a chronological event log that improves team visibility into key experience settings.
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.
If the Live Collaborators window isn't already open, click on any of the collaborator icons to open it.
In the bottom-right corner of the window, click the ⋯ button and select Disable Team Create.
When prompted, confirm ending the session to reload the place in a non‑collaborative state.
