More specific permissions for actions that collaborators can do in Team Create

Currently, as a Roblox developer, it is difficult to manage permissions in Team Create because I can only give someone edit access or not. I’d like more specific permissions to manage my teams better. What I mean by more specific permissions is the ability for a user to perform a certain action. For example, modify scripts, create new objects, etc.

What kind of specific permissions?

When saying specific permissions, I’m talking about permissions which span to more than “is in team create/isn’t in team create”. At the moment, a player who is invited to a team create has full control over everything in the game. This could be a security risk for some programming organisations who employ external scripters/builders.

Imagine a Discord-server-style permissions system for Team Create. The owner of the game has full control over the permissions and can assign them to other members of the team create with high granularity. The developer could be restricted from editing certain locations or certain objects, or reading the contents of certain scripts.

What could this be used for?

Imagine a team of content creators have created a game which is fully underway for release. However, they need help from somebody who can help them achieve something in scripting they need. A scripter reaches out for work and they accept.

They invite this scripter to a team create. However, there is no way for them to restrict this scripter to just modifying scripts. It would be very helpful for them to be able to do this because the scripter only needs to modify the scripts. The scripter, generally, has no need at all to modify buildings or structure of the game. So, it would make sense to restrict him from doing this to prevent unauthorised or accidental changes to the structure of the game.

Summary

I think that the addition of permissions to Team Create would make it much more useful, since it would make the separation of roles within a development team very easy. I don’t have to give someone full edit access to my game to have them help out with development.

Minor Edit: A similar request to this was replied to by a staff member here: Script-less team create - #2 by Sorcus

33 Likes

As a Roblox developer, it is currently too hard to trust people that you don’t know in team-create because they have access to game saving and publishing. When I work with other people, it’s hard for me to decide if the person can be trusted or not, because someone stole a place from me already in the past, when I gave him access to team-create.
I think that a way to prevent such things from happening again is to let the owner of the place/game, control who can save and publish the place as their own. That way, developers don’t have to be very picky with the people that they choose to collaborate with, and easily see if the person had bad intentions (if the person doesn’t work and doesn’t have any experience as they claimed to have).

If Roblox is able to address this issue, it would improve my development experience because I can add friends and people to team-create, without having to worry much about them leaking/stealing private assets. And if I know they are not trusted after added, I know that they at least didn’t copy much (or everything) from my work.

Thank you for reading and have a great day :slightly_smiling_face:

7 Likes

Group owners are allowed to edit their game permissions to allow a group rank to have “No access” “Play” or “Edit” permissions but if a group rank is set to not allowed to have access (No Acess) to the places but has the “Create and Edit” permission on the website (As their group role permissions), those individuals are still permitted to open and edit places in which they shouldn’t have permission to join on studio to begin with.

As a Roblox Game Designer, many developers I’ve encountered worry about having their assets stolen by others that come in for short or long term positions.

If Roblox is able to address this issue, it would improve my development experience because developers would worry less about getting their assets stolen and would focus on the whole point of a project which is to create an enjoyable environment for the community.

7 Likes

This is still an extremely relevant feature request. If Roblox truly wants to continue to modernize and expand with large projects on the platform we need to have access to seamless collaboration between users. In order to achieve this, team create needs more specific permissions for which users can view and modify different parts of the game, most importantly to me, specific scripts.

Currently, it is extremely difficult to hire contractors, create collaborations, or receive help without going to great lengths. Although I can create separate places with only specific assets for this work, not only is this time consuming, but this makes transferring information very difficult.

Some examples of this critical problem occurring include:

  • Hiring a contractor to create a new backend system: This contractor needs access to specific scripts to create this system, by no means do they need access to all of them.
  • Hiring a terrain editor to create an environment: This person has no reason to be creating or modifying any scripts in the game.
  • Getting help from a friend on a bug: This friend only needs to see the scripts they are providing me help with, not my entire source code.

This isn’t a matter of only letting vetted users or trusted friends into Team Create. When it comes to games where source code is of top importance, like my game, Arcade Island, security must be taken with a trust no one approach. Developers can’t afford to risk their entire codebase being leaked to anyone. I, as others may relate, do not care who I am hiring, and will take the necessary measures to go out of my way to protect my work - there needs to be a better way to handle this.

12 Likes

is this still not done yet? i don’t want to give out my scripts to a part time builder

1 Like

This should for sure be a pretty high priority. Simply add passwords to scripts for now at least. We need artist permissions, audio permissions, scripting, animation etc.