Transformations > Access Policy transformation > Access Policy transformation configuration
  

Access Policy transformation configuration

When you configure an Access Policy transformation, you select a data asset that associates policies that you create on the Data Access Management page in Data Governance and Catalog with the source data set.
A data asset is a data structure such as a table in a database that you have cataloged in Data Governance and Catalog. You select the data asset when you configure the properties on the Access Policy tab.
Use a single Source transformation with an Access Policy transformation. Connect the Access Policy transformation directly to the Source transformation.
The following image shows where to place an Access Policy transformation and its configuration options:
The following table describes the fields on the Access Policy tab:
The Access Policy tab of the transformation. The tab properties include Consumer, Usage, Data Asset, and Consistency Seed fields.
Field
Description
Consumer
Identifies the user who will consume the data. Select a single user.
Active users in your organization with the Data Marketplace User role appear in this list. Select one of those users. Note that the user you choose helps determine the set of rules that the transformation applies to the data.
Usage
Identifies the usage context such as for customer analysis or anti-money laundering research. Usage context is one type of metadata that helps determine the set of rules that the transformation applies to the data.
Users create and manage usage contexts in Data Marketplace. To learn more, see Set Up Data Marketplace in the Data Marketplace help.
Data Asset
Identifies the data asset to which the transformation applies the rules.
A data asset is a data structure such as a table in a database that you have cataloged in Data Governance and Catalog.
By default, the source object that you selected when you configured the Source transformation appears when you click Select. Select the data asset in that source object.
If the data asset doesn’t automatically appear, select Override Asset Name and enter a name (or partial name) and click Refresh to view and select from the list of data assets. This is required if you select “Query” from the Source Type menu or if the connection or data asset in the catalog is different.
Consistency Seed
Provides a value that represents the rule logic that the transformation applies to the data element classification.
A consistency seed ensures that a rule's behavior for a data element classification will be consistent for the same consistency seed value, usage context, and user across mappings. For example, you can ensure that a rule always replaces the last name "Smith" with "Abcd."
If you want consistent tokenization between different Access Policy transformations, insert the same consistency seed in other Access Policy transformations. If you don't want consistent tokenization between different Access Policy transformations, generate a unique seed.
Click Synchronize Access Policy and save the mapping to ensure that all required design time properties are configured. This ensures that the appropriate data access policy rules resolve correctly when the mapping runs.
Note: Changes to data access policies take several minutes to take effect. This can impact environments when testing and validating policies when a change is required. To immediately apply changes to data access policies, follow the instructions in the Immediately apply changes to Data Access Management policies knowledge article.