Administering a catalog

You can administer a catalog to control who has access to the catalog, the permissions of the catalog collaborators, and catalog settings.

Required permission To create a catalog, you must have this user permission:

• Manage catalogs

To administer an existing catalog, you must have the Admin role and one of these user permissions within the catalog:

• Manage catalogs
• Access catalogs

A catalog consists of the following components:

• A metadata repository that acts as an index for data and other assets.
• A list of collaborators who need to access the assets.
• An object storage instance to store assets that are copied into the catalog.

You can control the security of assets in a catalog by using the following roles, rules, or access types:

• Collaborator roles control what actions users can do in the catalog.
• Asset access can restrict an asset to a specific set of collaborators.
• Data protection rules can protect data assets from unauthorized access. Owners of data assets in governed catalogs have access to all data assets in the catalog while other users are subject to data protection rules.

As a catalog administrator, you can complete the following tasks:

• Create catalogs. You might create one comprehensive catalog or multiple catalogs for diverse purposes. For more information, see Creating a catalog.
• Add and manage collaborators. You can add collaborators to a catalog at any time. You assign roles to control which collaborators can add and use assets and which collaborators can view assets.
• Add assets to the catalog. You might be responsible for adding some assets, along with other collaborators.
• Manage custom properties and relationships for assets. For more information, see Custom properties and relationships for governance artifacts and catalog assets.

Watch this short video to see how to create and administer a catalog.

This video provides a visual method to learn the concepts and tasks in this documentation.