CX Enterprise atlas / Shared Services & Administration | Platform & administration
ProductGenerally available
Shared Services & AdministrationPlatform & administration
Also known as User management and product licenses, User and product management, Adobe Admin Console for enterprise
Adobe's central administration service at adminconsole.adobe.com, shared by CX Enterprise, Creative Cloud and Document Cloud. Administrators set up organizations, identity and single sign-on, add users and user groups, delegate admin roles, grant product access and permissions through product profiles, and manage contracts, storage, security settings, audit logs and support cases. Sign-in runs on the Adobe Identity Management System (IMS).
Also known as Organizations and accounts, Adobe organizations
An organization is the company-level container that holds users, groups, products, identity settings and single sign-on across all CX Enterprise applications. A company can have several organizations, and one administrator can belong to many.
Integrates with: Organization switcher, Federated ID sign-in links
Last checked 2026-09-30
Also known as IMS Org ID, Adobe Org ID
The unique identifier of a provisioned organization: a 24-character alphanumeric string ending in @AdobeOrg. It appears in the Admin Console URL and in the user information panel (Ctrl+i) of CX Enterprise, and support and API integrations ask for it.
Last checked 2026-09-30
Also known as Business ID
When one email address is used for several Adobe plans and at least one is a business plan, Adobe creates a separate profile for each plan, each with its own storage. A Business profile belongs to a plan provided by an organization, including Experience Cloud, and its content can be controlled by the plan administrator. A Personal profile belongs to an individual plan.
Last checked 2026-09-30
Also known as Organization name change, Default email language, Notes for users
Organization-level settings: the organization's display name (system admins can change it themselves since March 2026, including in Global Admin Console hierarchies), the default language of Adobe emails sent to users, and custom notes shown to users.
Last checked 2026-09-30
Also known as GAC, Adobe Global Admin Console
A separate console that nests many Admin Console organizations into a hierarchy with a root organization, like an organization chart. Global administrators create child organizations, allocate licences to them, and set policies, while system administrators run each organization day to day. Aimed at multinationals, government agencies and education consortiums. Access is requested through a support case.
Last checked 2026-09-30
Also known as Organization hierarchies, Child organizations
Create, delete and move child organizations under any organization in the tree. A new child inherits its parent's policies and locks and system administrators, the parent's directory users, and its sharing and password policies and security contacts. Each policy controls whether that item is inherited.
Last checked 2026-09-30
Also known as Global administrator, Global viewer
Two roles specific to the Global Admin Console. A global admin is transitive: it covers every organization below the one it is assigned on, including ones created later. Global admins can also assign the standard roles (system, product, product profile, user group, deployment, support and storage admin) in each organization. Global viewers can see and export data but not change it.
Last checked 2026-09-30
Also known as Policy locks
Allow/deny policies on each organization, such as claiming domains, adding Adobe ID, Enterprise ID or Federated ID users, and inheritance of admins, users and sharing settings. A global admin can lock a policy so that admins lower in the tree cannot change it.
Last checked 2026-09-30
Named sets of policy values and lock states, stored with an organization. Global admins apply them to any child organization to configure policies the same way across the hierarchy.
Last checked 2026-09-30
Also known as Allocate products to child organizations, Pooled storage allocation
Splits licences bought on ETLA contracts between organizations in the hierarchy, along with pooled storage quotas for organizations on the new storage model. Since July 2026 products can be allocated from several paid ETLA contracts, with reporting that adds them up. Some Digital Experience products, such as Workfront, Experience Manager and Experience Platform, cannot be allocated.
Last checked 2026-09-30
Global admins create, edit and delete product profiles and user groups in any organization they cover. They cannot add end users, only administrators.
Last checked 2026-09-30
Also known as Pending jobs, Review Pending Changes
Changes in the Global Admin Console are staged, then reviewed and submitted as a job from the Job Execution tab. Staged edits are kept for 30 days, and the tab shows 30 days of job history with errors and warnings.
Last checked 2026-09-30
Also known as Multi-organization license assignment reports, Global audit logs
Reports across the hierarchy: licence assignment reports for chosen organizations and products by month or year, audit logs of global-admin actions in all organizations for the last 90 days, and downloads of exported data.
Last checked 2026-09-30
Export the hierarchy, organization details and product allocations as JSON, CSV or XLSX, edit the data offline, and import it back as staged changes.
Last checked 2026-09-30
Also known as Identity and single sign-on, Identity management settings
How an organization's users authenticate: identity types, directories and claimed domains, single sign-on with an identity provider, domain enforcement, trust between organizations and authentication policies. Configured in Settings > Identity and Settings > Privacy and Security.
Last checked 2026-09-30
Also known as Adobe identity types
Admin Console supports three account types. They differ in who owns the account and its data, who handles authentication, and which security controls apply.
Last checked 2026-09-30
An account created and managed by the individual user, with Adobe handling authentication. It can be used on unverified, public or trusted domains, and the user keeps control of their personal data.
Last checked 2026-09-30
An account created, owned and managed by the organization on a verified domain. Adobe authenticates it, and the organization sets the password policy.
Last checked 2026-09-30
An organization-owned account that authenticates through the organization's identity provider over SAML 2.0 or OpenID Connect. It is the only identity type that supports single sign-on, and the identity provider controls its passwords and multi-factor rules.
Last checked 2026-09-30
Also known as Identity directories, Federated directories
A directory holds an organization's Enterprise ID or Federated ID users, their domains and the authentication setup, much like an LDAP or Active Directory container. Admins can move domains between directories and move directories between Admin Consoles. Encrypted directories and directories in a trust relationship need special migration steps.
Last checked 2026-09-30
Also known as Claim domains, Verify domain ownership
The organization proves it owns an email domain by adding an adobe-idp-site-verification DNS TXT record. Only one organization can own a domain, and its subdomains are then validated automatically.
Last checked 2026-09-30
Lets users with an email address on a verified federated domain create their own Federated ID when they first sign in through single sign-on, without being provisioned first. It works together with automatic assignment rules and product requests.
Last checked 2026-09-30
Also known as Directory trust, Trusted directories, Set up organization via directory trust
Lets other organizations (trustees) create users on a domain owned by another organization, while authentication stays with the owner's identity configuration. Owners approve, reject or revoke trustee access requests, and approval covers all current and future domains in the directory.
Last checked 2026-09-30
Also known as Domain enforcement for restricted authentication
Stops users from creating personal Adobe IDs with company email addresses and routes all sign-ins through the organization's identity system. It can require existing Adobe ID users to change their email address, and it is on by default for new directories. An exception list lets named addresses, such as service accounts or emergency admin accounts, keep an Adobe ID.
Last checked 2026-09-30
Also known as FGA, Federated guest accounts
Lets an enterprise add users with any email address, including agency and vendor staff on domains it doesn't own, as its own federated users, under the same SSO enforcement as employees. Guest accounts are kept apart from internal accounts, and guests switch accounts from the organization menu. It supports AEM Assets as a Cloud Service, AEM Sites, Adobe Express, GenStudio and Workfront, and became generally available in July 2026.
Last checked 2026-09-30
Also known as SSO, Set up identity with SSO
Federated directories connect Adobe to the organization's identity provider, so users sign in with their company credentials and the identity provider enforces authentication policy. There are three setup paths: Microsoft Entra ID, Google, or any other SAML 2.0 provider.
Last checked 2026-09-30
Also known as Other SAML providers, Okta SSO, Microsoft AD FS SSO, Shibboleth SSO
Federation with any SAML 2.0 identity provider, such as Okta, Ping Identity, Shibboleth, Microsoft AD FS or RapidIdentity. The Admin Console and the provider exchange metadata (ACS URL and entity ID), and admins can map attributes and a default country.
Last checked 2026-09-30
Also known as Azure AD SSO, Azure Active Directory connector, Microsoft Azure connector
Creates a federated directory against Microsoft Entra ID (formerly Azure Active Directory), either in a few steps over OpenID Connect from the Admin Console or through a SAML app configured in the Azure portal.
Last checked 2026-09-30
Also known as Google Workspace SSO, Google connector
One workflow that creates the directory, claims domains verified in Google and configures a Google SAML app, so users sign in to Adobe with their Google Workspace credentials.
Last checked 2026-09-30
Also known as Identity provider initiated login, SAML RelayState
Users open Adobe web apps straight from their identity provider's app launcher. A SAML RelayState URL chooses the landing app (Adobe Home by default, or Experience Cloud Home, Express, Workfront, Experience Manager or Marketo Engage). Released in February 2026.
Last checked 2026-09-30
Also known as Authentication settings (enterprise)
Organization-wide sign-in policies under Settings > Privacy and Security. They apply to Enterprise ID and Adobe ID users, while Federated ID users follow the identity provider's rules.
Last checked 2026-09-30
Also known as Password protection levels
Low, medium or high password complexity levels, applied to future password creation and resets, plus automatic lockout after repeated failed sign-ins.
Last checked 2026-09-30
Also known as 2-step verification
System admins can require two-step verification for all Enterprise ID and Adobe ID users, so users cannot turn it off.
Last checked 2026-09-30
Also known as Restrict product access by IP address, IP allowlist
An allowlist of up to 150 public IPv4 addresses or CIDR ranges. Users outside it can't sign in to Adobe products or switch to a business profile. It applies across every directory and product in the console.
Powers: IP access list enforcement
Last checked 2026-09-30
Also known as Adobe IMS, Adobe Identity Management Services, Adobe Identity Management
The Adobe service behind all Adobe sign-in and API authorization. It authenticates Adobe ID, Enterprise ID and Federated ID accounts, issues OAuth 2.0 access tokens to users and applications, and checks product entitlements from the organization's product profiles. CX Enterprise applications, Admin Console and Adobe APIs all sign users in through IMS.
Last checked 2026-09-30
Also known as IMS user authentication, 3-legged OAuth
The OAuth 2.0 authorization-code flow, in which a user signs in with IMS and consents before an app reads or changes that user's data. It covers web app, single-page app and native app credentials.
Last checked 2026-09-30
Also known as OAuth Server-to-Server credential, IMS client credentials
The client-credentials grant for applications that act on the organization's data without a user present. Its IMS APIs fetch access tokens and list, add and remove client secrets for rotation. The credential's product profiles in Admin Console decide what it can reach.
Last checked 2026-09-30
Also known as JWT credentials, Service Account (JWT)
The former certificate-based server-to-server credential. New ones could not be created after 1 May 2024, and existing ones stopped working when their certificates expired after 1 January 2025.
Replaced by OAuth Server-to-Server authentication
Last checked 2026-09-30
Also known as Enterprise Web App credential
A credential for Adobe Technology Partner Program apps. A customer administrator grants consent and assigns product profiles, and then the partner app can read or change that organization's data. Admins can revoke consent at any time.
Last checked 2026-09-30
Also known as Users, Manage users and groups
Adding, organizing and removing the users, groups and developers of an organization, one at a time, in bulk, or synced from a corporate directory.
Last checked 2026-09-30
Also known as Manage users individually
The Users tab, for creating, editing and removing individual accounts (up to ten at a time) and for assigning them products, product profiles and user groups. It includes an inactive-users view, searchable by email, username or name since July 2026, and CSV export of the user list.
Last checked 2026-09-30
Also known as Manage users in bulk, Manage multiple users
Adds, edits or removes users, and assigns their product profiles and admin rights, from a CSV file of up to 25,000 rows. Results appear under bulk operation results, and a summary is emailed to the admin.
Last checked 2026-09-30
Named sets of users that receive product profiles and user roles together. Groups can be created one at a time or by CSV, can have their own user group admins, and can be synced from Active Directory, Entra ID or Google organizational units.
Last checked 2026-09-30
All Enterprise ID and Federated ID accounts in each directory, including users removed from the organization. Admins permanently delete accounts, and their assets, from here.
Last checked 2026-09-30
Also known as Edit user identity type, Migrate existing users
Converts users from Adobe ID to Enterprise ID or Federated ID by CSV, or between Enterprise ID and Federated ID by moving their domain to another directory. Creative Cloud assets move automatically, and other entitlements may need a manual migration.
Last checked 2026-09-30
Also known as Manage developers, Manage API credentials, API credentials
Admins add developers to product profiles that include API access, which lets them create credentials in Adobe Developer Console. Those credentials are then tied to product profiles, whose permissions every API call inherits. Moving a credential from a test profile to a production profile, or removing it, controls what an integration can reach.
Last checked 2026-09-30
Also known as User provisioning connectors
Automated provisioning that keeps Admin Console users and groups in line with the organization's directory. A directory managed by a sync can no longer be edited by hand or by another sync method.
Last checked 2026-09-30
Also known as UST, Adobe User Sync Tool, Adobe User Sync, user-sync.py
An open-source command-line tool that customers run on their own server. On a schedule, it copies users and group memberships from Active Directory or another LDAP directory into the Admin Console, calling the User Management API with OAuth Server-to-Server credentials. It supports Federated ID and Enterprise ID users.
Last checked 2026-09-30
Also known as Azure Sync, Azure AD Sync
SCIM provisioning from Microsoft Entra ID into any federated directory, whatever its identity provider. Admins choose which users and groups to send and map the attributes. Removing users from the sync scope disables them rather than deleting them.
Last checked 2026-09-30
SCIM provisioning from the Google Admin Console into a federated directory. Google organizational units become Admin Console user groups, and it works whichever provider handles authentication.
Last checked 2026-09-30
Also known as UMAPI, User Management REST API
The REST API for the Admin Console. Enterprise customers use it to create, update and remove users, manage user groups and product profile membership, and read organization, group and profile data from their own provisioning systems. It authenticates with an OAuth Server-to-Server credential. Adobe promises at least six months' notice before breaking changes.
Integrates with: Developer Console
Last checked 2026-09-30
A batch endpoint that runs user commands (create, update, remove, add to or remove from groups and profiles) and user group commands (create, update, delete, manage members).
Last checked 2026-09-30
Read APIs that return one user, all users in the organization (paged), users in a group, and the groups and product profiles of the organization.
Last checked 2026-09-30
Read APIs for user groups, a single group and a group's members.
Last checked 2026-09-30
APIs that list products and product profiles, read a profile and its users, and update a product profile.
Last checked 2026-09-30
Also known as umapi-client.py
An open-source Python library that wraps the User Management API.
Last checked 2026-09-30
Also known as Administrative roles, Admin roles and hierarchy
A hierarchy of administrative roles for splitting management work across an organization. Only system admins can assign or change other admin roles. Roles can be combined.
Last checked 2026-09-30
Also known as System admin
Full control of the organization: identity and authentication, users, products, contracts and billing, security settings and all admin role assignments.
Last checked 2026-09-30
Also known as Contract admin
Introduced in 2024. Views the contracts assigned to it, adds or removes other contract admins, assigns those contracts' products to users, and buys more licences.
Last checked 2026-09-30
Also known as Product admin
Manages specific products: creates their product profiles, adds users and groups to them, and appoints product profile admins, other product admins and group admins for those products.
Last checked 2026-09-30
Also known as Product profile admin
Manages the users, groups, permissions and product roles in the product profiles assigned to it. It does not get product access itself unless it is also added as a user.
Last checked 2026-09-30
Also known as User group admin, Group admin
Manages membership of the user groups assigned to it.
Last checked 2026-09-30
Also known as Deployment admin
Creates and deploys desktop app packages and updates from the Packages tab.
Last checked 2026-09-30
Also known as Support admin, Basic support administrator, Product support administrator
A non-administrative role that can see, create and manage support cases, including CX Enterprise cases filed in Experience League. It comes in two forms: basic, for all products except Marketo Engage, and product support admin, for specific Marketo Engage instances. Only system admins can grant it.
Last checked 2026-09-30
Also known as Storage admin
Manages the organization's business storage: consumption by active and inactive users, content transfers, shared folders, retention policy, asset settings and content logs.
Last checked 2026-09-30
Also known as Admin Console user roles, Roles
Organization-level roles, under Users > Roles, that control what users and groups can do inside their Adobe apps. They are separate from admin roles and product profiles. System and product admins assign them, preferably to groups.
Last checked 2026-09-30
Also known as Predefined user roles
Built-in roles. Member is the default for everyone and covers Express add-ons, templates, social publishing, Firefly and partner models, and Projects. Admin developer covers Developer Console projects and access to the Admin Console audit log event stream. There are also Adobe Express roles (add-on user, application manager, template manager, social publishing manager) and the Firefly user and partner model user roles, added in March 2026.
Last checked 2026-09-30
System admins combine up to 100 permissions from the available permission sets (Adobe Express, Express add-ons, Firefly, Firefly Custom Models, partner models, admin APIs and I/O event providers) into their own roles. Role changes are recorded in the audit log.
Last checked 2026-09-30
Also known as Product licenses, License management
The Products tab and related tools that turn purchased licences into user access: product profiles and their permissions, licensing methods, provisioning status, access automation, trials and app integrations.
Last checked 2026-09-30
Also known as Product profile
The containers that grant access. Each product has one or more profiles defining the services, permissions and usage limits for the users, groups, developers and API credentials in it. A user in several profiles gets all of their access combined. Adobe recommends no more than 8,000 profiles per organization, and no more than 4,000 per user, for Experience Cloud products.
Last checked 2026-09-30
Also known as Permission items, Add permissions to a product profile
Per-product permission items, grouped into sections, that a profile grants to everyone in it. For CX Enterprise apps these are items such as Analytics report suites and tools, or Target properties and roles. With Auto-include, a section also picks up permission items Adobe adds later.
Last checked 2026-09-30
Also known as Optional services, Manage services in the Admin Console
Optional services, such as Adobe Express, Firefly, Acrobat AI features, PDF Services and Frame.io, that can be switched on or off per product profile. Core services are always on.
Last checked 2026-09-30
Profile-level rules (User Managed, Restricted, or Enforce Auto-update) that decide whether users can install and update Creative Cloud desktop apps themselves.
Last checked 2026-09-30
Also known as Named User Licensing, Shared Device Licensing
Named User Licensing, the default, ties a licence to a user identity and gives access to Adobe-hosted services. Shared Device Licensing ties Creative Cloud desktop licences to lab or classroom machines.
Last checked 2026-09-30
A per-user column on each product that shows whether an assigned licence is actually in effect (Completed or No access), with causes such as expired licences, a shortage of seats, or overuse blocked in a Global Admin Console hierarchy.
Last checked 2026-09-30
Settings under Products > Product access automation that let users obtain licences without an admin assigning each one.
Last checked 2026-09-30
Also known as Automatic product assignment, Product Access URLs
Rules that immediately grant a product profile to eligible users, meaning all users or those in chosen directories and domains, when they request access in an Adobe app or open a shareable Product Access URL. Products that include API access also make the user a developer.
Last checked 2026-09-30
Also known as Product access requests
Users request a product, with a business justification, from Creative Cloud, Express, Firefly, Acrobat, Stock, Acrobat Sign or Developer Console. System admins approve or deny the request in the Admin Console, and unanswered requests expire after 60 days.
Last checked 2026-09-30
System admins on an active ETLA can start eligible product trials, each as a separate trial contract, and special offers that are added to existing contracts. Users can be allowed to start the trial themselves, and trials can later be converted to paid licences.
Last checked 2026-09-30
Also known as Manage app integrations, App integration access policy
System admins approve third-party apps from Adobe Exchange that can reach organization content. Access can be allowed for all users, for chosen users and groups, or for no one, either organization-wide or per app. Admins can also revoke consent that users have granted.
Integrates with: Exchange
Last checked 2026-09-30
Also known as Admin Console for CX Enterprise, Experience Cloud product administration
How CX Enterprise applications use the Admin Console. Admins provision users and product profiles there, and each application's permissions (for example Analytics, Target, Campaign, Workfront, Marketo Engage and Commerce) sit in its profiles. Experience Platform and its apps (Real-Time CDP, Journey Optimizer, Customer Journey Analytics, Mix Modeler) instead take their detailed roles, sandboxes and labels from the Permissions interface at experience.adobe.com, once a user has product access in the Admin Console.
Integrates with: Access control, Access control, Access control
Last checked 2026-09-30
Also known as Admin Tool, Experience Cloud Admin Tool, View user details (Admin Tool)
A read-only view at experience.adobe.com that lists every CX Enterprise user and product profile. For users it shows application access, roles and last sign-in (kept for 365 days). For each profile it shows users, groups, developers, integrations and admins, with detailed permissions and resources.
Last checked 2026-09-30
Also known as Contracts and renewals, Account tab
The Account tab, where system and contract admins manage the organization's Adobe agreements.
Last checked 2026-09-30
Also known as Manage your contracts and agreements
Shows each Enterprise, VIP, VIP Marketplace or Teams contract with its ID, status, end date, products and quantities, contract admins and Adobe account manager. Admins can rename contracts and, on some contract types, buy more licences.
Last checked 2026-09-30
Also known as Enterprise Term License Agreement, ETLA
The phases an expiring Enterprise Term Licensing Agreement goes through (notification, grace period, post-grace and inactive) and what admins and users can still do in each. After the grace period, products are removed from users.
Last checked 2026-09-30
Also known as VIP renewals and compliance, Value Incentive Plan
The yearly renewal window for Value Incentive Plan enterprise licences, with licence counts shown as total, used, need renewal, need payment and no access.
Last checked 2026-09-30
Adding a new contract to an existing Admin Console so it replaces an expiring one. Identity, users and storage are kept, but users and admins must be reassigned to the new contract's product profiles.
Last checked 2026-09-30
Also known as Reports and logs, Admin Console Insights
The Insights tab, which holds the organization's reports and logs for system administrators.
Last checked 2026-09-30
Also known as Admin Console audit log, Admin audit log
A searchable, downloadable record of organization-level changes to settings, admins, users and products, with event, object, affected user, admin and IP address, kept for 90 days. Changes made inside a product, such as creating an Analytics report suite, are not included.
Last checked 2026-09-30
Also known as Admin Console audit logs via API, Adobe Admin Console Audit Logs
Since March 2026, audit log events can also be streamed through Adobe I/O Events into customer storage or security tools. Only system admins and users with the Admin developer role can add the provider to a Developer Console project.
Last checked 2026-09-30
Reports of user actions (create, update, move and more) on organization-owned Creative Cloud and Document Cloud assets for the past 90 days. They can be downloaded or streamed through Adobe I/O Events, and cover users in directories the organization owns.
Last checked 2026-09-30
Reports that compare assigned licences with purchased quantities per product, for planning deployments and licence use.
Last checked 2026-09-30
Also known as Manage storage and assets, Storage tab
Management of the organization-owned cloud storage used by Creative Cloud, Document Cloud and Express content.
Last checked 2026-09-30
Also known as Enterprise storage, Business storage, Enterprise Storage Model
Cloud storage owned by the organization and pooled across all purchased entitlements. Users can go beyond their own share while the pool lasts, and admins can view, manage and reclaim the content.
Last checked 2026-09-30
Shared, organization-owned project spaces for collaborating on assets with internal and external people. Admins oversee all projects even if they are not invited.
Last checked 2026-09-30
Also known as Reclaim assets from a user
When a user is removed, their stored content can be transferred directly to another user, keeping folder structure, versions and sharing. It can also be held until later or deleted.
Last checked 2026-09-30
Moves a user's supported content from a personal Adobe ID account to their new Enterprise ID or Federated ID account, with the user's consent.
Last checked 2026-09-30
Also known as Content retention policy for inactive users, Content retention policy for WIP content
Automated deletion schedules. Folders of removed (inactive) users can be kept permanently or for a period between 30 days and 10 years (February 2026). Lifecycle rules for work-in-progress Creative Cloud Projects can be set through the Adobe Admin APIs (June 2026).
Last checked 2026-09-30
Also known as Settings, Security settings
Organization-wide settings for encryption, content sharing and incident contacts, set by system administrators in the Settings tab.
Last checked 2026-09-30
Also known as Manage encryption, Encryption key management
An Adobe-generated key unique to the organization that encrypts its Creative Cloud and Document Cloud files. Admins can revoke and restore it to cut off access during an incident. Once enabled it is permanent. It does not cover files stored in Experience Cloud, Frame.io videos, Lightroom or Behance.
Last checked 2026-09-30
Also known as Asset settings, Sharing restrictions, Authorized domains
Three levels for sharing company-owned assets outside the organization: no restrictions, no public links, or sharing only with the organization plus claimed, trusted and authorized domains.
Last checked 2026-09-30
Also known as Content Credentials for enterprise content, Connected Identities access
Controls whether users can apply Content Credentials in Adobe apps and include identity details from their Connected Identities profile. Access to the Connected Identities page is switched separately.
Last checked 2026-09-30
Also known as Privacy and security contacts
The Data Access Administrator, Security Administrator and Data Protection Officer contacts that Adobe notifies of security or privacy incidents and data subject access requests.
Last checked 2026-09-30
Also known as Deploy apps and updates, Packages tab
The Packages tab, where deployment admins build or download Creative Cloud and Acrobat desktop install packages (self-service or managed) and get the Remote Update Manager and Adobe Update Server Setup Tool.
Last checked 2026-09-30
Also known as Support tab, Enterprise Support
Access to Adobe Customer Care for system and support admins: support cases, Expert Sessions and help resources. CX Enterprise support cases are moving to Experience League as the single entry point, and they use the same Admin Console support admin role.
Last checked 2026-09-30
Also known as Create and manage support cases, Experience League support tickets
Admins create, track and manage cases with P1 (critical) to P4 (minor) priority, from the Admin Console Support tab or, for Digital Experience products, from Experience League. P1 production outages are also handled by phone.
Integrates with: Product Support Agent
Last checked 2026-09-30
30-minute how-to calls with Adobe Customer Care, booked from Support > Expert Sessions at least 24 hours ahead.
Last checked 2026-09-30