Permissions
Assign a Permission Set Group
Section titled “Assign a Permission Set Group”Assign one packaged group for each role:
| Role | Group in Setup | API name | Included permission sets |
|---|---|---|---|
| User | DQS User Access | DQS_User_Group | dqs_user |
| Administrator | DQS Administrator Access | DQS_Admin_Group | dqs_user + dqs_admin |
In Setup → Permission Set Groups, open the group, select Manage Assignments → Add Assignments, choose users, and complete the assignment. The administrator group already includes base access; assigning both groups is unnecessary.
Existing direct permission set assignments remain valid and are not migrated automatically. For legacy direct assignment, administrators need both dqs_user and dqs_admin; dqs_admin alone is not the complete administrator role.
What each role can do
Section titled “What each role can do”DQS User Access is not read-only. Users can create and edit draft definitions, configure capabilities and field overrides, import layout fields, run scans, and review results. The base permission set also grants create, read, edit, and delete access to the core DQS definition, result, schedule, and error-log objects. Application rules impose additional restrictions.
DQS Administrator Access adds administrator operations, including deletion of draft definitions and Field Usage setup, report generation, history, and PDF export. Active definitions cannot be deleted, even by a DQS administrator.
Data access and activation
Section titled “Data access and activation”Object and field permissions still apply to the Salesforce data being analyzed. DQS access does not guarantee access to every source object, field, or metadata component. Field Usage settings and saved reports require administrator access; they are not part of the base user role.
Assigning a group does not activate the package. Complete app activation separately after installation.