Directory & Identity

Adobe

Browse and manage Adobe users, groups, and product profiles for one Adobe organization through the User Management API.

Dex connects to Adobe Enterprise User Management (UMAPI) so admins can look up users, review user groups and product profiles, and run user/group action commands for one Adobe organization. Each connection is a single Adobe Organization authenticated with per-tenant OAuth Server-to-Server credentials - there is no shared MSP master credential. The Organization ID is stored as a credential and forced into every request path by the platform, so admins never need to supply or guess it. Write actions (create, update, remove) are gated behind approval.

Start free →See Dex Live

What Dex does with Adobe

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Look up a single Adobe user by email or username in the connected organization
List Adobe UMAPI users for the connected org (paged, capped for readability)
Review Adobe user groups and product profiles for the connected org
Run UMAPI user/group action commands - create, update, or remove - with approval
Narrow a full user inventory by domain rather than enumerating the whole organization

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Look up the Adobe user dlevi@example.com and show their group memberships
>What user groups and product profiles exist in our Adobe org?
>List the Adobe users on the example.com domain
>Add jsmith@contoso.com to the Creative Cloud product profile

Policy actions

Every action Dex can take on Adobe is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`adobe_list_users`	List Adobe UMAPI users for the connected org (paged, 0-based)	—
`adobe_list_groups`	List Adobe user groups and product profiles for the connected org	—
`adobe_get_user`	Get one Adobe user by email or username in the connected org	—
`adobe_action`	POST UMAPI user/group action commands (create/update/remove) for the connected org	approval

How to configure Adobe

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In Adobe Developer Console, create an OAuth Server-to-Server credential for the User Management API and enable that API on the project.
2
Copy the Client ID (also used as the x-api-key) and the Client Secret from the same credential.
3
From the Adobe Admin Console, note your Organization ID in the form HEX@AdobeOrg.
4
In Dex, enable the Adobe integration and paste the Client ID, Client Secret, Organization ID, and optional IMS host.
5
Dex mints a token against Adobe IMS and validates the connection with a live read before saving.

Credentials required

client_id: Adobe Developer Console Client ID for the OAuth Server-to-Server credential (also used as x-api-key)
client_secret: OAuth Server-to-Server Client Secret from the same Developer Console credential (secret; treat like a password)
org_id: Adobe Organization ID from Admin Console in the form HEX@AdobeOrg (not a secret; forced into every request path by the platform)
ims_host: Optional Adobe IMS host (default ims-na1.adobelogin.com; only ims-*.adobelogin.com hosts are allowed)

Requirements

•An Adobe enterprise organization with the User Management API enabled on an OAuth Server-to-Server credential
•The Organization ID from the Admin Console in the form HEX@AdobeOrg
•Per-tenant credentials only - each connection is one Adobe Organization; there is no shared MSP master credential
•Read scope covers users, groups, and product profiles; write actions are limited to UMAPI user/group action commands