> ## Documentation Index
> Fetch the complete documentation index at: https://support.configview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Adobe (Admin Console) setup

Configview reads your Adobe organisation (Creative Cloud, Acrobat, Adobe Express and the other products managed in the Adobe Admin Console) through the **Adobe User Management API** (`https://usermanagement.adobe.io/v2/usermanagement`), using an **OAuth Server-to-Server credential** from the Adobe Developer Console. Configview sends only `GET` requests (plus the token request to Adobe's sign-in service). It never creates, changes or removes a user, group or licence.

You will end up with **3 required secrets** (`ADOBE_CLIENT_ID`, `ADOBE_CLIENT_SECRET` and `ADOBE_ORG_ID`) in Configview when setup is complete.

> **Scope of this integration today.** Configview answers "who holds an Adobe licence, who administers the organisation, and which seats are wasted": every user with identity type (Adobe ID, Enterprise ID or federated), status and country, the product profiles (licences, including Adobe Express) and user groups they belong to, licence quota against members assigned per product profile, and the admin roles (system, deployment, support, product, user group). It does **not** read files, creative content, passwords or usage. The API exposes **no last-login field and no audit-log pull endpoint**, so neither is collected (see Known gaps).

***

## What you need

* An Adobe organisation managed in the Admin Console (Adobe Enterprise or Teams with the Admin Console)
* A **system administrator** of that organisation. Only a system administrator can create the integration.
* Access to the Adobe Developer Console (`https://developer.adobe.com/console`)

***

## Step 1: Open the Adobe page in Configview

Open Configview in a second browser tab and leave it open:

`https://{companyname}.configview.com/admin/integrations/adobe`

***

## Step 2: Create the credential

1. In the Developer Console choose the right organisation (top right), then **Create new project**
2. Click **Add API**, pick **User Management API** and continue
3. Choose the **OAuth Server-to-Server** credential type (the older Service Account / JWT credential no longer works)
4. Name the credential and save the project
5. On the credential page copy the **Client ID**, click **Retrieve client secret** and copy it, and copy the **Organization ID** (it looks like `XXXXXXXXXXXXXXXXXXXXXXXX@AdobeOrg`)
6. In the Configview tab paste them into `ADOBE_CLIENT_ID`, `ADOBE_CLIENT_SECRET` and `ADOBE_ORG_ID` under **Credentials** and save

**Least privilege.** The User Management API credential is created by a system administrator and acts as a technical account for the organisation. Configview only calls read endpoints. Adobe does not offer a read-only variant of the credential, so keep the secret in Configview only and rotate it from the credential page if it is ever exposed (up to two secrets can exist, so rotating needs no downtime).

***

## Step 3: Connect and verify

1. Click **Connect**. Configview creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Users** | Every user: email, name, country, identity type, status, groups, admin roles. |
| **Groups and product profiles** | Product profiles with product name, licence quota and member count; user groups; admin groups. |
| **Group members** | Who is in which product profile, user group or admin group. |

2. Click **Verify now**. The health check reads the three secrets, requests an access token and reads one page of groups.

If a check fails:

* **Token refused.** The client ID or secret is wrong, or the credential has no User Management API attached.
* **401.** The token or organization ID is wrong.
* **403.** The credential has no access to this organization, or the organization is being migrated.
* **429.** Adobe throttled the request. Configview waits for `Retry-After` and retries.

***

## Data Tables

Each table has a `run_at` column and keeps only the newest run.

| Table | Source | Key Columns |
| - | - | - |
| `adobe_users` | `GET /users/{orgId}/{page}` | user\_id, email, domain, country, status, user\_type, group\_list, admin\_group\_list, is\_admin, is\_system\_admin |
| `adobe_groups` | `GET /groups/{orgId}/{page}` | group\_id, group\_name, group\_type, product\_name, license\_quota, license\_unlimited, member\_count |
| `adobe_group_members` | `GET /users/{orgId}/{page}/{groupName}` | group\_name, group\_type, user\_id, email, user\_type, status |

***

## Things worth knowing

**Adobe Express and other licences are product profiles.** A product profile is a licence: it names the product (`product_name`, for example Adobe Express), carries a `license_quota` (a number or UNLIMITED) and lists its members. Quota minus `member_count` is the number of unused seats. Group names are not fixed by Adobe, so Configview filters on `group_type` and `product_name`, not on a name.

**Identity types.** `federatedID` and `enterpriseID` are owned by the company. `adobeID` is a personal account that belongs to the person; the company cannot reclaim its files. Configview lists them.

**Technical accounts.** The user list leaves out technical accounts (for example this credential itself), so counts can be lower than the total shown in the Admin Console.

**Rate limit.** Adobe throttles per client: 25 requests a minute on the user lists and 5 a minute on the groups list, plus a shared limit for the whole application. Configview paces itself at 20 and 4 a minute and waits as long as Adobe's `Retry-After` header says. Group members need one paged request series per group, so a large organisation with many groups takes a while. Adobe asks integrations to sync no more than about twice an hour; the daily default is well within that.

## Known gaps

* **No last login.** The API has no last-active field. The Admin Console shows it in its own screens only, so Configview cannot tell a user who never signs in from an active one.
* **No audit log.** Adobe delivers the Admin Console audit log (about 90 days, OCSF format) through Adobe I/O Events, a registered journal or webhook, not a plain endpoint. It is not collected yet.
* **No usage or consumption.** Product usage, Stock credits and Firefly generative credits are not exposed by this API.
* **Indirect assignment.** The user list shows product profiles reached through a user group as well as direct ones; the member list shows each group's own members.

## What isn't collected

* Passwords, tokens and the credential's secret beyond what you paste into Configview
* Files, designs, PDFs, libraries and any creative content
* Usage and consumption data
* Deprecated `adminRoles` (the same information is in the admin groups)


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