Governance
Updated
Governance in Customer Feedback Management offers granular control over user permissions across various functional levels, allowing access to be granted based on specific roles and responsibilities. It enhances security and operational efficiency by supporting permissions at the Survey, Program, and App levels, each with configurable actions that can be enabled or restricted. This framework ensures clear accountability and simplifies the management of user access throughout the platform.

The Roles are divided into 3 main categories:
Survey Level: These permissions control access and actions related to surveys.
View Translation: Allows you to view translations in the survey.
Edit Translation: Allows you to create or modify translations.
View Distribution: Provides access to view survey distribution details.
Edit Distribution: Allows you to set up or edit survey distribution.
View Response & Analytics: Grants access to view survey responses and analytics reports.
Edit Response & Analytics: Allows you to configure or modify analytics and response settings.
View Automation: Provides access to view workflows and case rules.
Edit Automation: Allows you to create and edit workflows, case rules, and associated actions.
Delete Automation: Grants permission to delete workflows and case rules.
Edit Settings: Allows you to update survey settings.
Publish: Grants the ability to publish the survey along with any modifications made.
Program Level: This set of permissions gives you access to Programs and Subprograms.
View: Allows you to access Program and Sub-Program pages and view the Survey screen. Users cannot edit or add actions.
Note:
For existing surveys, users with Program Level > View access are restricted by Survey Level permissions.
Users can see the Program page but cannot edit survey details or permissions.
Edit: This permission gives you ability to:
Modify Programs and Sub-Programs.
View all activities related to the Program.
Add new surveys and create surveys (through button access on the Record Manager).
Edit surveys they have been created using the Builder.
Note:
Editing survey details or permissions requires Platform Level > Edit Program permission.
Builder access, granted through this permission, allows you to edit surveys at the Survey Level (“Can Edit”).
Cloning a survey is tied to the ability to add a survey. This action is only available if you have Platform Level > Edit Program permission. Without it, cloning is disabled.
Delete: This permission gives you access to delete access to Programs. You’ll be able to delete both shared and created Programs/Subprograms, in addition to all the capabilities included in the View permission.
Note: Deleting a survey is only allowed if the user has Platform Level > Delete permission. Without this, deletion is not permitted.
App Level: This permission controls the visibility of the feature within the CFM App.
View Creatives: Allows you to view access to creatives.
Edit Creatives: Grants permission to edit creatives.
View Hierarchy: Allows you to view hierarchy.
Edit Hierarchy: Grants permission to edit hierarchy.
View Survey Fields: Allows you to view transaction fields and response custom fields.
Edit Survey Fields: Grants permission to edit transaction fields and response custom fields.
For Custom Fields:
If field visibility is set to a project, you must have Edit Survey Custom Field (granular permission) + Edit Survey Field at the Platform Level.
If scoped to a program, you must have Edit Survey Field at the Platform Level.
If visible in all programs, you must have Edit Survey Field at the Platform Level.
View Transactions: Allows you to view transactions.
Edit Transactions: Grants permission to edit transactions and perform all associated edit actions.
View Profile Samples: Allows you to view profile samples.
Edit Profile Samples: Grants permission to edit profile samples and perform all associated edit actions.
Survey Masking:
View: You can view existing masking templates.
Create: You can create new masking templates.
Edit: You can edit templates that you’ve created or that have been shared with you with editing access.
Delete: You can delete templates you’ve created or those shared with you with edit permissions.

Business Problems Solved
Role-Based Access Control: Effective use of role-based access controls in the Governance Module helps organizations maintain accountability and operational efficiency. By assigning team members permissions specific to their areas of responsibility, teams can focus on their tasks without access to unrelated programs, reducing inefficiencies and minimizing the risk of data misuse. This targeted permission management leads to streamlined workflows and enhanced accountability across the organization.
With the Governance Module, you can enhance security by assigning precise permissions that limit user access to only the areas they need, reducing the risk of unauthorized actions and increasing accountability. At the same time, you can streamline workflows by aligning access with roles and responsibilities, helping your team avoid confusion and boost productivity for better project outcomes.
Prerequisities
To access the governance your role shall have following permission:

Accessing Roles and Permissions
Go to Universal Search and search for All Settings.
Alternatively, go to All Settings can be found under the Settings section within the Platform module.

Navigate to User Management and select either Workspace Roles or Global Roles.

Go to + Create Role.

Navigate to the Create New Role page and fill in the details:

Name: Enter a meaningful name to the role.
Description: Enter a meaningful description to the role.
Users and User groups: Select the users or user groups where you would want to add this particular role.
Role Permissions: Navigate to CFM App section, and under the CFM App sections select the type of role you would want to create.
Note:
To validate your Governance setup and ensure that permissions are correctly configured, start by creating a test role (e.g., Test Survey Analyst) and assign it to a dummy or test user. Grant the role specific permissions at the Survey, Program, and App levels. Then, log in as the test user and attempt to perform actions based on the permissions assigned. For example, if only “View” access is granted, verify that the user cannot edit or publish content. If “Edit” is enabled, ensure the user can create or update items as expected. For “Delete” permissions, confirm that deletion works only when appropriate platform-level permissions are also in place.
Best Practices
Always establish roles based on the principle of least privilege. Begin with the minimum necessary access and only increase it when business requirements dictate.
Use user groups instead of assigning roles individually. This ensures easier scaling, auditing, and management as teams grow.
Clearly separate roles for administrators, managers, and viewers to avoid overlap and confusion in accountability.
Regularly assess role assignments to confirm that users still require the permissions they have been given.