> ## Documentation Index > Fetch the complete documentation index at: https://docs.mspilot.io/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > MSPilot enrolls technician Windows machines and Apple Silicon Macs so Claude Desktop and ChatGPT run through one governed gateway. Seat words are standard seat and power seat. ConnectWise Manage imports clients and contacts, with optional configuration inventory when no RMM is connected. HIPAA is not a self-serve switch. Mode Switcher is mspilot-mode.exe for the MSP's own Windows machines. # ConnectWise Manage > Connect your cloud PSA, import clients and contacts, and optionally pull device configurations. ConnectWise Manage imports companies as MSPilot clients and keeps their contacts in sync. You can also import workstation and server configurations when you do not use a separate RMM connection. ## Create an API member 1. In ConnectWise Manage, open **System → Security Roles**. Create a dedicated role for MSPilot, or use an existing integration role with the permissions below. 2. Open **System → Members → API Members** and create a dedicated API member. 3. Assign the role and complete the required member fields for your site. 4. Save the member. Open its **API Keys** tab and create a key named `MSPilot`. 5. Copy the **Public Key** and **Private Key** to your password manager. The private key is shown once. Use a dedicated API member rather than a technician's keys. Its company restrictions determine which records MSPilot can read. ## Required permissions ### Clients and contacts Set these permissions in the API member's security role: * **Companies → Company Maintenance: Inquire All** for company import. * **Companies → Contacts: Inquire All** for contact sync. * **System → Table Setup: Inquire All** for company status lookup. If **Table Setup** uses a customized lookup allowlist, include **Company / Company Status**. Keep any lookup access required by your other integrations. ### Optional device import If you turn on **Import devices from ConnectWise Manage**, also grant: * **Companies → Configurations: Inquire All**. * **System → Table Setup: Inquire All**, with **Company / Configuration** and **Company / Configuration Status** in its lookup allowlist. Leave configuration **Add**, **Edit**, **Delete**, and **Configuration - Display Passwords** access off. Device import reads inventory; it does not create or modify Manage configurations. You do not need device permissions when you only import clients and contacts. ## Connect Manage 1. In MSPilot, open **Integrations** and choose **ConnectWise Manage** under **Choose your PSA**. 2. Enter the **Cloud site URL** for your Manage cloud region, such as `https://na.myconnectwise.net`. 3. Enter the **Company ID** you use to sign in to Manage. This is your login company identifier, not a customer's numeric company ID. 4. Paste the API member's **Public key** and **Private key**. 5. Click **Connect Manage**. 6. Click **Sync clients** to import companies and contacts. If new connections are marked **Soon** in your environment, use an existing connection or wait until Manage connections are enabled there. ## Choose whether to import devices Device import starts off. In the connected **ConnectWise Manage** panel, check **Import devices from ConnectWise Manage** if you want Manage to supply inventory. You can also open the connected Manage card to change this setting. Click **Sync clients** after enabling it. MSPilot attaches each configuration to the client imported from the same Manage company ID. You do not need to map companies by name. Use **Choose configuration types** to select your workstation and server types if your Manage setup uses custom names. **Automatically detect workstations and servers** uses configuration type names and operating system details. Domains, licenses, printers, and other non-device configurations are excluded by default. With a custom selection, choose only the types that represent computers. Click **Save configuration types**, then **Sync clients** to apply the selection. Selecting no types imports no devices. Repeated sync updates the same configuration rather than creating another device. Removed or excluded configurations disappear from discovered inventory after a successful sync. Turning device import off stops manual and scheduled Manage device sync and hides its discovered devices. It does not unenroll an installed MSPilot agent. On a client's **Overview** tab, **Manage inventory** shows the company link and **Refresh Manage devices** refreshes only that client's inventory. Install and enroll the MSPilot agent from **Deployment**. Manage supplies inventory and cannot run deployment scripts. ### When you also use an RMM Your connected RMM supplies devices. Manage device import is disabled so MSPilot does not pull two inventories for the same machines. Manage continues to supply clients and contacts. Selecting an RMM also pauses Manage device import while you connect it. MSPilot does not fall back to Manage if that RMM becomes temporarily unavailable. If an RMM writes inventory into Manage configurations, you can import those configurations without connecting the RMM separately. The records must be visible under the correct company in Manage first. ## Troubleshooting If Manage connects but device sync returns a permission error, check **Configurations: Inquire All** and both configuration setup lookups. Client credential validation does not test optional device permissions. If a device is missing, check its company, active status, configuration type, and the saved type selection. Configurations belonging to companies you have not imported cannot attach to an MSPilot client. If sync warns that configurations were skipped, complete their missing name, company, or type in Manage and sync again. Valid devices still update. MSPilot preserves existing discovered devices for affected companies until it can safely identify the missing records. If you see **Devices from RMM**, Manage device import is disabled because the RMM supplies inventory. Review the RMM connection rather than granting more Manage permissions. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.