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
To collaborate with others, you first need to add collaborators to your experience. You can then edit their permission settings which correspond to their level of access to the experience.
Adding Collaborators
When you're ready to collaborate on an experience, click the Collaborate button in the upper-right corner of Studio:
In order to manage collaborators, the place must be saved to Roblox. If not saved to Roblox, a Save to Roblox button is shown in the dialog. Click this button, save your place to Roblox, and then click the Collaborate button to return to the Manage Collaborators dialog.
Type into the search bar at the top to search for a collaborator to add. A dropdown will appear listing any collaborators that match your entry. Select the collaborator to add them and click Save for your collaboration settings to take effect.
In user-owned experiences, the search bar shows both users and groups to add as a collaborator. If a user is your friend, you see a friend icon to the right of their username. In group-owned experiences, you can only add users, not groups, as collaborators.
Adding collaborators to your place automatically turns on Team Create.
Editing Permissions
Collaborators you add to an experience have permission settings that correspond to their level of access to the experience. Here's a complete list of the different permission settings a user can have and a description of the permissions they have:
| 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 user-owned experiences vs. group-owned experiences.
User-Owned Experiences
For user-owned experiences you can grant Play access to any user or group, but you can only grant Edit access to users that are friends with you. To give Edit permissions to individual collaborators for an experience that you own:
With the experience open in Studio, click the Collaborate button in the upper right corner of Studio.
Select Edit from the permissions dropdown for the individual.
Group-Owned Experiences
For group-owned experiences, only the owner of the group can manage which roles have Edit permissions. You can add individual collaborators to group-owned experiences, however they can only have Play access, not Edit access. There are two ways a group role can have Edit access: changing the permissions for all group experiences, and changing the role for a specific group experience.
All Group Experiences
To manage which roles in a group have editing permissions for all group experiences:
Navigate to the Groups page and select the group.
Click the … button in the upper-right corner and select Configure Group.
In the left column, select the Roles tab.
For each group role that you want to give editing permissions to, enable Create and edit group experiences.
In the Manage Collaborators dialog, these roles display Edit access but are grayed out to indicate that you can't change the access level from Studio.
Specific Group Experiences
Group owners can grant Edit access to specific experiences to roles without the Create and edit group experiences permission enabled. With a group-owned experience open, click on the Collaborate button. Then select the role, which is No Access by default, and set the access level to Edit. All users within this role should now have Edit access for this experience only; this won't grant them access to other group experiences.
Users outside of a group can't have Edit access to the group's experiences, but you can grant them Play access.
Accessing a Session
Those who have permission to edit an experience can join a Team Create session as follows:
Close all currently open places in Studio, or restart Studio.
Select the Shared With Me tab for user-owned experiences, or the Group Games tab if it's a group-owned experience.
Click the desired tile to begin editing.
Collaborative Building
All collaborators can manipulate objects, and the changes automatically appear for other collaborators.
User Color
Each collaborator in a session has a color behind their avatar in the Team Create window.
When a collaborator selects an object, a selection box in their color appears around the object in the 3D view. The Explorer window also indicates when a collaborator selects an object.
Undo and Redo
If multiple creators have made edits to a part or instance, pressing Undo for that object reverts it to the state before you made a change and revert all changes that other editors might have made following your latest edit.
Collaborative Scripting
If Team Create is on, Roblox stores scripts in a central cloud-based repository that all collaborators can access. This allows creators to:
- Independently work on the same script that others are editing.
- Know when others are working on a script.
- Test changes locally before committing them to the cloud.
- Compare and commit script changes to the cloud when ready.
Collaborative scripting is disabled by default. To enable it, select Game Settings → Options and turn on Enable Collaborative Editing. Note that you'll also need to disable Team Create and then reenable it to restart the session.
Drafting Scripts
You can edit scripts while collaborators edit them and playtest scripts locally without affecting the experience for others. After you finish drafting a script, you can commit it to the cloud and Team Test the cloud version with collaborators.
When editing 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.
Comparing Local and Cloud Scripts
To compare a local draft of a script with the version saved to the cloud:
Right-click the local draft.
Select Compare with server to open the Diff Result window.
Compare the line numbers to help determine which to keep. Code that collaborators changed or deleted appears in red. Code that you updated appears in green.
Committing Scripts to the Cloud
To commit your local edits to the cloud:
Left-click a script, or hold Shift and left-click to select multiple scripts.
Click Commit to commit all selected scripts to the cloud.
Merging Changes
If a collaborator commits to the same script that you're editing, an icon with a green ⊕ symbol appears in the Drafts window.
To merge their changes into your script:
Identify which scripts you need to merge.
Left-click a script, or hold Shift and left-click to select multiple scripts.
Right-click any selected script.
Click Merge from server to open the Merge Tools window. This window shows you how the latest edits relate to your own. If there are conflicting changes, you can pick which code to keep, or make manual edits.
- Select Draft to keep your changes or leave it unchecked to discard them.
- Select Server to merge the changes into your draft or leave it unchecked to ignore them.
- Select Other to manually edit the script and save the changes to your draft.
Once you check the desired options, toggle the Preview Resolution switch to preview how the script will look.
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 deleted scripts:
- Left-click a script, or hold Shift and left-click to select multiple scripts.
- Right-click any selected script.
- Click Restore Script. Scripts restore to the place's Workspace and you may need to manually re-parent them back to their original location.
Chatting with Collaborators
To chat with collaborators:
In the View tab, click Chat.
Click on the text box and type your message.
Press Enter to send the message.
Saving and Publishing
If Team Create is on, 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. Additionally, the status bar at the bottom of the Studio window shows when a save is in progress and when it's done.
Changes made between auto-saves aren't published, so updating a live game still requires explicit publishing via Publish to Roblox.
Reverting to Previous Versions
The owners of an experience can revert changes made by other editors.
Navigate to the experience's main page on the Roblox website.
Click the … button to the right of the experience title and select Configure this Place.
On the target page, click Version History in the left column.
Choose an earlier version and click Revert to this version to roll back.
Be careful when reverting changes in this way. If anyone is currently editing a game with Team Create, their session could still auto-save and overwrite the revert action. To ensure that nobody else is editing the game when you revert the changes, disable Team Create.
Team Create
Team Create is the Studio feature that enables collaboration for your place. Teams of all sizes, including solo creators, can benefit from features such as script version control and place autosaving by enabling collaboration. Workflows that involve the Manage Collaborators dialog will automatically enable Team Create for you when necessary so the collaborative experience is seamless. However, you can still manually enable or disable Team Create if necessary.
Enabling Team Create
Owners of an experience can enable Team Create. There are two ways to enable Team Create manually:
Toggle Team Create on when you save or publish to Roblox for the first time.
Open the Team Create widget in the View tab and click the Turn On button.
If you haven't saved or published the place to Roblox, the Turn On button appears as Save to Roblox. When you click the button, the Save Game dialog opens, and you can enable Team Create as shown in the first method.
Disabling Team Create
Owners of an experience can disable Team Create. When disabled, Studio forces all other collaborators to exit the session.
To disable Team Create:
At the bottom of the Team Create window, click the … button.
Select Disable Team Create.
When prompted, click Yes to end the session.
