Request Forms

Request forms are reusable and detailed forms that dictate the details data stewards have about the requesters making access requests. Request forms can be attached to

• Data products: When attached to a data product, one request form is used for both data access requests and masking exception requests.

• Assets: When attached to assets, separate request forms can be designated for access requests and masking exception requests.

Request forms can be attached to multiple assets and data products. Request forms dictate the same access request process for any asset or data product that uses them, providing consistent and reliable information from the requesters to the data stewards making determinations.

Request form details

Request forms contain the following content:

• Form details: Details about the request form such as the name and request questions. Request questions are the questions a data consumer must answer, and the answers will be recorded in the access request for the data steward to review.

• Review flow: The review flow configures if the access request requires approval or not, the data stewards who will approve the requests, or the ability for data product owners to select their own data stewards.

  • Review flows can delegate to the data product or asset rather than being tied to the request form itself, if desired. However, tying data stewards to the request form itself allows them to edit the request form questions.

• Data use agreement: A data use agreement can optionally be included. If it is, the data consumer must acknowledge it before they can request access, ensuring they agree to how the data should be used.

• Linked data products: This is a list of all the data products that use this request form. Assets with this request form will not be listed.

Adding request forms to assets

Request forms are hierarchical, so for example, any attached to the schema will also be used for the tables within that schema. The governance user can also override the hierarchy and apply request forms to specific assets, like tables.

You should have your most restrictive request forms for databases and schemas. If your most restrictive request forms are at the table level, data consumers can easily bypass them by requesting access to the less-restrictive database or schema instead.

Similarly, review flows can be inherited through the hierarchy. However, the request form review flow always takes precedence. This means that if data stewards are assigned in the request forms, the review flows assigned or inherited through the asset hierarchy are Inactive.