Summary
-
Introduction
Crewhu connects to HaloPSA through an API application. The permissions you grant there control what data Crewhu can read or write, and each product needs its own set.
You only need to grant permissions for the products you use. Many are shared, so you won’t check the same box twice.
Note:
For this guide, an active HaloPSA integration in Crewhu is required. To create one, see Halo PSA Integration. You will also need access in Halo to edit API applications.
-
How Crewhu Checks Permissions
After entering your Halo credentials in the Setup Integration screen, click Test Integration. Crewhu checks the API application and shows results grouped by product.
Each group shows how many permissions are granted, with a check mark next to each one in place. A product works only when all permissions in its group are granted. If you don’t use a product, ignore its group.
-
Updating the API Application in Halo
- In Halo, go to Configuration > Integrations > HaloPSA API > View Applications.
- Open the application used by Crewhu.
- Set Login Type to Agent and select the agent configured for Crewhu.
- The application can only access what that agent is allowed to see. An agent missing the required role access levels will limit the data Crewhu receives, even with the right permissions checked. For agent requirements, see Halo PSA Integration. An API-only agent doesn’t use a Halo license.
- Go to the Permissions tab and check the permissions for the products you use (see the table below).
- Save the application.
- Back in Crewhu, click Test Integration to confirm every group you need is complete.
-
All Permissions
| Permission | CSAT Writeback |
Trends & Gamification |
Explorer |
Project Surveys |
|---|---|---|---|---|
| read:tickets | ✔️ |
✔️ |
✔️ |
✔️ |
| read:customers | ✔️ |
✔️ |
✔️ |
✔️ |
| edit:tickets | ✔️ |
✖️ |
✖️ |
✖️ |
read:customers is required by every product. Without it, the client and user sync fails across the board.
edit:tickets is only needed for CSAT Writeback (Legacy): it lets Crewhu write data back to Halo.
-
Permissions by Crewhu Product
CSAT Writeback (Legacy)
Writes the survey rating to Crewhu custom fields on your Halo tickets and adds the feedback as a private note. The ticket status is not changed.
- read:tickets
- read:customers
- edit:tickets
Without edit:tickets, the writeback silently fails: nothing flags on the ticket. The Crewhu custom fields must also exist in Halo and be added to the Field List of your ticket types. Crewhu doesn’t create these fields. See Halo PSA Integration.
-
Trends & Metrics for Gamification
Uses Halo ticket metrics to run contests. Uses the same data as Trends:
- read:tickets
- read:customers
-
Explorer
Reads tickets, clients, and users, and matches them with CSAT surveys in Crewhu Explorer.
- read:tickets
- read:customers
-
Project Surveys
Reads your projects in Halo, including their clients and users, to send Project Surveys to the right contacts. Crewhu only reads project data and never modifies your projects.
- read:tickets
- read:customers
Note:
In Halo, projects are unlocked by read:tickets, not read:projects.
Comments
0 comments
Please sign in to leave a comment.