Users & Permissions

The key permissions for enabling and configuring Data Processing Engine are in the Data Pipelines Base User permission set. This permission set is associated with a permission set license, of which only 3 are included as standard with NPC. Therefore, this permission set needs to be assigned judiciously.

If you are not using fundraising, just assign the Data Pipelines Base User permission set directly to the users who need it. (It is not included in any other standard permission set groups.)

If you are using fundraising, note that the Data Pipelines Base User permission set is included in the standard Fundraising Admin permission set group. Therefore, if you have multiple admins, you need to assign the permission set directly to only the users who need it, and create a custom permission set group that doesn’t include Data Pipelines Base User for other admins.

Users who only need to see the results of DPE calculations just need read access to the appropriate objects and fields.

Additional permission sets are needed if you are using the flexcards to display Program Management DPE results, or Fundraising Portfolios with Actionable Lists.

• Program management users need the OmniStudio User permission set if flexcards are in use.
  • Security and Permissions for Nonprofit Cloud
• Actionable Segmentation users need the Query for Data Pipelines User permission set.
  • Actionable Segmentation Basics
  • Assign Permission Sets for Actionable Segmentation

Relevant Users for Basic Setup

• System Administrator: needs the Data Pipeline Base User permission set assigned
• Integration User (assigned the Analytics Cloud Integration User profile): needs at least Read access to every object and field referenced in DPE definitions. Assign the object/field permissions directly to the Analytics Cloud Integration User profile - you do NOT need to assign a Fundraising Access permission set license to the Integration User.
• Writeback User: needs full CRED access to all objects and fields referenced in the definition
  • This is the user that the DPE uses to create and update records, and is specified in the Writeback nodes of the definition
  • Must have permissions to create/read/edit/delete
  • Note that the Writeback User defaults to the Default Workflow User (set in Process Automation Settings), but does not have to be the same user.