Click's CRM includes:
- Click's CRM
- Click Sales Engagement (SE)
- Click Marketing Automation (MA).
These three components are installed together via a single Click's CRM package installer. There are also some configuration steps that the installation admin will need to complete within their environment following the installation
In this article, the individual in the organization handing the installation and setup is referred to as the "Installation Admin".
NOTE: If you are performing an UPDATE to an existing CRM installation, you ONLY need to do Step 1.
NOTE: Please disable all ad-blockers prior to completing installation and configuration. Ad-blockers can interrupt configuration from completing successfully.
NOTE: A user with permissions of global administrator of Office 365 with access mode = read-write AND a Power Apps Premium or Power Automate Premium license is required. Global administrator of Office 365 with access mode = administrative rights will not be sufficient.
Prerequisites: Gather & Submit Registration Info
In order to provide the information required to install and configure Click's CRM, Click needs the following info from the installation admin:
- Preferred data center region.
- Power Platform environment URL where Click's CRM solution will be installed. This must be a new Power Platform environment without Dynamics.
- Unique organization name.
- Application ID (Client ID).
- Client Secret.
If you have not yet done this, please see our Registration article for details.
NOTE: CDX environments are not supported. Please see Microsoft's CDX Terms of Use. CDX Environments that have Click's CRM installed will run into issues sending emails, as these emails will be marked as spam.
Click Generates and Provides Setup Materials to the Installation Admin
Once the installation admin has submitted the registration materials, the following information will be included in the Click Solution File email and will be needed for future steps in this guide:
- A download link to the Package Installer containing the CRM, Sales Engagement, and Marketing Automation solution files.
- Account Key
- Token
- License Key
- Instructions for next steps
NOTE: The email will come from system@CLICKDIMENSIONS.onmicrosoft.com and will be sent to the email used during registration. If you do not receive it, please check your spam and junk folders.
Step 1: Installation Admin Runs the CRM Installation Package:
Use 7zip or WinRAR to export the Package Deployment zip file provided by Click and run the included PackageDeployer.exe file. (If you do not use 7zip, you may encounter an error when running the PackageDeployer.exe file.)
If you are using the Windows File extractor (not recommended) before you run the program you have to right-click on properties, and then ensure that you have unblock the Security option that blocks files from executing. It may look like one of the two options below.
Be sure to check the checkboxes for Display list of available organization and Show Advanced.
- Choose the correct organization from the list, then click Login to begin the installation. This will import a series of solution files and records into the environment, and may take 30min - 1hr to complete.
- Click Next on the "Welcome to Click's CRM" Installer screen.
- On the ‘Ready to Install’ screen, please verify that the intended target Power Platform environment is displayed and click the Next button.
- After the "Reading Click CRM Installer Configuration" page completes the pre-validation checks of the included solutions, click the Next button.
- The Installer will now install the CRM solution into the selected environment. This action can take 30+ minutes to complete the import process, and you can allow the installer to run in the background while routinely checking its progress.
- At the end of the installation, when the installer is processing post-import data steps, the user will be promoted to insert the Account Key. This information can be found in the welcome email. The user will enter the account key and click Submit.
- Once the account key has been submitted, the installer will process the information and pop open a Success and Welcome screen which can be closed.
NOTE: During this process, if you see any red code errors, icons or messages indicating that the import process failed, please click on the download log file link and save the log file. This log file may be requested by Click to troubleshoot the installation process.
Step 2: Installation Admin Configures Environment
To complete the initial environment configuration, the installation admin must navigate to App Settings > Configuration, open the existing Configuration record, and click the "Run Setup" button.
This will open a window where you will be asked to provide your Power Platform environment URL (the same one you provided when registering).
When you provide your environment URL and click "Connect", it will establish and validate your environment's connection to Dataverse, Outlook, and Users.
It will then ask you to check a box agreeing that Click can update the solution configuration in your Power Platform environment. Check the box and click "Continue."
You will then be taken to a "Setup Complete!" screen, with a button to take you back to CRM.
Step 3: Installation Admin Verifies 'CRM Logic' Solution Cloud Flows
Next, the system admin will navigate to the CRM Logic solution to verify that all of its Power Automate Cloud Flows are turned on and assigned to a user with a Power Apps Premium or Power Automate Premium license.
To do this, navigate to Advanced Settings > Solutions > Managed Solutions > CRM Logic > Cloud Flows.
If the installation admin that ran the installer themselves has one of these licenses, the CRM Logic Cloud Flows should already be on and assigned. In this case, there is nothing to do besides verify that they are correctly assigned and enabled, as shown above. (Note that the above screenshot shows only a subset of the CRM Logic cloud flows - you must ensure that every cloud flow within the CRM Logic solution is 'On' and assigned to a User with a Power Apps Premium or Power Automate Premium license.)
If the installation admin that ran the installer did not have a Power Apps Premium or Power Automate Premium license at the time the installer was run, the CRM Logic solution's Cloud Flows will need to be explicitly assigned to a user with one of those licenses. This is required for Click CRM to function properly.
Step 4: Installation Admin Assigns Security Roles to Users
Next, the system admin will determine which roles each User should be assigned, based on the level of access each User requires to perform their job.
| Role Name | Functions | Application |
| ClickDimensions CRM Admin |
The Application Admin has full permissions over the CRM Application. They can access the CRM and App Settings Areas. They can create, write and delete all the entities. |
CRM |
| ClickDimensions CRM Manager |
Read access to some Configure Area entities. Create, read, and write permissions on entities outside the Configure Area. Can access Opportunity, Competitor, Marketing List, and Campaign records owned by Users on the team they manage. |
CRM |
| ClickDimensions CRM User |
Read access to some Configure Area entities. Create read and write permissions on entities owned outside the Configure Area if the User is the record owner. |
CRM |
| ClickDimensions Core | See Core Security Role Settings | Marketing Automation |
| ClickDimensions Lock Email Blocks | See Lock Email Blocks Security Role Settings | Marketing Automation |
| ClickDimensions Service | See Service Security Role Settings | Marketing Automation |
| ClickDimensions User | See User Security Role Settings | Marketing Automation |
Step 5: Individual Users Configure Mailbox Connection
Finally, relevant Users in the environment will each need to individually configure their User's access to Outlook within CRM. This process is:
1. Open a Template or a Sequence's Email step
2. There will be a message saying "Click needs access to your mailbox."
3. Click the Grant Access button in this message and follow the steps.
NOTE: For this setup process to work, access must be granted to Microsoft Graph.