Skip to main content
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

1

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 with such an account, and pick the client’s organization at the top right.
2

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.
3

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).

​
2. Add the credential in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations → Adobe Admin Console, under Identity & Workspace.
2

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.
3

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.
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.

​
3. Turn Adobe on per agent

1

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.
2

Pick an access profile

Under Adobe Admin Console, pick an access profile, or set each permission group by hand.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.

​
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.