> ## 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 iboss to Neo

> Create an API key in a client's iboss console and save it in Neo

You connect iboss once for each client that uses it. Each connection takes the client's iboss cloud API host and an API key from the client's own iboss account.

## 1. Create the API key in iboss

<Steps>
  <Step title="Open the client's account">
    Sign in to the iboss admin console and open the client's account (from your MSSP console, open that customer). An API key belongs to the account it is created in.
  </Step>

  <Step title="Add an API key">
    Type "system administrators" into the console's search bar, open **System Administrator Management**, go to the **API Keys** tab and click **Add API Key**. Give it a prefix such as `neo-agent` and an expiry date (at most five years).
  </Step>

  <Step title="Choose its RBAC group">
    The key's RBAC group decides what Neo can read and change in this account. The **Default RBAC Group** gives full administrative access; for less, create an RBAC group with the areas your agents need (for example web reporting and policy layers).
  </Step>

  <Step title="Allow Neo's IP addresses">
    Under **Source IP Login Restrictions**, add each address on the [IP Whitelisting](/integrations/ip-whitelisting) page as a CIDR ending in `/32`, and press **Enter** after each. iboss refuses every request from an address that is not on this list.
  </Step>

  <Step title="Copy the key">
    Save the key and copy its full value, which ends with the account number.
  </Step>
</Steps>

<Warning>
  Neo stops working for this client when the key expires, is disabled or is removed. Before the expiry date, extend it in iboss or save a new key in Neo. Neo's agents never rotate the key.
</Warning>

## 2. Add the key in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open [**Integrations** → **iboss**](https://dashboard.neoagent.io/integrations?open=iboss), under Security.
  </Step>

  <Step title="Pick the client">
    In **Customer**, choose the client this iboss account belongs to. The client must be on your **Companies** tab. For a second client, click **Add customer**.
  </Step>

  <Step title="Enter the host and paste the key">
    Enter the **Cloud API Host**, `api.ibosscloud.com` for most accounts, paste the **API Key**, and click **Save settings**. Neo checks the key against iboss before saving, so a wrong key, or a missing IP address on the key, is rejected straight away.
  </Step>
</Steps>

## 3. Turn iboss on per agent

<Steps>
  <Step title="Open the agent's integrations">
    Open the agent in the Neo Dashboard and go to its **Integrations** tab, or ask your Neo Support Agent to add iboss to it.
  </Step>

  <Step title="Pick an access profile">
    Under **iboss**, pick an access profile, or set each permission group by hand.

    | Profile | What it does |
    | - | - |
    | **Read Only** | Reads logs, reports, policies and settings; changes nothing |
    | **Helpdesk** | Reads everything; adding or removing an allow or block list entry asks a technician |
    | **IT Admin** | Changes policies, groups, locations, connectors, DLP, users and devices on its own; list entries, firewall rules and SSL decryption changes ask a technician |
    | **Full Automation** | Every supported call without approval, except the changes under Safety Controls that always ask |
  </Step>
</Steps>

<Tip>
  For temporary exceptions, give the agent the **Trigger or Schedule Workflow** tool: it schedules its own run to remove the entry when the time is up.
</Tip>


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