In this article, you'll find the following guides for connecting with HaloPSA:
- Complete Partner Setup in HaloPSA
- Connect to HaloPSA on Dropsuite Partner Portal
- Create a New Organization Synced with HaloPSA
- Edit an Existing Organization with HaloPSA
- Create an Agent with Minimal Permissions on HaloPSA
- Revoke HaloPSA Integration
Complete Partner Setup in HaloPSA
Role Creation within HaloPSA
- Launch HaloPSA URL. Note that this is different from partner to partner. For Dropsuite, the URL is: https://dropsuite.halopsa.com/
- Log in with your valid credentials.
- Navigate to Configuration > Teams & Agents > Roles. To create a new role, select New.
- Complete the role information
From the Details tab:
- Role Name: Dropsuite API role
- Choose Save, then choose Edit.
From the Permissions tab:
- Feature Access section:
- Tickets Access Level: Select Read and Modify.
- Customers Access Level: Select Read Only.
- Suppliers Access Level: Select Read and Modify.
- Software Licensing Access Level: Select Read and Modify.
- Tickets Permissions section:
- Can add new Tickets: Select Yes.
- Can Edit Tickets Which Are Not Assigned To Them: Select Yes.
- Ticket Type Restrictions section:
- Allow use of all Ticket Types: Select Yes.
- Client Restrictions section:
- Allow use of all Customers: Select Yes for convenience. If you want to control access only for specific customers used with Dropsuite integration, select No. Then, choose the relevant customers in the Accessible Customers dropdown.
- Choose Save.
Agent Creation within HaloPSA
- Navigate to Configuration > Teams & Agents > Agents.
- Choose New to create a new agent.
- Fill in the following details for the agent:
From the Details tab:
- Account Details section:
- Username: Type Dropsuite API agent.
- Roles: Select Dropsuite API role.
- Select Account Active.
- Select Is an API-only Agent.
- Agent Details section:
- Default Team: Select No Default Team.
- Work Hours: Select Default Working Hours.
- Approval Settings section:
- Clear Can approve Invoices.
- Choose Save.
Application Setup within HaloPSA
- Navigate to Configuration > Integrations > HaloPSA API.
- Choose View Applications.
- Choose New to create a new application.
- Enter a meaningful application name, and ensure the Active check box is selected.
- Set the Authentication Method to Client ID and Secret (Services).
- Copy the client secret and save it for future reference.
- Set Login Type to Agent.
- Select the agent created in the previous steps.
- From the Permissions tab and select permission type as all:standard.
- Click Save and copy the Client ID for future reference.
Connect to HaloPSA on Dropsuite Partner Portal
- Log in to the Dropsuite Partner Portal.
- Navigate to the Integration menu on the left navigation bar.
The Integration menu is available for all types of partners: distributor, direct reseller, and sub-reseller.
- Choose Connect on the HaloPSA card.
- Fill out the form with the correct credentials, and then choose Next Step.
- Site URL: It can be found at Configuration > Integrations > HaloPSO API > API Details (Remove /API from the resource server URL
- Client ID
- Client Secret
- Upon successful connection, a success banner will appear, and you will be redirected to the integration configuration form. Returning to the Integration page will display a Connected badge next to HaloPSA.
- Fill out all required fields in the integration configuration form, and then choose Next Step. You can skip this step and return later to complete the configuration
- Do you want to sync seat quantity to PSA
- Select Ticket Type for service ticket creation
- Select Ticket SLA for service ticket creation
- Select Ticket Priority for service ticket creation
- Upon successful integration configuration, a banner will confirm completion. You can proceed with organization mapping.
Note: Choosing Reset Integration Configuration clears the integration configuration form without affecting your HaloPSA connection.
Create a New Organization Synced with HaloPSA
- Follow the standard procedure to create a new organization.
- After creating the organization, a pop-up will display all connected integrations. In the HaloPSA section, choose Manage
- The system will redirect you to the Manage Connection page. Select Customer and Software License, and then choose Connect. Connect will disable if required fields are empty.
- Upon successful mapping, a green check mark will appear, and the Unlink button will be accessible.
Edit an Existing Organization with HaloPSA
You can edit the mapping from either the Organization or Integration page:
From the Organization page:
- Select the organization, and then choose View Integration under the Kebab button.
- Choose Manage in the HaloPSA section.
- The system will redirect you to the Manage Connection page; select the Customer and Software License, and then choose Connect.
From the Integration page:
- Select Manage Connection under the HaloPSA option.
- The system will redirect you to the Manage Connection page. Select the Customer and Software License, and then choose Connect.
Revoke HaloPSA Integration
- Log in to Dropsuite Partner Portal.
- Navigate to the integration page.
- Select Option, and then select Revoke Connection on the HaloPSA card.
- The system will display the same page with the Connect button active after revoking has been successful.
FAQ
What do error descriptions in service ticket mean?
There are several types of error descriptions. The following table lists each type, along with a brief explanation.
| Error Description | Explanation |
| The email backup has failed |
This error covers the various email backup errors, including:
|
| OneDrive backup fail. Unable to connect to mail server | Failed download item or request to Microsoft Graph with status code 404 (file not found), 429 (throttle), 503 (Microsoft service is down), connection reset by peer or timeout (related to our machine or network). |
| OneDrive backup fail. Authentication error | Failed download item or request to Microsoft Graph with status code 400 (missing params/data in request), 401 (permission related to user/account), 403 (no access to file, scopes or permission related to file). |
| Main App (Global Admin) Token authorization error was detected | This happens when the main app configuration can’t be authorized for some reason; it could be deleted or the permission might be revoked. |
| Main App (Global Admin) Token authorization error is resolved | This happens when the main app resolved its issue and successfully generated the authorization token to continue the process. |
| Device Token authorization error was detected |
The program attempted to authenticate or authorize access using a device token, but that token was either:
This device token is the first step from OAuth flows for any login. |
| Delegated Token authorization error was detected |
In systems like Microsoft Graph API or OAuth 2.0, a delegated token is used when:
This error occurs if the permission is not given when the user is trying to give consent for some permission asked. |
| Backup tasks fail. Unable to connect to mail server | This error occurs when there is an issue with the system trying to connect to the mail server to retrieve all of the tasks owned by the user. |
| Backup tasks fail. Unable to connect to GWS API due to per day throttling | The throttling limit occurs when the Google tasks are being backed up. There is a limit given to Dropsuite’s app to call the Google task’s API. |
| Backup tasks fail. Authentication error | The task backup failure occurs due to an incorrect combination of user data. Could be the UPN is invalid, wrong combination of credentials data, or permission to log in is revoked. |
| Backup contacts fail. Unable to connect to mail server | This error occurs if there is an issue with the system trying to connect to the mail server to retrieve all contacts owned by the user. |
| Backup contacts fail. Authentication error | The contact backup failure occurs due to an incorrect combination of user data. Could be the UPN is invalid, wrong combination of the credentials data, or permission to log in is revoked. |
| Backup calendars fail. Unable to connect to mail server | This error occurs when there is an issue with the system trying to connect to the mail server to retrieve all calendars owned by the user. |
| Backup calendars fail. Authentication error | The calendar backup failure occurs due to an incorrect combination of user data. Could be the UPN is invalid, wrong combination of the credentials data, or permission to log in is revoked. |
| Archive fail. Authentication error | |
| Backup calendars fail. GWS API connection error | This error occurs when the email owning the calendar is inactive or the calendar feature on the Google Workspace Admin console is disabled. |
| Backup contacts fail. GWS API connection error | This error occurs when the email owning the contact is inactive or the contact feature on the Google Workspace Admin console is disabled. |