This document provides instructions for configuring the ConnectWise Manage Cloud integration in BrightGauge. Before you connect to the Manage Cloud datasource in BrightGauge, you must create an API member with a dedicated security role in Manage.
Create a Security Role in Manage
Security roles enable you to define permissions and access for your Manage members. The Manage integration requires an API member with a dedicated security role to ensure proper access to your data. Please be sure to create the security role and the API member from the Manage desktop application.
To create a security role in Manage:
- Navigate to System > Security Roles.
- Click the New Item icon.
- Enter a Role ID to help you easily identify the new role. For example, BrightGaugeAPI.
- Click Save.
- Assign the Inquire Level > All permission for the following actions. Leave the Add, Edit, and Delete levels set to None.
Note: As the integration is developed, new permissions will be added that are not currently listed here. If you encounter an issue with the integration, please refer back to this table to ensure that all necessary permissions are enabled.
Module Action Companies
- CRM/Sales Activities
- Team Members
- Product Catalog
- Purchase Orders
- Reports - PO Open Order
- Project Header
- Project Reports
- Project Tickets
- Sales Orders
- Service Tickets
- Close Service Tickets
- API Reports
- Table Setup
Time & Expense
- Expense Report Entry
- Time Entry
- Click Save.
After you create the security role, you can proceed to create the API member.
Create an API Member in Manage
The create the API member in Manage:
- Navigate to System > Members.
- Select the API Members tab.
- Click on the New Item icon.
- Enter a Member ID and a Member Name. For example, BrightGaugeAPI.
- Select the new security role from the Role ID menu. Please note that the Admin role is not recommended for the integration.
- Select Corporate for the Level. This is to ensure that you do not restrict the service boards you see.
- Click Save after all fields have been completed.
- Select the API Keys tab.
- Click on the New Item icon.
- Enter a Decription for the key. For example, BrightGauge API.
- Click on the Save icon. The keys are displayed after the item is saved. Be sure to save both keys now, as you may only view the Private Key at the time it is created.
Log in to your BrightGauge Account
If you have not yet created an account, go here to get started.
On first login, from the Account Overview page, click on the Add a Datasource button. Proceed to enter the API credentials.
To add the datasource:
- Click on the Data menu and select Datasources.
- Locate the ConnectWise Manage Cloud datasource under either All or PSA. The Edit ConnectWise Manage API screen opens.
Enter the Credentials
From the datasource connection screen, enter the following information:
- Name: A name for your integration. For example, ConnectWise Manage Cloud.
- Site: The region in which your ConnectWise Manage instance is hosted. It's most notable by the URL you use to login to Manage.
- Company ID: Your ConnectWise Manage company name.
- Public Key: The public API key you generated in Manage.
- Private Key: The private API key you generated in Manage.
- Your Locale: Your country or region for ConnectWise. It will allow for deep linking.
Test the Connection
After you complete all fields, make sure to test the connection. If successful, save the connection.
Please note that the AutoFill feature in your web browser may attempt to input the wrong credentials for the database user field. After a successful test connection, the page is refreshed and the AutoFill takes effect automatically. The user then selects save, accidentally saving the auto-filled credentials, which are incorrect. To prevent this issue, open a private (or incognito) browsing window to complete the datasource configuration page. Or, simply retype the credentials after the test connection and click Save.
After you save the connection, the datasets and gauges are added to your account and begin syncing immediately. Dashboards, reports, datasets, and gauges are added to your account after the datasource is saved. The initial sync usually takes 20-30 minutes to complete.
FAQ: Dispatch Portal
If your newly-created BrightGauge user is showing up in the dispatch portal, then there's an easy option to stop that. In the panel where you first created the user, there's a section for scheduling. Make sure to select the Do not display this member on the Dispatch Portal checkbox for the API.
- Agreement KPIs
- BGS - Procurement
- BGS - Projects
- BGS - SLA
- BGS - Service Board
- BGS - Service Desk Leaders
- BGS Sales Board
- Client Dashboard Template
- In/Out Board
- Member Efficiency
- Tech Dashboard
- Agreement Monthly Review
- BGS - Monthly Project Wrapup
- BGS - Service Desk Leaders
- BGS - Weekly Project Report
- CW Hosted Executive Summary Report
- Member Efficiency - Current Week
- Member Efficiency - Today
- Activity Data: Data for Activities updated in the last 120 days
- Agreement Addition List: Data for additions for agreements
- Agreement Data: This dataset is a listing of all agreements in Manage with an end date in the last 365 days or no end date entered. Cancelled agreements are also not included
- Agreement Data Monthly Last 3 Months: This dataset looks at agreement invoices, hours against the agreement, and addition costs by month to give you statistics on how the agreement is performing. The data is for the last 3 months only
- Assigned Resources Last 120 Days: Data for schedules on tickets. This allows you to see individual technicians scheduled for tickets. This is only for schedules updated in the last 120 days
- Assigned Resources Last 14 Days: This dataset pulls in scheduling information only for schedules on tickets updated in the last 14 days or that are open
- Company Data: This dataset pulls in data for companies setup within Manage. This gives 1 line per company and has information contained within their company setup. This pulls in all, non-deleted companies
- Configuration Data: Data for Configurations entered in Manage
- Configuration Questions and Answers: This dataset allows for one to see the questions and answers associated with Configurations. This means a single configuration will show multiple times if it has many questions. This dataset only shows active configurations with questions
- Configuration Ticket Statistics Last 240 Days: This dataset is a clone of ticket statistics to show information on attached configuration. A single ticket will show 3 times if there are 3 configs. This is only for tickets updated in the last 240 days
- Contact Data: This data shows you contact information for contacts in Manage. This dataset can be used in dataset mashups to see data for those without information (an advanced feature)
- Invoice Data: Invoice data updated in the last two years
- Member Data: This is a dataset to look at data for your current users setup in Manage
- Opportunity Data: Data for Opportunities updated in the last 365 days
- Products: ConnectWise products purchased within the last 2 years
- Project Phase and Tickets: Data for the individual phases of a project and any associated tickets. This pulls in data for all open projects (no actual end date has been set) or for phases updated in the last 240 days
- Project Statistics: A wholesale look at projects open or updated in the last 240 days
- Purchase Orders: Purchase orders updated in the last 365 days or currently open
- Sales Orders: Sales Order information for orders updated in the last 365 days
- Service Boards: Service board data as they appear in your Manage instance. This dataset also allowss you to see the scheduled on-call technician associated with each service board
- Survey Responses: Data for surveys received in the last 120 days
- Ticket SLA Data Live: Data for SLA data for live tickets. NO closed or resolved tickets in this dataset. The time to goal fields in this dataset are only applicable before they hit the associated SLA level (response, resolution plan, resolution)
- Ticket Statistics Last 240 Days: Data for tickets updated in the last 240 days. This is meant for longer, trending data
- Tickets Stats Last 14 Days: Data for tickets updated in the last 14 days or not closed. This is a fast syncing dataset meant for dashboards
- Time Entry Last 120 Days: Data for time entries from the last 120 days
For a list of all default gauges, please visit the Gauges section of your account, sort by the Datasource you'd like to see, and select for Default.
If you have any questions, don't hesitate to ask us at email@example.com.