Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Connect Adobe product profile inventory. Read product profiles and returned membership while keeping resource quotas separate from purchased seats. Current availability: Read adapter implemented; company authorization and successful live sync required.

Before you start. An authorized company administrator with Vendor licenses management permission and an approved provider data-use scope. The company’s protected integration vault. Use a dedicated provider application; never put credentials in a KB, video, chat or source file.

Step 1. In Adobe Developer Console, create an OAuth Server-to-Server User Management API integration for the company organization. A system administrator must authorize its setup.

Step 2. Use the User Management scopes openid, AdobeID and user_management_sdk. Enter the organization ID ending @AdobeOrg, client ID and client secret in Connect.

Step 3. Save the encrypted connection in Companies > company > Vendor licenses. Choose Sync now in production after provider authorization. Dev and QA isolate external operations. Review the recorded sync result and compare the snapshot with the provider console.

Step 4. Review the product profiles and the active organization users returned by UMAPI. Administrative indicators come from documented group types, not guessed group-name prefixes.

Step 5. Open Inventory scope for the returned profile quota. A quota may describe a resource allowance and profile memberships can overlap; Connect therefore leaves purchased capacity and spare seats unknown.

Step 6. The reader limits each groups/users collection to five pages per sync to stay bounded. If more pages are required, arrange a scheduled export integration before claiming a complete larger inventory.

Now verify the result. An unknown Adobe identity type stays unknown. Duplicate profile names fail the join rather than assigning users to an ambiguous product. A successful company sync is required before describing the connection as healthy; an available adapter alone is not a connected account. Check a second company and a view-only account: neither can change this company’s credentials or lifecycle state. Pause, Resume and Trash affect only the local connection. Resume waits for a separate Sync action; no vendor user or license is modified.

If you get stuck. 401 or 403: check credential expiry, the selected provider organization and the exact required permissions. Do not grant broad write access merely to bypass a failed read. A failed or incomplete provider response preserves the last complete snapshot. Review the error, correct the connection and explicitly retry. On a 429 rate-limit response, wait for the provider’s retry window before another manual sync. Large inventories can require a separately designed scheduled export; the current bounded sync does not commit partial results.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.