Open PSA in Thread Admin
Leave this screen open.


Open a new browser tab to configure the API user.
1. Configure the Security Role for the API User
Log in to ConnectWise.

Create a new security role.

Name the role and save.

Set the permissions below and save.
Companies
Finance
Project
Service Desk
System
- On the Table Setup row, click customize.
- In the Update Security modal, move the following tables to Allow Access to these:

Time & Expense
2. Create the API Member and Keys
Add a new API member.

Fill out the required fields and assign the role.
- Set Member ID to Thread (or whatever you like to call it)
- Make sure that Level is set to Corporate (Level 1).
- IMPORTANT: Remove all boards from Service Defaults -> Restricted Board Access. Click Save.

- 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:

Open the API Keys tab and add a key.

Name the key Thread and save.

Save your public and private keys.

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.
Enter the Host base URL.
Enter your Company ID.
Enter the Public Key.
Enter the Private Key.
Choose whether to keep members in sync with PSA.
- Leave this checked to quickly enable your team’s access to Thread.
- Uncheck this if you prefer to invite members individually. If you choose this option, you will be able to invite members later.
Click Continue.
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.Open the service board.
Mark a default team.
Mark a default status.
Repeat for each board.
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.Open each technician security role.
Set the Manage Hosted API inquire level.
Save and repeat for every technician role.
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. A flow 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.
ConnectWise PSA FAQ
My reports credit the Thread API user for closing tickets. How do we reflect which technician closed the ticket?
My reports credit the Thread API user for closing tickets. How do we reflect which technician closed the ticket?

A technician can't see the Thread Pods on their tickets. What permission is missing?
A technician can't see the Thread Pods on their tickets. What permission is missing?
Tickets fail with 'Cannot find default team for board specified.' How do I fix it?
Tickets fail with 'Cannot find default team for board specified.' How do I fix it?
Connecting fails with "Permissions missing (code 903)". How do I fix it?
Connecting fails with "Permissions missing (code 903)". How do I fix it?
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.