LinkedIn
Copied!

Table of Contents

Building a client-based access control environment

If you have Pega marketing application in production that stores personal client data, you can configure an application that is used only for handling CBAC requests from clients. The client makes a CBAC request to the GDPR request management application, which communicates the request to the marketing application to retrieve or modify the personal data. The result of the request is passed back to the GDPR request management application and communicated to the client.

Client-based access control (CBAC) in Pega Platform involves the following elements:
  • A Pega GDPR request management application where client rights are displayed and the CBAC requests originate.
  • One or more Pega applications where the personal data is used and stored in a Pega database, and where client requests are enforced.

To build this environment, do the following tasks:

  1. Configure the GDPR request management application and supporting artifacts, such as the repository list and REST connectors.

  2. Configure the CBAC rules that identify where the personal data is stored in the Pega database.

    The Pega Infinity™ CRM applications come with CBAC rules for the standard personal data properties. If you define additional personal data properties in your version of the application, you must customize these rules.
  3. Configure the CBAC rules that identify where the personal data is stored in the Pega database.

  4. Apply optional configuration to the Pega application. For more information about this configuration, see the Related Content.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.