Limit Role Permissions on Assets to Specific Folders

Feature Requests
1

I have…

I’m submitting a…

  • Documentation issue or request

Current behavior

I’d like the ability to limit role permissions to Assets in particular folders.

For instance, suppose I have client XYZ and an asset folder at clients/XYZ. It would be great if I could have more granularity than asset read/write, such that I could allow that client to only read or write to their own directory.

Right now, we can broadly define scopes like assets.read and assets.create. Could it be possible to extend that syntax? Maybe add a new root scope to disambiguate, so something like:

asset-dir.client/ABC.read
asset-dir.client/XYZ.read
asset-dir.client/XYZ.write

# Wildcard support would be nice too
asset-dir.client/*.read

# And maybe follow some glob conventions around single wildcard vs. double wildcard
# such that a single matches a single directory, while double wildcards match any path length?
asset-dir.client/**.read

Ideally, these permissions would affect the asset API and the admin UI as well, so that users can only navigate to allowed folders.

Environment

App Name:

  • Cloud version

Version: [VERSION]
Cloud Version

2

No, it is not possible. But you can convert it to a feature request.

3

Thanks! I’ve converted it to a feature request.

1 Like
4

I am not sure if permissions work so well here, because folders can be moved and renamed. So only the folder ID would work. You probably just want to associate a folder with a role.