User and Product Management in the Admin Console

Information about users and groups, Adobe ID account types (personal IDs, enterprise IDs, and federated IDs), and group mapping (single sign-on) in the Marketing Cloud.

Note: The Admin Console (formerly, Enterprise Dashboard) is a user management feature for the Creative Cloud, Document Cloud, and Experience Cloud solutions. Content on this page is intended for Experience Cloud solution administrators. You can find broader information articles about the Admin Console and identity management at Enterprise Help & Support. Existing Analytics administrators who manage users in Analytics > Admin > User Management should continue to do so. A migration for existing Analytics group management to the Adobe Admin Console is in the planning stages.

On this page:

Access the Admin Console

All Adobe user, group, and entitlement management features performed in the Adobe Admin Console (Administration > Launch Admin Console).

Note: If you do not see the Administration link in the Marketing Cloud top menu, you are not a Marketing Cloud system administrator for the displayed organization.

The Admin Console page displays solutions (product contexts) to which your organization has access.

Element Description
Overview

The Admin Console page displays solutions (product contexts) to which your organization has access.

Products

Displays product names, licenses, number of users, and configurations for each product. Each product represents a product solution that you own, as well as available core services.

User Management

Displays users who are members of your organization, as well as the products and services to which they are entitled. You can add users and assign users to groups. See Manage users and groups in the Marketing Cloud.

Identity

You can manage domains, access requests, and password requirements.

Tools

You can upload a company logo, specify admin permissions, and generate an API to programmatically manage users.

Support

Get help and support for the Admin Console.

Organizations

Organizations are displayed in the user's Accounts menu, and you can switch organizations as needed.

Manage Product Configurations

On the Products page, you can access the product configurations to which your organization has access. Create a product configuration and apply user or group permissions.

For example, an Analytics administrator can create a product configuration that provides access to Activity Map.

See Add product configurations for information about adding product configurations, and adding users and administrators to the configuration.

About Adobe IDs - Personal, Enterprise, and Federated IDs

Adobe uses an underlying identity management system to authenticate and authorize users for single sign-on. Adobe currently supports three identity or account types, each using the email address as the user's name.

You can use enterprise IDs, federated IDs with single sign-on, and Adobe IDs in the same enterprise deployment. For example, use Adobe IDs for users who may use other Adobe product and services. Use enterprise or federated IDs for users where you want to strictly manage their accounts.

Before you create enterprise IDs or federated IDs, consider the impact on existing users. It is possible that users have an Adobe ID with email addresses from your domain to access products and services from Adobe.

Descriptions of Identity Types

Identity Type Description

Adobe ID

End users create, own, and manage their Adobe IDs, and Adobe performs the authentication. End users create, own, and manage their Adobe IDs and maintain complete control over files and data associated with their ID. They can purchase additional products and services from Adobe using this ID. Administrators can invite these users to join a Marketing Cloud organization, as well as remove them from an organization. However, users cannot be locked out from their Adobe ID accounts, and the accounts cannot be deleted or taken over by the administrator.

Use Adobe IDs in the following scenarios:

  • You want to enable users to create, own, and manage their identities.
  • You want to allow users to purchase or sign up for other Adobe products and services.
  • If you expect users to use other Adobe services, such as Acrobat.com and Digital Publishing Suite, which do not currently support enterprise or federated IDs.
  • If users already have Adobe IDs and associated data, such as files, fonts, or settings.
  • In educational setups, where students can retain their Adobe ID after they graduate.
  • If you have contractors and freelancers who do not use your corporate email address.

Enterprise ID

Enterprise ID is created, owned, and managed by an organization. Adobe hosts the enterprise ID and performs authentication, but the organization maintains the enterprise ID. End users cannot sign up and create an enterprise ID, nor can they sign up for additional products and services from Adobe using an enterprise ID.

Administrators create an enterprise ID and issue it to a user. Administrators can revoke access to products and services by taking over the account, or by deleting the enterprise ID to permanently block access to associated data.

Enterprise IDs are recommended in the following scenarios:

  • If you need to maintain strict control over apps and services available to a user.
  • If you need emergency access to files and data associated with an ID.
  • If you need the ability to completely block or delete a user account.

Federated ID

Federated ID is created and owned by an organization. It is linked to the enterprise directory via federation. The organization manages credentials and processes single sign-on via a SAML2 identity provider.

Federated IDs are recommended in the following scenarios:

  • You want to provision users based your organization's enterprise directory.
  • You want to manage user authentication.
  • You need to maintain strict control over apps and services available to a user.
  • You want to allow users to use the same email address to sign up for an Adobe ID.

For more about identity management, see Managing Identity Types.