Responsibilities

A responsibility is the assignment of one or more users and/or user groups to a resource role for a resource.

Based on their responsibilities, users can act on the permissions conveyed to them via the resource role.

Child resources always inherit the responsibilities from their parent resources:

  • If the resource is a community, the responsibilities are inherited by subcommunities, domains and assets in the community. For example, if you are a Business Steward for a certain community, you are a Business Steward for all the subcommunities, domains and assets inside that community.
  • If the resource is a domain, the responsibilities are inherited by the assets in the domain.
  • If the resource is an asset, the responsibilities only apply to the asset itself, because assets never have children.
Example 

Suppose the following setup:

  • Anita Morrison is assigned the Community Manager resource role for a community called "Enterprise".
  • John Fisher is assigned the Business Steward resource role for a domain called "Critical Data Elements" in the "Enterprise" community.
  • Joanna Zhou is assigned the Owner resource role for a domain called "Critical Data Elements" in the "Enterprise" community.
  • William Parker is assigned the Owner resource role for an asset called "Customer Revenue" in the "Critical Data Elements" domain.

This leads to the following responsibilities:

Resource

Direct responsibilities

Inherited responsibilities
Enterprise community
  • Anita Morrison as Community Manager
  • None
Critical Data Elements domain
  • John Fisher as Business Steward
  • Joanna Zhou as Owner
  • Anita Morrison as Community Manager
Customer Revenue asset
  • William Parker as Owner
  • Anita Morrison as Community Manager
  • John Fisher as Business Steward
  • Joanna Zhou as Owner

Note You can view direct and inherited responsibilities of a resource in different places.