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

> Get a client's ELMO API credentials and save them in Neo

You connect ELMO once for each client that uses it, with two values from that client's ELMO: a Client ID and a Client Secret.

## 1. Get the API credentials from ELMO

**1. Make sure the client's ELMO has API access**

ELMO turns on API access per ELMO account. If the client's ELMO has no API management, ask the client's ELMO account manager to turn it on.

**2. Create the API credentials**

A Company Admin of the client's ELMO creates the API credentials in ELMO's API management. Give the person who creates them a security profile that allows API access management.

**3. Copy the two values**

Copy the **Client ID** and the **Client Secret** shown with them. Keep them for the next step.

## 2. Add the credentials in Neo

**1. Open Integrations**

In the Neo Dashboard, open [**Integrations** → **ELMO**](https://dashboard.neoagent.io/integrations?open=elmo), under HR & Business Apps.

**2. Pick the client**

In **Customer**, choose the client this ELMO company belongs to. The client must be on your **Companies** tab. For a second client, click **Add customer**.

**3. Save the credentials**

Paste the Client ID and the Client Secret, and click **Save settings**. Neo gets a token from ELMO and reads one user before saving, so a wrong value is rejected straight away.

> [!WARNING]
>
> If a Company Admin deletes or replaces the API credentials in ELMO, save the new ones here. Neo loses access to that client's ELMO until you do.

ELMO allows each set of credentials about one API request a second, with short bursts of 10, and 5,000 requests a day. Neo sends at most 60 requests a minute for each client and does not count the day's total, so a busy scheduled agent can still reach ELMO's daily limit. ELMO then refuses calls until the next day, and the agent reports what it could not do.

## 3. Turn ELMO on per agent

**1. Open the agent's tools**

Open the agent in the Neo Dashboard, go to its **Tools & Settings** tab and click **HR & Business Apps**.

**2. Pick a preset**

Expand the **ELMO** block and pick one of its **Presets**, or set each permission group by hand.

| Preset | What it does |
| - | - |
| **Read Only** | Reads users, onboarding users and the org structure; changes nothing |
| **Helpdesk** | Every change to users, onboarding users or the org structure asks a technician |
| **IT Admin** | Creates, activates and deactivates users and changes the org structure on its own |
| **Full Automation** | Every supported call in every group without approval |

In every preset, updating a user, an onboarding user or a user's personal contact details asks a technician. Read Only, Helpdesk and IT Admin keep Personal Contact Details, Employment & Payroll, Leave and Recruitment off. Turn one on only for an agent that needs it.

For a change of manager form, **Read Only** is enough on the ELMO side. The agent also needs the Microsoft Graph permission groups User Management (to set the manager) and SharePoint & OneDrive (to update the client's list).


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