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

> Make a key pair, get Plaud Enterprise API access for your Plaud Team workspace, and save the credentials in Neo

You connect Plaud once at the MSP level, for your Plaud Team workspace. Only a Plaud Team admin can set up Enterprise API access.

## 1. Make a key pair

On a computer with OpenSSL, make an RSA key pair:

```bash theme={null}
openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:2048 -out private_key.pem
openssl pkey -in private_key.pem -pubout -out public_key.pem
```

`public_key.pem` goes to Plaud. `private_key.pem` goes only into Neo: keep it out of email and chat, because anyone who has it can read your workspace's recordings.

## 2. Get Enterprise API access from Plaud

Ask Plaud for Enterprise API access for your workspace and send them `public_key.pem`. The Enterprise API is in private beta, so Plaud turns it on per workspace. Plaud sends back:

* a **Client ID**
* the **API host**: `https://api.plaud.ai` for a US workspace
* for some workspaces, such as a Japan workspace, a **token issuer**, and sometimes a **key ID**

## 3. Ask your team for consent

Once access is on, Plaud asks each team member in the Plaud app, the next time they open it, whether their own recordings can be read through the Enterprise API. Neo reads Team files straight away, and a member's own recordings only after that member says yes. Tell your team to accept, so their meetings reach your PSA.

## 4. Add the credentials in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Plaud card, under Customer Success.

**2. Save the credentials**

Paste the **Client ID**, the whole **Private key** file (from `-----BEGIN PRIVATE KEY-----` to `-----END PRIVATE KEY-----`) and the **API host**. Fill in **Token issuer** and **Key ID** only if Plaud sent them. Click **Save settings**. Neo signs in to Plaud and reads your workspace before saving, so a wrong key or a workspace without Enterprise API access is rejected straight away.

Neo signs a short-lived token request with your private key and calls only the API host Plaud gave you, which must be on `plaud.ai`.

## 5. Turn Plaud on per agent

Open the agent, go to the Integrations section, and pick an access profile for the Plaud block, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Recordings & Summaries** | Disabled, Read Only | Each recording's title, time, length, who made it, and its AI summaries. |
| **Transcripts** | Disabled, Read Only | Every word said in a recording. Off in the Read Only and Helpdesk profiles. |
| **Workspace & Members** | Disabled, Read Only | Your workspace and its members, used to find who made a recording. |

See [Plaud API](https://docs.neoagent.io/agents/tools/sales/plaud-api.md) for the profiles and what the agent can read.

## Troubleshooting

| Problem | What to do |
| - | - |
| Saving says Plaud refused the client id and key | Check that the private key is the pair of the public key you sent Plaud, and that the API host is the one Plaud sent |
| Saving says the workspace read failed, private beta | Plaud has not turned on Enterprise API access for the workspace yet. Ask Plaud |
| A team member's meetings never appear | That member has not accepted the consent notice in the Plaud app, or recorded to a private file. Ask them to open the Plaud app and accept |
| A recording is logged on no company | Its title and summary name no client, or name one that matches several companies. Put the client's name in the recording's title |


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