When installing the Prodly package, all profiles for which the package is installed will have the Prodly custom permissions assigned by default. The custom permissions provide additional Admin access to certain features. These types of Custom Permissions can be assigned within a Permission Set to a specific User or to an entire Salesforce Profile. If you only wish to grant User custom permissions, install the package for Admins only. If you wish to install the package for All users but do not want all users to have these permissions, you will have to unassigned the custom permissions from those profiles manually.
This table highlights the custom permissions and the Admin access they provide:
| Custom Permission Label | API Name | Description |
| Prodly Account Settings Manage | Prodly_Account_Settings_Manage | The Prodly Account Settings Manage custom permission is designed to allow only designated users to edit high-impact settings. This custom permission set is critical for ensuring that sensitive settings are only modified by authorized personnel. Non-admin users with the Prodly User permission set assigned, without this custom permission will have the Deployment section in settings tab hidden which will prevent them from modifying any deployment specific setting with high impact. Further more they will not be able to authenticate themselves any Integration systems. They will also not be able to remove any existing Version Control setup and will be limited to only be able to authenticate themselves to the existing Version Control Repository. |
| Prodly Control Instance Manage | Prodly_Control_Instance_Manage | The Prodly Control Instance Manage custom permission is designed to prevent non-admins from authenticating the control instance, which can lead to missing access in different areas and cause errors or problems during deployments. Non-admin users with the Prodly User permission set assigned, without this custom permission will not be able to reauthenticate the control instance if there is no valid control connection. Instead, they will see a custom screen indicating that the control is not authenticated and they do not have the relevant permission to do so. |
| Prodly Metadata Manage | Prodly_Metadata_Manage | The Prodly Metadata Manage custom permission is designed to allow only designated users to deploy metadata, given the strict compliance rules and regulations that govern this process. Non-admin users with the Prodly User permission set assigned, without this custom permission will not be able to view the metadata section and the creation/use of bundles in the Deploy page. |
| Prodly Next Gen Data Deploy | Prodly_Next_Gen_Data_Deploy | The Prodly Next Gen Data Deploy permission is designed to ensure that only designated users can using our new NextGen service in addition to the NextGen toggle in the settings tab. Any type of user regardless which on of the Prodly permission set have assigned, without this custom permission while the NextGen toggle in settings tab is ON will be limited to: – Deployments will not use the NextGen service and will perform deployments using the old Moover system; – Validation will perform a simulation using the old Moover system instead of having the New Full Data preview detailed results; – The Retry option for failed records in results will not be available; – In Compare page will not allow users to compare and/or save a bundle which includes also data; – In Deploy page will not allow users to deploy any bundle that includes data. |
Notes to be considered:
It is essential to note that the Prodly Next Gen Data Deploy permission is not encompassed within the Prodly Admin Permission set.
Additionally, the Prodly AppOps User permission set does not include any of the aforementioned custom permissions.