Expanded Sharing for Assets

Hi Creators,

Last year, we expanded the permissions system to let you share audio and video assets with groups. Today, we’re enabling sharing of images, decals, meshes, mesh parts, and models with friends and groups. We’re also expanding package sharing to enable sharing with groups. Finally, we’re enhancing the auto-sharing functionality to help reduce future asset insert permission errors for your collaborators.

Expanded Sharing

To better facilitate collaboration, you can now share your images, decals, meshes, mesh parts, and models with your friends and groups. This includes assets uploaded to your individual account or to any of your groups. To share a group asset, you must have “Manage development item permissions” permission on Creator Hub Group permissions or “Create and edit community experiences“ permission on Roblox.com Community permissions. Previously, there was no way to directly share these assets.

You can share your assets and manage their permissions in Creator Hub, the same way you can currently share audio and video assets.

We are also expanding package sharing. You can now share any packages that you or any of your groups have uploaded with your friends or other groups. Previously, you could only share packages uploaded to your individual account with your friends.

You can share your packages and manage their permissions in Creator Hub or in Studio.

You can easily find assets that are shared with you or your groups in the revamped Asset Manager (Beta). You can select the account on the left menu, and set the “Source” filter to “Shared With Me”.

As an alternative, you can also find the shared assets in Toolbox under “Inventory”.

Reducing Permission Errors

To help reduce permissions errors with your collaborators, when you insert one of your restricted (private) assets into one of your collaborators’ experiences, that private asset will automatically be shared with your collaborator’s account. This is in addition to existing functionality, which automatically shares the asset with the experience. This helps to reduce future permission errors for your collaborator, since they’ll have access to the asset in their account. You can always manage your collaborators’ access in Creator Hub. Revoking access to your collaborators removes the asset from their inventory, however any experience or model they created that is using the asset will continue to have access.

Additionally, when a restricted (private) asset is shared with a group, members of the group that can edit group experiences can also insert that asset in experiences that don’t belong to the group. We are actively working on the permission system, and would love your feedback on how to further improve the system, including adding additional group controls for managing and using assets.

Known Issue

If a package is shared with a group, the permissions can only be set to “use”. Setting the permission to “edit” will result in an error. We are working to fix the issue.

Future Improvements

This is the first of three launches for asset privacy and permissions over the next few weeks. The next two launches will further improve sharing and distribution of models and packages, and provide the ability to opt-in to privacy for images, decals, and meshes. We’ll share more soon.

Additionally, we know animations workflows are restrictive, especially when collaborating and reusing animations across accounts. The foundation we are building with the upcoming launches will enable us to reduce the friction of using animations with your collaborators. Stay tuned for more details later this year!

To further help facilitate collaboration, we will add permission pages in Studio to support sharing of images, decals, meshes, mesh parts and models assets. We will also enable bulk sharing of multiple assets using the newly revamped Asset Manager (Beta).

As always, let us know if you have any feedback — thank you!

98 Likes

This topic was automatically opened after 10 minutes.

Thanks for the update! Im still waiting for restricting permission for the translator portal

I hope this would get added soon

11 Likes

While this is a good update, we are still unable to revoke permissions once granted for assets in use in an experience, can this please be fixed?

7 Likes

Very nice! Does this mean that this will eventually streamline the process of changing the ownership of a game from player > group or group > group if it has a lot of assets like animations and sounds?

2 Likes

I know a lot of ppl will be happy with this update really cool W roblox

4 Likes

Will this do anything for this bug report since January: New permission system is broken?

We don’t want to give people access to edit our experiences, we just want them to be able to upload to the group and use the group’s assets - the current “asset permissions” in Creator Roles has not worked for this purpose.

6 Likes

So does this mean that if all of the MeshParts in a game are whitelisted to specific Groups, then a stolen copy of that game would open up into an empty baseplate under someone else? Or are the MeshIDs restricted separately? If we make our games entirely out of meshes and only share them with our team members, we would never worry about asset theft again.

4 Likes

Also this too, its a GIGANTIC problem with this system.

the odds, I made a ‘bug report’ related to this just 3 hours ago :sob:

THANK YOU SO MUCH!!!

2 Likes

Thanks this is a really useful change! Can’t wait for the rest of the launches.

So long as privacy is truly opt-in and we don’t have a repeat of the audio privacy update for other asset types, these changes sound solid to me!

3 Likes

Will that mean that from now on, if someone’s game uses f.e. a decal that was published by someone else, then that decal won’t be visible anymore unless they contact the original uploader and get whitelisted? That doesn’t seem optimal, as many games, including mine, use decals and meshes that other users uploaded (no point wasting time and uploading the same mesh/decal myself if it’s already on the platform).
I hope this update doesn’t work the same way the audio privacy one did.

1 Like

Great change,

Along with An Update on Automated Action Against Modified Clients it may almost completely stop any asset theft for good. Those types of assets when private are already inaccessible from the browser level most likely to prevent any sort of third party AI training. This is going the right direction for us creators.

1 Like

I’ll be definitely waiting for this, can’t comprehend how much I’ve encountered this problem when the game is owned by a user account rather than a group.
I am probably missing the point of this post, but this is at least in the scope so im glad this is being addressed.

1 Like

No way, the feature I asked for got added!!!
But…I’m guessing you still can’t upload public music for everyone to use…

I’ve added my alt to one of my meshes.
In theory this user should be able to use my mesh in experiences right?
What happens if someone else tries to use the same mesh? will it render invisible to that user? or will they still be able to use it?

What is the purpose of this update? allowing users to use “shared” assets from the toolbox?
Is that the only purpose for it?

I think this is a very welcome update and all, but I hope in the future, we’ll be able to not allow other users to spawn our meshes in studio and download/steal them. I’m aware that Roblox can’t fully prevent stealing, since all assets are cached into a user’s device so they can load, but I’m expecting Roblox to do their best to prevent stealing, and make the job harder for the bad actors.

1 Like

I thought this was it. I thought we’d be able to put animations up for sale. I was wrong.

1 Like

Quite disappointing to see animations are still not part of privacy sharing… they’re probably the most important asset type that currently has no sharing support.

3 Likes

Please allow us to use InsertService:LoadAsset() on assets that gave our game permission to use. This update could be very powerful and could simplify user-generated content workflows if this were to work.

6 Likes