What is the minimum role required for creating a policy acknowledgement campaign?

What is the minimum role required for creating a policy acknowledgement campaign?

• A. sn_compliance.user
• B. sn_compliance.manager
• C. sn_compliance.admin
• D. sn_risk.user

Answer: (A)

Creating a policy acknowledgement campaign relies on having access to the policy management features, not on broader risk or admin capabilities. The basic compliance user role provides the necessary permissions to work with policy-related records, including creating and configuring campaigns. This aligns with the idea of least privilege: you give only what’s needed to perform the task. Roles beyond the basic compliance user, such as a compliance manager or a full admin, grant additional capabilities (like approvals, governance-wide changes, or system-wide configuration). While those roles can do more, they’re not required to create a campaign and aren’t the minimal set needed. A risk-focused user role doesn’t include the policy-management scope needed to create campaigns, which is why it isn’t sufficient for this task.

Creating a policy acknowledgement campaign relies on having access to the policy management features, not on broader risk or admin capabilities. The basic compliance user role provides the necessary permissions to work with policy-related records, including creating and configuring campaigns. This aligns with the idea of least privilege: you give only what’s needed to perform the task.

Roles beyond the basic compliance user, such as a compliance manager or a full admin, grant additional capabilities (like approvals, governance-wide changes, or system-wide configuration). While those roles can do more, they’re not required to create a campaign and aren’t the minimal set needed.

A risk-focused user role doesn’t include the policy-management scope needed to create campaigns, which is why it isn’t sufficient for this task.