Granular Permissions at Survey Level
Updated
With Granular Governance in Surveys, you get full control over who can access and manage different parts of each survey. Whether it's the Builder, Translations, Distribution, Analytics, Workflows, or Settings, you can assign specific permissions based on each team member’s role. This helps your team stay focused, keeps your workflows organized, strengthens data security, and ensures that every survey is managed with clarity and integrity.
Business Use Cases
Streamlined Collaboration Through Role-Based Permissions: Managing multiple stakeholders in survey creation can be challenging without clear boundaries. Granular governance allows teams to assign role-based permissions, such as view-only access for leadership, edit rights for core contributors, and restricted distribution access for designated owners. This structure improves ownership, reduces the risk of accidental changes, and ensures smoother collaboration on live surveys.
Empowering Regional Teams Without Losing Control: When overseeing surveys in different regions, it is essential to strike a balance between autonomy and consistency. Detailed permissions facilitate this by enabling regional teams to formulate and modify questions, while central teams maintain authority over design, publishing, and distribution. This approach allows for quicker localization of content without sacrificing brand standards.
Enhanced Security is achieved by allowing a Compliance Officer or Global Admin to assign precise permissions, ensuring users have access only to the areas they need. This minimizes the risk of unauthorized actions and promotes greater accountability across teams. With survey-level precision, a Survey Owner can grant permissions for individual surveys, allowing team members to engage only within their defined scope, thus protecting data and preventing work overlaps. For tailored collaboration, a CX Manager can provide edit access to contributors and view access to leadership, supporting multi-level stakeholder involvement while maintaining clarity and control. To ease operational burden, a Product Admin can utilize dynamic user groups and permission templates, enabling efficient management of large teams without constant manual updates. Finally, secure cross-functional workflows are supported as a Head of Digital Customer Experience can confidently assign task-specific access across regions or departments, enhancing turnaround time while maintaining critical safeguards.
Prerequisites
To assign or modify permissions for a survey: You need to be either the Owner of the survey or have been given "Can Edit" access for that particular survey.
Setting Up Granular Permissions
Navigate to CFM Persona App, go to the Programs Page, and then access a survey.
Click the Vertical Ellipsis (⋮) against the Survey and click Permissions.
Go to the Survey Permissions page, and under Set User Permissions, select User or User Group and select relevant permissions:
Can Edit
Can View
Custom
After clicking “Add User,” you can adjust the applicable permissions to limit access for a user or user group. These settings can also be modified later using the Settings icon next to the added users.
Click Save and manage permission changes as needed & update the Survey Details.
How to Use it?
You can use different permissions for different access based on below permission types:
Builder
Can View: It provides only Read-only access to the Builder tab.
Can Edit: It provides access to all edit actions within the Builder i.e. Edit/Add/Copy/Delete Questions, Add Logics, Clone Questions, Edit Pages, Edit Theme & Styling, AI+ Builder.
Translations
Can View: It provides access to view the translation done.
Can Edit: Can Edit will have sub permissions as per below:
Edit: It provides access to Add New Translation, Edit content of existing translations or delete a translation.
Mark All Complete: Update translation status.
Distribution
Can View: It provides view access to reports only (no creation/edits).
Can Edit: Can Edit will have sub permissions as per below:
Edit: Full access to manage distributions.
Delete: Remove distributions.
Response & Analytics
Can View: It allows user to View and filter responses & analytics.
Can Edit: Can Edit will have sub permissions as per below:
Edit: It provides access to Archive, Update Tag, Edit response Quality, Delete Response.
View Survey Dimension: It allows user to view the dimensions exposed through shared survey in filters, dashboards, Adding Widget Dimension & Metrics for custom dashboard.
Import: User with this permission will be able to import the responses.
Export: User with this permission will be able to export the responses.
Note: When a user is granted “Can View” permission, they also gain access to the Analytics Feed and can view data in any shared custom dashboard that uses those survey dimensions within its widgets.
Automations
Can View: User will be able to view
Can Edit: Can Edit will have sub permissions as per below:
Edit: It provides user with all edit access (excluding Delete & Deploy) to workflow & Case Rule.
Delete: It provides user with delete access to workflow & Case Rule.
Activate Case Rules: It provides user with the access to activate the case rules.
Activate Workflow: It provides user with the access to activate the workflow.
Settings
Can View: It provides you with the access to view Settings page and corresponding Record Managers/ Setting but will not allow to edit.
Can Edit: Can Edit will have sub permissions as per below:
Edit Response: It provides you with ability to edit Allow Completing Survey Later, Quota Setup, Quarantine Rule Setup, Link Hierarchy to Response Field, Case Properties Widget.
Edit Survey Custom Field: It provides you with ability to edit Transaction Fields, Response Custom Fields
Edit Masking: It provides you with ability to edit the masking settings for a survey.
Publishing
Publish: It allows you to publish the survey.
Can not Publish: It restricts you to publish the survey.
Note: Only users with Can Edit access can modify permissions or clone or delete surveys.
To ensure permissions are configured correctly, start by assigning a permission set to a user or group. Then, log in as that user to validate that their access is appropriately limited. Attempt restricted actions to confirm that access is denied where expected. Additionally, test different role combinations to ensure the user interface behaves as intended and reflects the correct access levels.
Best Practices
Define role hierarchies clearly.
Leverage dynamic user groups for efficiency.
Regularly review permissions for security hygiene.