> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up the ConnectWise PSA Ticketing Integration

> Create the ConnectWise Manage security role, API member, and keys Thread needs to sync tickets, contacts, time entries, and configurations with your PSA.

This guide explains how to set up the ConnectWise PSA Integration in the platform.

During the initial setup of your account in the platform, you are prompted to set up your ticketing system. Following the prompts for ConnectWise will lead you to the following screen asking you to enter API credentials.

**1. Leave this screen open.**

Leave this screen open, we will come back to it later.

![ConnectWise API credentials entry screen in the platform setup](https://mintcdn.com/thread/orXb8p5xlYZ8oWd0/images/workspace-creation-cw-setup.png?fit=max\&auto=format\&n=orXb8p5xlYZ8oWd0\&q=85\&s=993f79cb9d0cb7cd6908a4fedb088b80)

**2. Open a new browser tab to configure the API user.**

Open a new browser tab or window to continue to the next step, configuring the API user.

## 1. Configure the Security Role for the API User

**1. Log in to ConnectWise.**

Log in to ConnectWise.

![ConnectWise login screen](https://mintcdn.com/thread/yMrisProrR453qj0/images/26201e3d-image.png?fit=max\&auto=format\&n=yMrisProrR453qj0\&q=85\&s=464d46c22baf0c2cb9e5bc838e4326df)

**2. Create a new security role.**

Select in the left side panel **System** -> **Security Roles** and click on the **+** sign to create a new security role.

![System → Security Roles with the add button in ConnectWise](https://mintcdn.com/thread/yMrisProrR453qj0/images/04960a6d-image.png?fit=max\&auto=format\&n=yMrisProrR453qj0\&q=85\&s=de5a899b62fbe5afc7981eb6d06d388e)

**3. Name the role and save.**

Enter a name for the new role in the **Role ID** field and click **Save**.

![Role ID field for a new security role in ConnectWise](https://mintcdn.com/thread/yMrisProrR453qj0/images/26f8cb3b-screenshot-2026-05-08-133712.png?fit=max\&auto=format\&n=yMrisProrR453qj0\&q=85\&s=34b43e52f54eb9c3840d95b728450c47)

**4. Set the permissions below and save.**

Set the permissions in the following tables, then click **Save**.

Each table below lists one category on the security role. Set every row to the levels shown. Thread checks the API member's role against these levels, so a level set lower than shown is reported as a missing permission. Delete stays at **None** everywhere except **Resource Scheduling**, **Table Setup**, and **Time Entry**.

### Companies

| Permission | Add Level | Edit Level | Delete Level | Inquire Level | Why Thread needs it |
| - | - | - | - | - | - |
| Company Maintenance | All | All | None | All | Creates or updates company records when new customers reach out. |
| Configurations | All | All | None | All | Links device configurations to tickets. Edit is needed to create the link. |
| Contacts | All | All | None | All | Creates contact records and links them to tickets. |
| Manage Attachments | All | All | None | All | Uploads files from customer conversations to tickets. |
| Team Members | All | All | None | All | Reads members for work roles and work types. |

### Finance

| Permission | Add Level | Edit Level | Delete Level | Inquire Level | Why Thread needs it |
| - | - | - | - | - | - |
| Agreements | None | None | None | All | Reads service agreements to show SLA information and route tickets. |
| Billing View Time | All | All | None | All | Supports billable time tracking and billing reconciliation. |

> [!NOTE]
>
> The **Agreements** permission covers agreement records only. Thread can still set or clear the agreement on a ticket through the **Service Tickets** permission. See [Agreements on tickets](#agreements-on-tickets).

### Project

| Permission | Add Level | Edit Level | Delete Level | Inquire Level | Why Thread needs it |
| - | - | - | - | - | - |
| Project Tickets | All | All | None | All | Reads and updates project tickets. |

### Service Desk

| Permission | Add Level | Edit Level | Delete Level | Inquire Level | Why Thread needs it |
| - | - | - | - | - | - |
| Close Service Tickets | All | All | None | All | Closes tickets from Thread. |
| Merge Tickets | All | All | None | All | Merges duplicate tickets. |
| Resource Scheduling | All | All | All | All | Schedules, reschedules, and removes technician appointments from Planner. |
| Service Tickets | All | All | None | All | Creates, reads, and updates tickets in ConnectWise. |

### System

| Permission | Add Level | Edit Level | Delete Level | Inquire Level | Why Thread needs it |
| - | - | - | - | - | - |
| Manage Hosted API | None | None | None | All | Reads the Thread Pods registered on the service ticket screen. |
| Member Maintenance | None | None | None | All | Reads members to sync your team with Thread. |
| Security Roles | None | None | None | All | Reads the API member's own role so Thread can check these permissions. |
| Table Setup | All | All | All | All | Reads the setup tables listed below. Add and Edit let Thread create and update its ticket source, its pods, and its callbacks. Delete lets Thread remove callbacks it no longer uses, such as one for a board you stopped syncing. |

**Manage Hosted API** and **Table Setup** are separate rows, and the API member's role needs both. The **Manage Hosted API** row controls the permission itself. The **General / Manage Hosted API** table inside **Table Setup** gives access to the setup table where Thread registers its pods.

Next, limit **Table Setup** to the tables Thread uses:

1. On the **Table Setup** row, click **customize**.
2. In the **Update Security** modal, move the following tables to **Allow Access to these**:

| Table | Why Thread needs it |
| - | - |
| Agreements / Agreement Type | Reads agreement types for routing and categorization. |
| Company / Company Status | Reads company status for company-level workflows. |
| Company / Country | Stores the correct country on client records so phone numbers format correctly. If this table is disallowed, the country sync fails, company and contact syncs still complete, and client country fields stay blank. |
| General / Integrator Login | Lets Thread read, create, reactivate and remove the ConnectWise callbacks (webhooks) that keep tickets updated in real time. Without it, connecting or reconnecting fails and new service boards get no callback. |
| General / Manage Hosted API | Creates and updates the Thread Pods on the service ticket screen. |
| Scheduling / Location | Reads locations for scheduling and routing. |
| Service / Email Formats | Keeps emails from Thread consistent with your ConnectWise formatting. |
| Service / Priority | Syncs priorities and supports auto-prioritization. |
| Service / Service Board | Powers ticket routing, multi-board workflows, and filtering. |
| Service / SLA | Tracks SLA targets in Thread. |
| Service / Source | Creates and manages the Thread ticket source, so you can see where tickets originate. |
| Time / Work Role | Links time entries to the correct work role. |

![Table Setup customize modal with the required permissions allowed](https://mintcdn.com/thread/MmA6qEMELRi-vXeU/images/dd8c7843-image.png?fit=max\&auto=format\&n=MmA6qEMELRi-vXeU\&q=85\&s=1b78949d83d093b27b883968760c8294)

### Time & Expense

| Permission | Add Level | Edit Level | Delete Level | Inquire Level | Why Thread needs it |
| - | - | - | - | - | - |
| Expense Billable Option | All | All | None | All | Marks expenses as billable or non-billable. |
| Expense Report Entry | All | All | None | All | Supports expense entries tied to tickets. |
| Time Entry | All | All | All | All | Creates, edits, and deletes time entries from TimePad. |
| Time Entry Billable Option | None | All | None | None | Sets time entries as billable or non-billable. Only Edit is needed. |

## 2. Create the API Member and Keys

**1. Add a new API member.**

Select **System** -> **Members** in the left side panel, click on **API Members** tab and click on **+** to add a new API member.

![API Members tab with the add button in ConnectWise](https://mintcdn.com/thread/yMrisProrR453qj0/images/36b848c5-image.png?fit=max\&auto=format\&n=yMrisProrR453qj0\&q=85\&s=d805251fc3515b24c22df897a1164615)

**2. Fill out the required fields and assign the role.**

Fill out all required fields, and select the role created earlier in **System** -> **Role ID**.

1. Set **Member ID** to *Thread* (or whatever you like to call it)
2. Make sure that **Level** is set to Corporate (Level 1).
3. **IMPORTANT**: Remove all boards from **Service Defaults** -> **Restricted Board Access**. Click **Save**.

![Restricted Board Access cleared under Service Defaults](https://mintcdn.com/thread/yMrisProrR453qj0/images/351b80ab-screenshot-2026-05-08-134002.png?fit=max\&auto=format\&n=yMrisProrR453qj0\&q=85\&s=dae2ff3351f42e297beba1a8a9666674)

4. If you are setting up Board exclusions in your API Member there is an extra flag that has to be turned on to make callbacks from api users compliant to their board restrictions. 1) Navigate to System > Setup Tables > Manage Labs table 2) Pull up and activate the 'Callback Member Board Restrictions' lab with the Actions drop down:

![Callback Member Board Restrictions lab in Manage Labs](https://mintcdn.com/thread/MmA6qEMELRi-vXeU/images/f3e089bb-image.png?fit=max\&auto=format\&n=MmA6qEMELRi-vXeU\&q=85\&s=62633801be2b961fff48b3240f77164f)

**3. Open the API Keys tab and add a key.**

Select **API Keys** tab and click on **+** icon in the top left corner

![API Keys tab with the add button in ConnectWise](https://mintcdn.com/thread/ysyi1-ysJ96KyxOf/images/712c8813-image.png?fit=max\&auto=format\&n=ysyi1-ysJ96KyxOf\&q=85\&s=b744695430805f2e348b1923d9e1acf0)

**4. Name the key Thread and save.**

Type "Thread" in Description field and press **Save**.

![Description field set to Thread for the new API key](https://mintcdn.com/thread/yMrisProrR453qj0/images/3d53198b-image.png?fit=max\&auto=format\&n=yMrisProrR453qj0\&q=85\&s=188df1c71c168fa7a357402d9812f1f9)

**5. Save your public and private keys.**

**Save your public and private keys** - while public key is always available in ConnectWise, private key is only available at the time the key is created, so please make a note of it, you will need it in the next step.

![Generated public and private API keys in ConnectWise](https://mintcdn.com/thread/MmA6qEMELRi-vXeU/images/e6dba202-screenshot-2026-05-08-134440.png?fit=max\&auto=format\&n=MmA6qEMELRi-vXeU\&q=85\&s=7de3c3a475fb245c2ef9d9d1a2210d5b)

## 3. Configure Thread with the API Information

Now that you've set up your API keys, it's time to integrate ConnectWise with Thread! It's time to take the information you saved in the previous steps and enter it into the web form.

![Thread ConnectWise integration credentials web form](https://mintcdn.com/thread/yMrisProrR453qj0/images/417c06bd-2023-08-29-14-10-37.png?fit=max\&auto=format\&n=yMrisProrR453qj0\&q=85\&s=bc7805c576073a1ea41be05ca02cc2a6)

**1. Enter the Host base URL.**

**Host** - Enter in the base URL that you use to log in to ConnectWise. If you are a ConnectWise Cloud customer, you can refer to the table below for extra assistance. If you manage and/or host your own instance of ConnectWise, refer to the URL that you use to log in to ConnectWise.

| ConnectWise Cloud Region | ConnectWise PSA URL |
| - | - |
| North America | [https://na.myconnectwise.net](https://na.myconnectwise.net) |
| Europe | [https://eu.myconnectwise.net](https://eu.myconnectwise.net) |
| Australia and New Zealand | [https://aus.myconnectwise.net](https://aus.myconnectwise.net) |
| Africa | [https://za.myconnectwise.net](https://za.myconnectwise.net) |

**2. Enter your Company ID.**

**My Company ID** - Enter in the company ID that you use to log in to ConnectWise.

**3. Enter the Public Key.**

**Public Key** - Enter in the **Public Key** for the API key you saved in step **2.5 Create the API Member and Keys** section above.

**4. Enter the Private Key.**

**Private Key** - Enter the **Private Key** for the API key you saved in step **2.5** **Create the API Member and Keys** section above.

**5. Choose whether to keep members in sync with PSA.**

**Keep members in sync with PSA**

1. Leave this checked to quickly enable your team's access to Thread.
2. Uncheck this if you prefer to invite members individually. If you choose this option, you will be able to invite members later.

**6. Click Continue.**

Once everything has been entered correctly, click **Continue** to proceed.

## 4. Set a default team and status on your service boards

Thread doesn't send a team when it creates a ConnectWise ticket, so ConnectWise assigns the board's default team. If the board has no default team, ConnectWise rejects the ticket. The same applies to status: when the feature creating the ticket doesn't set a status, ConnectWise uses the board's default status.

This applies to every board Thread creates tickets on, whether the ticket comes from Voice AI, Super Magic, Messenger, or another Thread feature.

**1. Open the service board.**

In ConnectWise, go to **System** → **Setup Tables** → **Service Board** and open a board Thread creates tickets on.

**2. Mark a default team.**

On the **Teams** tab, open a team, check **Default**, and click **Save**.

**3. Mark a default status.**

On the **Statuses** tab, open a status, check **Default**, and click **Save**.

**4. Repeat for each board.**

Repeat these steps for every other board Thread creates tickets on.

## Give technicians access to Thread Pods

The Thread Pods (**Thread: Real time notes** and **Thread: Auto time entries**) appear on service tickets only for members whose own security role can read them. This is separate from the API member's role.

**1. Open each technician security role.**

In ConnectWise, go to **System** → **Security Roles** and open a role assigned to technicians who use the pods.

**2. Set the Manage Hosted API inquire level.**

Expand **System** and set **Manage Hosted API** to **Inquire Level: All**. Leave **Add Level**, **Edit Level**, and **Delete Level** at **None**.

**3. Save and repeat for every technician role.**

Click **Save**, then repeat for each role. Technicians do not need **Table Setup** access to see the pods.

To add the pods to a technician's ticket view, follow [Add Thread Pods to ConnectWise service tickets](https://docs.getthread.com/integrations/how-to-enable-a-pod.md).

## Agreements on tickets

The **Finance > Agreements** permission controls agreement records. Thread only reads those records and never creates, edits, or deletes them.

The agreement assigned to a ticket is a ticket field. Thread updates it through the **Service Tickets** permission. Thread changes a ticket's agreement in these cases:

* **A technician or flow sets it.** Technicians can pick an agreement in the [thread control panel](https://docs.getthread.com/inbox/thread-control-panel.md). A [flow](https://docs.getthread.com/inbox/flows.md) can set the agreement when its conditions match.
* **The ticket moves to a different company.** Thread clears the previous company's agreement, because it doesn't belong to the new company. Thread then applies the new company's default agreement for the ticket's board, if one exists.
* **The ticket moves to a board outside the agreement's location.** If ConnectWise rejects the board move because the agreement is restricted to a location, Thread removes the agreement and retries the move.

Changing only the contact within the same company keeps the existing agreement.

## ConnectWise PSA FAQ

> [accordion] My reports credit the Thread API user for closing tickets. How do we reflect which technician closed the ticket?
>
> **Q: "Since my techs started using Inbox, I noticed that my reports are giving credit to the Thread API user for closing tickets. We want to make sure our reports reflect which technician closed the ticket. How do you recommend we handle this?"**
>
> A: ConnectWise's API does not allow vendors to impersonate users in the audit trail (only in the notes and other areas). This means that if a technician closes a ticket using Thread, it will attribute the closed by meta data in the ticket to your Thread API member. A great workaround is to update your reporting to report on tickets closed by ticket owner.
>
> ![ConnectWise reporting workaround for tickets closed by owner](https://mintcdn.com/thread/MmA6qEMELRi-vXeU/images/f3e089bb-image.png?fit=max\&auto=format\&n=MmA6qEMELRi-vXeU\&q=85\&s=62633801be2b961fff48b3240f77164f)

> [accordion] A technician can't see the Thread Pods on their tickets. What permission is missing?
>
> The technician's own security role needs **System** → **Manage Hosted API** set to **Inquire Level: All**. The other levels can stay at **None**. Follow [Give technicians access to Thread Pods](#give-technicians-access-to-thread-pods), then have the technician reload their service ticket view. If the pods still don't appear, see the troubleshooting steps in [Add Thread Pods to ConnectWise service tickets](https://docs.getthread.com/integrations/how-to-enable-a-pod.md#troubleshooting).

> [accordion] Tickets fail with 'Cannot find default team for board specified.' How do I fix it?
>
> ConnectWise returns this 400 error when the board Thread is creating the ticket on has no default team. A related error, "Cannot find default status for board specified.", means the board has no default status.
>
> Set a default team and default status on that board, as described in [Set a default team and status on your service boards](#4-set-a-default-team-and-status-on-your-service-boards). Once you save the default, Thread can create tickets on that board again. You don't need to change anything in Thread.

> [accordion] Connecting fails with "Permissions missing (code 903)". How do I fix it?
>
> The error lists every permission the Thread API member's security role is missing, for example `Permissions missing (code 903): [Customization] General / Integrator Login`. Add each listed item to the role, then connect again.
>
> * An item starting with **\[Customization]** is a Table Setup permission. In ConnectWise, go to **System** → **Security Roles**, open the role assigned to the Thread API member, click **customize** next to **Table Setup**, allow the listed item, and save.
> * Any other item is a permission row on the role itself (such as **Service Tickets** or **Table Setup**). Set it to the levels in the tables in [Configure the Security Role for the API User](#1-configure-the-security-role-for-the-api-user).
>
> If you gave the API member a broader role (such as Admin) to get past this error, move it back to the Thread role once the permissions are in place.

## Next: Design your Customer Experience

> [card] [Design your customer chat experience](https://docs.getthread.com/messenger/configurations-in-messenger.md)
>
> Set up and personalize Thread Messenger for your clients.


## Related topics

- [Add Thread Pods to ConnectWise Service Tickets](https://docs.getthread.com/integrations/how-to-enable-a-pod.md)
- [Set Up the ConnectWise Automate Integration](https://docs.getthread.com/integrations/how-do-i-set-up-connectwise-automate.md)
- [Set Up the Autotask PSA Ticketing Integration](https://docs.getthread.com/integrations/creating-a-autotask-api-user.md)
