This page will walk you through the steps to install Prodly in your Salesforce org. Follow the instructions below to get set up quickly and start managing your deployments with ease.
To install and configure the Release managed package for the very first time:
For org-to-org deployments, Prodly recommends installing in the org where you intend to build data sets and initiate deployments (typically your production org). For Release version control deployment, you must install the Prodly Release managed package in the Salesforce org where your source of truth data resides. You can install in multiple orgs; however, you can only place an org under version control from one managed package installation.
Prodly Release is available on the Salesforce AppExchange. To install Release into your Salesforce instance:
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Due to the admin-focused nature of the app, that is, the level of access and potential for mass data modification that the app provides, Prodly strongly recommends providing access only to administrator profiles.
</aside>
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: