Protecting set-up of asset listings

Squiz Matrix Support
1

We are using asset listings a lot (we now have hundreds of them).


In some cases we want people to be able to add a sub-asset to an asset listing and be able to publish it. The users therefore need administrative access to the asset listing (is this right?). However, we don't want these back-end users to be able to fiddle with the set up of the asset listing itself (e.g. change types of assets listed, number of assets listed, sort order), or the default format.



Is there some way to set up the asset listing permissions so that people can't change the asset listing set up, but can still publish sub-assets? I've looked into pointing the asset listing to a folder, or similar, but it just confuses people unless we do that for all our asset listings (which is a solution I'm not interested in).

2

You only need Write access to create a child asset, not Admin access, however, the child inherits the same permission as the parent, so the user won't get Admin access to the child either.


In v3.6 you can use Triggers to automatically set additional permissions on create – I'm not sure what the solution would be in v3.4.

3

My understanding is that Write access only lets you create the asset… you can't change the status of the asset with only this level of access. Is that right?

4

That's right – which is the problem in the current v3.4 version. I'm not sure there is a way to do what you want (i.e. lock users out of the asset listing settings, while still allowing them to create child assets that they can change status on).

5

You'd need another folder or something:

    Asset Listing
    `- Folder
      |- Page 1
      `- Page 2


and point your asset listing at "Folder" and give users admin access to the Folder but not "Asset Listing"

Stuffs up your menus though if you are using them for that.
6

It not only stuffs up menus, but breadcrumbs too.


I'd considered the folder option, but it would mean going through and adding a folder to hundreds of asset listings so they all work in a consistent way, moving hundreds and hundreds of assets, and retraining people on where to put their stuff.



Do you think the developments in 3.6 will offer a solution?

7

Thee triggering system would allow admin access to be granted to the assets as they are created without having to rely on casacading permissions. You'd have to have your users in the same group and create trigger that says something like:


Any standard page created under this site should have admin access granted for User Group #123 when created.



What you cant do yet is add the additional condition that would say "Any standard page created directly under any asset listing".