> ## 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 Adobe Admin Console to Neo

> Create a User Management API credential in a client's Adobe organization and save it in Neo

You connect Adobe once for each client that uses it, with three values from that client's Adobe organization: a Client ID, a Client Secret and the Organization ID.

## 1. Create the API credential in Adobe

<Steps>
  <Step title="Sign in as a System Administrator">
    Only a System Administrator of the client's Adobe organization can create a credential for the User Management API. Sign in to the [Adobe Developer Console](https://developer.adobe.com/console) with such an account, and pick the client's organization at the top right.
  </Step>

  <Step title="Create a project with the User Management API">
    Click **Create new project**, then **Add API**, choose **User Management API**, and pick **OAuth Server-to-Server** as the credential type. Save the project.
  </Step>

  <Step title="Copy the three values">
    Open the project's **OAuth Server-to-Server** credential. Copy the **Client ID**, click **Retrieve client secret** and copy it, and copy the **Organization ID** (it ends in `@AdobeOrg`).
  </Step>
</Steps>

## 2. Add the credential in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open [**Integrations** → **Adobe Admin Console**](https://dashboard.neoagent.io/integrations?open=adobe), under Identity & Workspace.
  </Step>

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

  <Step title="Save the credential">
    Paste the Client ID, the Client Secret and the Organization ID, and click **Save settings**. Neo checks them against Adobe before saving: a wrong Client ID or Client Secret, or an Organization ID that is not the credential's, is rejected straight away.
  </Step>
</Steps>

<Warning>
  If someone rotates the client secret or deletes the project in the Adobe Developer Console, save the new values here. Neo loses access to that client's Adobe organization until you do.
</Warning>

## 3. Turn Adobe 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 Adobe to it.
  </Step>

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

    | Profile | What it does |
    | - | - |
    | **Read Only** | Reads users, licences, user groups and admins; changes nothing |
    | **Helpdesk** | Creates and removes users and assigns and frees licences, asking a technician before each change |
    | **IT Admin** | Every change on its own, except granting an admin role and changing a sign-in, which ask a technician |
    | **Full Automation** | Every supported call without approval |

    An onboarding agent needs **Users** and **Product Access & Licences**. An offboarding agent that removes the user from the organization needs **Users** only; add **Product Access & Licences** when it keeps the account and frees licences instead. A licence report needs both as Read Only.
  </Step>
</Steps>

## Before an agent creates users

Adobe creates a user in a domain the client's organization has claimed or trusts in the Admin Console (**Settings** → **Identity**). The agent creates new staff with the same account type as their colleagues: a Federated ID when the client signs in to Adobe through Microsoft Entra ID or another identity provider, an Enterprise ID when Adobe hosts the sign-in.


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