Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Configuring Hierarchy and Network Relationships
  10. Creating Match Rule Sets
  11. Configuring Search
  12. Configuring Tasks
  13. Configuring Security and Data Filters for Business Entities
  14. Configuring the Content Security Policy
  15. Integrating Data as a Service
  16. Configuring External Calls
  17. Designing the Data Director User Interface
  18. Localizing Data Director
  19. Appendix A: Provisioning Tool Frequently Asked Questions

Field-level Data Filters

Field-level Data Filters

You can control access to records based on a value in a field. For example, for compliance with the General Data Protection Regulation (GDPR), you want only the EU data stewards to access records that have an address within the European Union.
You can create field filters on business entities. In a field filter, you define access permissions in terms of deny rules, allow rules, or a mix of both types of rules. A rule is made up of a value for the field and the applicable user roles. For example, you might create a field filter on a GDPR field. Create an allow rule on the field with the value of true and select the DataSteward-EU role. Use the Remaining Values rule to assign false to all other user roles.
The field filters on a business entity override the field filters on a reference entity. A user role might be allowed to see a subset of lookup values based on the field filter in the reference entity, but if a field filter on the business entity denies access to some of those values, the user role cannot see the records with those values.

0 COMMENTS

We’d like to hear from you!