Metaproperty options allow you to set up permissions and restrictions for your assets, so that only certain users, user groups and/or permission profiles can see, edit, audit or delete the assets.
Do you have users contacting you saying that they cannot access, modify or remove an asset or would you like to have an overview of the permissions set up for a specific asset? With our Asset Permission Viewer you can get a quick overview allowing you to get the information you need to manage your portal and support your users.
By tagging your assets with metaproperty options you can set up restrictions on an asset level, so that only certain permission profiles, user groups or users can see, edit, audit or delete the assets. Read more about Asset Permissions here.
Whether you need an overview of the permissions for background information or you want to troubleshoot and support users, follow the steps below to the get the information you need.
-
Open the asset for which you want to view the asset permissions. Make sure you're in the Info tab of the Asset Detail View.
-
Open the Asset metaproperty permissions section in the Info tab and click the View asset permissions button, which will only show if asset permissions have been set up. If no permissions are configured the following message will be displayed: No asset permissions have been set.
All metaproperty options the asset is tagged with and for which permissions or restrictions have been set up will be listed in the Asset Permission Viewer. The options are indicated by the 
icon.
Below each metaproperty option the Asset Permission Viewer shows the permissions and/or restrictions that are in place and to which permission profiles, user groups and users they apply.
Note
The Asset Permission Viewer does not show hidden by default options for which no permissions have been set up.
Optionally, you can click the Edit button next to a metaproperty option to directly manage its permissions in Metaproperty Management
Let's take a look at the examples below to better understand the Asset Permission Viewer.
The first example asset is tagged with the North America metaproperty option, which is hidden by default. This means that by default no permission profile, user group or user can access the asset. Only the ones that have the necessary permissions to view, edit and/or audit the asset will be able to do so.
In this example the North America - Content Managers user group can view, edit and remove this asset as well as audit download requests of users trying to download this asset. Although less relevant for this specific asset, the Asset Permission Viewer also shows us that any other uploaded asset tagged with the North American metaproperty option will not be published to the Asset Bank until it has been audited. The North America - Content Managers user group has the permission to audit these specific upload requests.
For the same metaproperty option we can see that the North America - Designers user group is only allowed to view this asset.
All other users who are not in one of these two user groups will not be able to view the asset.
The second example asset is tagged with the United States and Photo option. By default all logged in users can view assets tagged with these options. However, as indicated in the Asset Permission Viewer the United States option is hidden for the EU Only user group.
The Photo metaproperty option can be viewed by all users except from users assigned to the Light Workflow User permission profile.
So users who are in the EU Only user group and/or assigned to the Light Workflow permission profile will not be able to view this asset.
Note
By default assets tagged with multiple permissions will not be visible to users who don't have all of the necessary permissions to view it.
It is possible though that your portal configuration allows users to view assets tagged with multiple options from the same hidden by default metaproperty even if they don't have access to each option. Read more about it here.
Contact your Customer Success Manager if you would like to double check which situation applies to your portal.
Comments
0 comments
Article is closed for comments.