Asset Libraries
An asset library is a container for a collection of assets and their versions in a Model Manager database. When the database is created, a first asset library — Asset library 1 — is automatically added for you. You would typically add more libraries to the database if you want to restrict access to a collection of assets for a particular set of Users and Groups. By granting permissions on the asset library, you can, for example, restrict who is able to browse and search the assets in the library.
The Asset Libraries page, opened by clicking Asset Libraries in the Database navigation sidebar, shows a table with all asset libraries in the database. Click on the name of an asset library in the table to show more details for that asset library.
Click the Add button to add a new asset library. Write a name for the new asset library in the Name field. Click Save.
The Asset Library Page
The Asset Library page contains details on an asset library in the database. Click Rename to change the name of the asset library. Click Delete to delete the asset library in the database. The deletion is not permanent — you can restore the deleted asset library by clicking Restore.
Click Owner to transfer ownership of the asset library to another user. Only the current owner or a root administrator can transfer ownership of the asset library. The user that creates the asset library is automatically set as its initial owner.
See Owners in the Model Manager Reference Manual.
Click Permissions to grant permissions for the asset library to users or groups. Only the current owner or a root administrator can grant permissions for the asset library. See Table 3-2 for the permissions available for an asset library.
Table 3-2: All available permissions for asset libraries.
See Granting Permissions in the Model Manager Reference Manual.
When the Model Manager authorizes a database action that targets an asset in the asset management system, it consults up to two levels of protection: the asset library that the asset belongs to and, possibly, the asset itself. See Table 4-1 for all available permissions for assets.
The necessary permission combinations for possible database actions targeting assets are summarized as follows:
Table 3-3: Necessary permission combinations for performing possible database actions that target assets in an asset library.