Simple Survey includes three permission sets that should be assigned to users who need to view survey results or interact with the Survey Builder, depending on their specific roles.

Users who are the subject of the surveys, such as Case, Opportunity, or Campaign Owners, only require a Simple Survey license; they do not need a permission set.

Simple Survey Site Guest User: Assign this permission set to the Simple Survey Site Guest User (required as part of setup).

• Includes "Create" and "Read" access to the Survey object and all packaged fields.
• Should only be assigned to the Simple Survey Site Guest user, the dedicated user related to all interactions with the landing page and site.

Simple Survey Read-Only: Assign this permission set to end-users who need access to view survey results.

• Includes "Read" access to the Survey object and all packaged fields.
• Does not include access to survey questions (custom fields) created after installation.

Simple Survey Administrator: Assign this permission set to the System Administrator or additional users who will be configuring the application, creating and/or managing survey programs, and managing and/or analyzing survey data.

• Includes access to the Setup Wizard, Survey Builder, and Simple Survey Insights for reporting.

Notes:

To see the Survey Builder, the External Client App must be configured.

Users without the System Administrator profile need the following permissions for the builder to create the Survey Record Types, Page Layouts, and fields, and for updating profile field-level security for the newly created fields:

• Modify Metadata Through Metadata API Functions
• API Enabled
• Customize Application
• Manage Profiles and Permission Sets
• Customize Application
• Manage Certificates

The above permissions have the following prerequisites: Manage Custom Permissions, Manage Translation, View Setup and Configuration, View Roles and Hierarchy.

Please keep in mind that opening up these permissions to non-System Administrators allows them to bypass org-wide security, modify business logic, and potentially escalate their own privileges. To follow the Principle of Least Privilege (PoLP), ensure they are only assigned to users who truly require these permissions, and consider revoking them immediately after the users have performed the necessary configurations or updates.