resource to the Roles tool, which allows the resource to be added to roles with specific privileges. When you assign a specific role to a user, then that user can use
SIF
requests to access the secure resources according to the privileges associated with that role. By default,
MDM Hub
designates a new resource, such as a base object, as secure.
Private
Hides the
MDM Hub
resource from the Roles tool. Prevents access of the resource from
SIF
requests.
A resource must be secure before external applications can use
SIF
requests to access an
MDM Hub
resource.
There are certain
MDM Hub
resources that you might not want to expose to external applications. For example, your
MDM Hub
implementation might have mappings or packages that are used only in batch jobs, and not in
SIF
requests, so these could remain private.
The
MDM Hub
does not consider package columns to be secure resources. Package columns inherit the secure status and privileges from the parent base object columns. If package columns are based on system table columns, you do not need to set up security for them, because they are accessible by default.