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

# Connecting CyberQP to Neo

> Create CyberQP API credentials and save them in Neo

You connect CyberQP once at the MSP level. The connection reaches what the CyberQP technician who creates it can see, so use a technician with the Primary or Super role.

## 1. Create the API credentials

<Steps>
  <Step title="Use a dedicated technician">
    We recommend a dedicated **System User** technician in CyberQP with the Primary or Super role, so the connection does not depend on a person's account. Sign in to the CyberQP dashboard as that technician.
  </Step>

  <Step title="Open the API login page for your data centre">
    In the same browser, open the page for the data centre you sign in to:

    | You sign in at | Open |
    | - | - |
    | admin.getquickpass.com | [https://us.getquickpass.com/api/v1/auth/login](https://us.getquickpass.com/api/v1/auth/login) |
    | eu-admin.getquickpass.com | [https://eu.getquickpass.com/api/v1/auth/login](https://eu.getquickpass.com/api/v1/auth/login) |
    | ca.admin.cyberqp.com | [https://ca.cyberqp.com/api/v1/auth/login](https://ca.cyberqp.com/api/v1/auth/login) |
  </Step>

  <Step title="Accept and copy the credentials">
    Click **Accept**. CyberQP shows an Access Token, a Refresh Token and a Client ID. Copy the **Refresh Token** and the **Client ID**. CyberQP shows them once.
  </Step>
</Steps>

<Warning>
  A CyberQP refresh token works once. Neo exchanges it when you save and keeps the new one CyberQP returns each time. Do not use the same refresh token in a script or another tool, or Neo's connection stops working. To give another tool access, open the API login page again for a new set of credentials.
</Warning>

## 2. Add the credentials in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open **Integrations** and find the CyberQP card, under Security.
  </Step>

  <Step title="Save the credentials">
    Pick your **Data Centre**, paste the **Client ID** and the **Refresh Token**, and click **Save**. Neo exchanges the token with CyberQP before it saves, so wrong credentials are rejected straight away.
  </Step>
</Steps>

<Note>
  A refresh token expires after six months without use. Neo uses it at least once a day while your PSA syncs, so the connection stays alive. If CyberQP refuses it, Neo tells you in the dashboard and by email; repeat the steps above to reconnect.
</Note>

## 3. Turn CyberQP on per agent

Open the agent, go to the Integrations section, and configure the CyberQP block. Pick a profile, then change any area:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Customers & Accounts** | Disabled, Read Only | Customers, agent GUIDs and accounts. |
| **Agent Deployment** | Disabled, Read Only | The agent install token. It installs the agent for any of your customers. |
| **Identity Verification** | Disabled, Read / Write | Sends a push to the end user. |
| **Just-In-Time Accounts** | Disabled, Read Only, Read / Write | Creating, enabling, disabling and deleting JIT admin accounts. Creating or enabling one always asks a technician. |
| **Passwords & OTP** | Disabled, Read Only, Read / Write | Every call always asks a technician, reading a password or an OTP code included. Turn it on only for agents that hand credentials to your team. |
| **Events** | Disabled, Read Only, Read / Write | CyberQP's audit events. |

See [CyberQP API](/agents/tools/security/cyberqp-api) for what each profile does.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.