copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2022-02-18 |
catalog, restrict visibility, hide object, restrict by user, filter catalog, private catalog, catalog management service, public catalog |
account |
{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:tip: .tip} {:note: .note} {:important: .important} {:external: target="_blank" .external}
{: #restrict-by-user-object}
Private catalogs provide a way to centrally manage access to objects in your own catalogs. You can customize your private catalogs to make specific solutions available to users in your account. By doing so, you can ensure that your catalogs are relevant to your business. {: shortdesc}
Let's say you're an operations admin for your team, and you want your team to use only approved networks. You can create one catalog that includes all of the private virtual private endpoints for use by users in your account. Team members with viewer access can access only the virtual private endpoints in that catalog.
All private catalogs that are in an account inherit filters that are set by the account owner or administrator at the account level. In addition, if the account is a parent account in an {{site.data.keyword.cloud_notm}} enterprise, the filters apply to all child account groups and accounts. {: tip}
{: #prereq-restrict-object}
You need the administrator role on the catalog management service to complete this task.
{: #catalog-all-object}
Complete the following steps to create a catalog for your objects:
- Go to Manage > Catalogs, in the {{site.data.keyword.cloud_notm}} console, and click Create a catalog.
- Select the Virtual Private Endpoint catalog type.
- Enter a name and description.
- Click Create.
{: #customcatalog-access-object}
To authorize users to work with the objects in your private catalogs, assign them the viewer role on the catalog management service.