Connecting your PSA: the Test connection button doesn't show, and other setup errors
In the setup wizard there is no separate Test connection button. The button that tests and saves your credentials is named for your PSA, for example Connect ConnectWise or Connect Autotask, and it sits in the bar at the bottom of the setup card, below the form. Press it after you fill in the fields: Current tests the connection first and saves it only when the test passes. In Settings › Integrations the same step is Test & save connection, at the bottom of the Connect section in your PSA's drawer.
In the setup wizard
- 1Pick your PSA's cardThe PSA step has no Next or Continue button: the cards are the choice. Click Autotask, ConnectWise PSA, HaloPSA, Syncro, Rev.io or SuperOps to open its credential form.
- 2Fill in the fieldsThe checklist above the fields says what to create in your PSA first.
- 3Press Connect and your PSA's nameIt is the filled button in the bar at the bottom of the card, beside ← Choose a different PSA and Connect it later. While the test runs it reads Testing the connection…, and when the test passes the wizard moves on by itself.
The button stays pressable while fields are empty. If one is missing, pressing it shows a line under the form naming what is required instead of running the test.
In Settings › Integrations
- ＋Open your PSA's row and press its Connect button, for example Connect ConnectWise. The drawer's Connect section holds the fields, and Test & save connection sits below them. Scroll down inside the drawer if you don't see it.
- ＋Only a tenant admin sees the Connect section and the button. Anyone else sees no way to connect, because credentials are a tenant admin's job.
- ＋If another PSA is already connected, the row reads "One PSA per workspace. Disconnect" and that PSA's name, and offers no Connect. Current works with one PSA per workspace.
- ＋On SuperOps the button at the foot of the drawer reads Connect SuperOps, and it stays greyed out until both the subdomain and the API token are filled in.
What each PSA asks for
| PSA | Required | Optional |
|---|---|---|
| Autotask | API username, API secret, tracking identifier (integration code) | API zone URL, under Advanced: set the API zone manually. Leave it blank so Current finds your zone |
| ConnectWise PSA | Cloud or On-premise, then the Site URL (or your server's address), Company ID, public key and private key | None |
| HaloPSA | Instance URL, Client ID, Client secret | Auth URL, and Tenant for hosted multi-tenant Halo only |
| Syncro | Syncro subdomain, API token | The date the token expires, if you set one |
| Rev.io | API key | Rev.io web address, for links to tickets and customers |
| SuperOps | SuperOps subdomain, API token, region | None |
Common errors and the fix
| The message says | What to do |
|---|---|
| All three credentials are required / All four fields are required | Fill in every required field above. The ConnectWise key pair comes from the API Member's API Keys tab. |
| Autotask rejected the credentials | Check the API username, the secret and the tracking identifier. The tracking identifier must be a Custom (Internal Integration) identifier. |
| Autotask doesn't recognise that API username | Copy the username from the API user's security settings in Autotask. It looks like an email address. |
| Autotask didn't answer within 10 seconds | Your details weren't checked yet. Press Connect again in a minute. |
| That's a ConnectWise sign-in portal, not your PSA address | Enter the address you sign in to ConnectWise PSA at, such as na.myconnectwise.net, eu.myconnectwise.net or aus.myconnectwise.net. |
| ConnectWise rejected the credentials | Check the Site URL first, then the Company ID and the key pair. |
| A list of security-role lines | The test reads every area the first sync needs. Set each listed line to Inquire: All on the API Member's security role and test again, or press Connect anyway and fix the role later. |
| We couldn't find a HaloPSA sign-in at … | Check the Instance URL (HaloPSA cloud looks like yourname.halopsa.com) and the Auth URL if you set one. |
| HaloPSA rejected the credentials | Check the Client ID and Client secret, and the application's authentication method: it must be Client ID and Secret (Services). |
| … is already connected to this workspace | Disconnect the other PSA in Settings › Integrations first, then connect this one. |
| Connected, but saving your progress failed | The connection worked. Press the button once more. |
What permissions does the API user need?
Each PSA's setup checklist lists the account to create and every permission it needs: "Prepare your Autotask before onboarding: the setup checklist", "Prepare your ConnectWise before onboarding: the setup checklist", "Prepare your HaloPSA before onboarding: the setup checklist", "Prepare your Syncro before onboarding: the setup checklist" and "Prepare your Rev.io before onboarding: the setup checklist". For Autotask, HaloPSA and Syncro a passing test proves the credentials are right but not that the account can see everything, so a missing permission shows up at the first sync as an area that comes back empty. For ConnectWise the test checks the security role too.
Is my PSA data encrypted?
Yes. Traffic to your PSA and to Current travels over TLS, your synced records are encrypted at rest, and every stored credential is encrypted with AES-256. After a test passes, the secret is kept on Current's servers and never sent back to a browser. See "How Current stores credentials and secrets".