# Private Marketplace
<a name="private-marketplace-current"></a>

With Private Marketplace, you control what users in your organization can procure from AWS Marketplace. Administrators can provide customized procurement experiences with curated catalogs of approved products to different audiences in your organization. Private Marketplace integrates with [AWS Organizations](https://aws.amazon.com/organizations), a service that helps you manage all your AWS accounts in one place.

You can create multiple experiences to govern your entire organization, AWS organizational units (OUs), or AWS accounts and adjust your procurement controls as your business needs change. If you update your organization structure within AWS Organizations, Private Marketplace updates the governance accordingly. You can also add company branding to each experience with a custom name and messaging that gives users more information about their procurement experience.

After you set up governing experiences using Private Marketplace, users in your organization can buy and deploy only vetted products that comply with your organization's policies and standards. They can browse the entire AWS Marketplace catalog and request additional products. Administrators can view user requests and approve or decline these requests. Private Marketplace publishes Amazon EventBridge events when users create requests and when administrators approve or decline these requests. To streamline the approval process and receive timely updates, administrators and users can set up email notifications for these events. For more information, see [Private Marketplace notifications](configuring-notifications.md).

**Note**  
The legacy version of Private Marketplace will be deprecated on March 17, 2026. To use the current version, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. To check integration status, see [Viewing Private Marketplace settings](view-private-marketplace-settings.md).

## Products governed by Private Marketplace
<a name="products-governed-by-private-marketplace"></a>

All products that require AWS Marketplace subscriptions will be governed by Private Marketplace. Keep in mind the following important exceptions and considerations:
+ As customers are already entitled to products whose EULAs are governed by the AWS Customer Agreement or other agreement with AWS governing use of AWS services, you cannot control subscriptions to such products using Private Marketplace. Hence, such products are not included in the list that you approve within your Private Marketplace experiences.
+ If your organization already has subscriptions to products in AWS Marketplace, Private Marketplace will not block usage from these existing subscriptions. Users will not be blocked from launching new instances from existing subscriptions. Private Marketplace will only block new subscriptions or changes to existing subscriptions to products that are not approved in the experience that is governing the user.
+ Private Marketplace does not control what can be deployed in AWS accounts. If you want to control what can be deployed including products that are automatically entitled.
+ For the latest information on access to Amazon Bedrock models, see the [Amazon Bedrock User Guide](https://docs.aws.amazon.com/bedrock/latest/userguide/what-is-bedrock.html).

# Private Marketplace for administrators
<a name="for-administrators"></a>

Private Marketplace restricts administrative actions to the organization's management account or a member account that is a delegated administrator for the service. An administrator must have the AWS Identity and Access Management (IAM) permissions included in the [AWSPrivateMarketplaceAdminFullAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSPrivateMarketplaceAdminFullAccess.html) managed policy.

This section describes how to manage Private Marketplace through the AWS Marketplace console. You can also manage Private Marketplace using the AWS Marketplace Catalog API. For more information, see [Working with Private Marketplace](https://docs.aws.amazon.com/marketplace-catalog/latest/api-reference/private-marketplace.html) in the *AWS Marketplace API Reference*.

# Prerequisites
<a name="prerequisites"></a>

To use Private Marketplace, you need one or more AWS accounts managed in AWS Organizations with all features enabled.
+ Create an organization using [Tutorial: Creating and configuring an organization](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_tutorials_basic.html).
+ If you have an existing organization with only consolidated billing feature, enable all features using [Enabling all features for an organization with Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_org_support-all-features.html).

## Integration with AWS Organizations
<a name="integration-with-aws-organizations"></a>

Before you can start creating Private Marketplace experiences and using them to control what your users can purchase from AWS Marketplace, you must enable trusted access in Organizations and create a service-linked role.

### Trusted access in AWS Organizations
<a name="trusted-access-in-aws-organizations"></a>

You must enable trusted access in Organizations to make Private Marketplace a trusted service that can perform tasks in your organization and its accounts on your behalf. For more information, see [Using AWS Organizations with other AWS services](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_integrate_services.html).

Trusted access in Organizations is essential for Private Marketplace to keep the governance in sync with changes in your Organizations structure. If you disable trusted access, it turns off Private Marketplace governance completely. All your audiences will be disassociated from Private Marketplace experiences, and all users in your organization will be able to procure any product from AWS Marketplace.

**Important**  
We **strongly recommend** enabling trusted access using AWS Marketplace console which will also create the required service-linked role. If you enable trusted access using the Organizations console or API, it will not create the service-linked role. You must first create the service-linked role using AWS Identity and Access Management (IAM).
Do not disable trusted access unless you are certain that you do not require Private Marketplace governance for your entire organization. There are less disruptive ways to turn off or update governance for parts of your organization. For more information, see [Updating experience configuration](manage-experiences.md#update-experience-configuration) and [Managing audience associations for an experience](manage-experiences.md#manage-audience-associations-for-an-experience).

### Service-linked role for Private Marketplace
<a name="service-linked-role-for-private-marketplace"></a>

You must create the `AWSServiceRoleForPrivateMarketplaceAdmin` service-linked role in the management account. It includes the permissions that are required to access data from Organizations and manage Private Marketplace resources on your behalf. For more information about the service-linked role, see [Using roles to configure Private Marketplace in AWS Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/using-service-linked-roles-private-marketplace.html).

**Note**  
If you have been using Private Marketplace without Organizations integration or using it to govern individual accounts that are not in Organizations, you will not be able to use the new features launched since February 16, 2024.  
To use the latest features, an administrator in the Organizations management account must create an integration for Private Marketplace. This is a prerequisite to use the AWS Marketplace console for managing Private Marketplace. The website for managing Private Marketplace will be deprecated on March 17, 2026. The integration is also required to use the features for organizational unit (OU) support and user request notifications noted in the following topics:  
[AWS Marketplace now supports managing Private Marketplace catalogs for organizational units](https://aws.amazon.com/about-aws/whats-new/2024/02/aws-marketplace-private-marketplace-catalogs-organizational-units/)
[AWS Marketplace now supports notifications for Private Marketplace](https://aws.amazon.com/about-aws/whats-new/2024/10/aws-marketplace-notifications-private-marketplace/)

# Getting started
<a name="get-started"></a>

To get started, enable Private Marketplace by creating a service-linked role and enabling trusted access in AWS Organizations. You can perform this action only from the management account of your organization using a role or user with AWS Identity and Access Management (IAM) permissions in the [AWSPrivateMarketplaceAdminFullAccess](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-security-iam-awsmanpol.html#security-iam-awsmanpol-awsprivatemarketplaceadminfullaccess) managed policy. This policy has all permissions required to enable, configure, and manage Private Marketplace.

## Enabling Private Marketplace
<a name="enable-private-marketplace"></a>

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Settings**.

1. Choose **Edit integrations** in Private Marketplace settings.

1. Choose **Enable trusted access across your organization**.

1. Choose **Create a Private Marketplace service-linked role for this account**.

1. Choose **Create integration**.

You can't undo this integration from the AWS Marketplace console. Use the IAM console to delete the service-linked role, or the Organizations console to disable trusted access.

**Note**  
You can also enable Private Marketplace by visiting the **Get started** page under **Private Marketplace** in the navigation pane in the AWS Marketplace console.

## Registering a delegated administrator
<a name="register-a-delegated-administrator"></a>

After enabling Private Marketplace in your organization, you can register a trusted account as a delegated administrator. This reduces the work for the management account administrator by letting the delegated administrator account create and manage Private Marketplace experiences in your organization. Additionally, Organizations gives a delegated administrator account read-only access to view organization structure, memberships, and policies. For more information, see [Delegated administrator for AWS services that work with Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_integrate_delegated_admin.html).

**To register a delegated administrator**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Settings**.

1. Choose **Register new administrator** in Private Marketplace settings.

1. Enter the AWS account ID that you want to register as a delegated administrator. The account must be a member of your organization.

1. Choose **Create a Private Marketplace service-linked role for this account**.

1. Choose **Register**.

You can remove the delegated administrator at any time and register a different account, if needed.

# Private Marketplace concepts
<a name="private-marketplace-concepts"></a>

This topic explains some of the key concepts for Private Marketplace.

## Experience
<a name="experience"></a>

A Private Marketplace experience is a curated catalog of approved products with custom branding that allows you to control what users in your organization can procure from AWS Marketplace. To govern users, you associate the audience containing the user with a **Live** experience. Audiences can be the entire organization, organizational units (OUs), or accounts in your Organizations. You can create multiple experiences with specific procurement controls for different audiences.

### Experience status
<a name="experience-status"></a>

The status of an experience determines if the experience is available to govern users. An experience can have two statuses:
+ **Live –** The experience is active and will govern users in the audience that the experience is associated with. Admins can continue to make updates and manage products.
+ **Not live – ** The experience is created but not yet available to govern users. Admins can continue to make updates and configure settings. It can be set to **Live** when ready for users.

### Experience mode
<a name="experience-mode"></a>

The mode of an experience determines whether the experience can be updated and used to govern users. An experience can have two modes:
+ **Active –** Active experiences can be updated and used to govern users. You can continue to make updates and manage products in active experiences.
  + When an active experience is **Live** and associated with an audience, all users in that audience will be governed by the experience.
  + When an active experience is **Not live**, it will not govern any users even when it is associated with an audience.
+ **Archived –** Archived experiences cannot be modified and used to govern users. An archived experience has to be reactivated, if you want to use it again. Archiving an experience can be thought as soft deleting an experience and preventing active use with ability to reactivate and use it again, if required.

## Audience
<a name="audience"></a>

Each hierarchical unit in Organizations — organization, organizational units (OUs), or accounts — can be an audience for an experience. You can think of audiences as nodes in the organization structure of Organizations hierarchy. Read more about [Organization structure](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html#organization-structure) in the AWS Organizations user guide.

With Private Marketplace, you can provide specific procurement experiences to different audiences in your organization based on their business needs. You do this by associating an experience with an audience.

Experiences flow down through the audience hierarchy — when applied at a higher level, all lower levels inherit it automatically. To override an inherited experience, you can associate the audience at a lower level with a different experience.

## Associated audience
<a name="associated-audience"></a>

An experience can be directly associated with multiple audiences collectively termed as **associated audiences**.

When an experience is **Live**, it will govern the associated audiences. Users in the associated audiences will only be allowed to procure products approved in the experience. The associated audiences will not inherit any product approvals from experiences associated at a higher level in the organization hierarchy.

When an experience is **Not live**, it will not govern the associated audiences. The associated audiences will inherit product approvals from the first **Live** experience associated at a higher level in the organization hierarchy.

## Governing experience
<a name="governing-experience"></a>

An audience will only be governed by a single experience at a point in time. This is referred to as the **governing experience**. When an experience is governing an audience, users in that audience will only be allowed to procure products approved in the experience. The governing experience is determined by the status of the experience, its associated audiences, and the organization hierarchy.

The governing experience and its audience relationship can be **Associated** when an audience is directly associated with an experience and **Inherited** when it inherits from an experience at a higher level. Read more about [Governance hierarchy](#governance-hierarchy) to understand how experience inheritance works.

## Default governing experience
<a name="default-governing-experience"></a>

The default governing experience governs the entire organization, excluding organizational units and accounts that are directly associated with other **Live** experiences. It is recommended to configure a default governing experience to govern your entire organization. The default governing experience should be curated with products that you approve for all users in your organization.

To configure a default governing experience for your organization, create an experience, select the products that you approve for procurement in your organization, and associate your organization root as the audience for the experience. After the experience is set to **Live**, users in your organization will only be allowed to procure AWS Marketplace products that you approved in the default governing experience. For more information, see [Configuring Private Marketplace](configure-private-marketplace.md) for steps to create and configure an experience.

If you have organizational units (OUs) or accounts with specific procurement needs, you can create additional experiences with different sets of approved products and associate them to these audiences.

## Governance hierarchy
<a name="governance-hierarchy"></a>

Private Marketplace provides hierarchical governance that is aligned with [Organizations hierarchy](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html#organization-structure). With Private Marketplace, you can create multiple experiences and associate them to your entire organization, AWS organizational units (OUs), or AWS accounts. This allows you to scale your procurement governance as your business needs evolve. If you update your organization hierarchy within Organizations, Private Marketplace updates the governance accordingly.

Here are the different levels of audience associations and the effect for each. Note that the status of an experience is also a factor to determine the governance. An experience will govern an audience only when it is set to **Live**. The effects described below assume a **Live** experience. When an experience associated with an audience is **Not live**, the audience inherits the **Live** experience at the next higher level.
+ **Organization association –** When you associate an experience with the organization root, all OUs and accounts in the organization inherit the experience. All users in the organization will be governed by the experience and will only be allowed to procure products approved in the experience.
+ **OU association –** When you associate an experience with a specific OU, it does not inherit experiences set at higher levels in the hierarchy. Accounts that are directly under that OU or any child OU inherit the experience associated with that OU. Users in accounts that are directly under that OU or any child OU will be governed by the experience and will only be allowed to procure products approved in the experience.
+ **Account association –** When you associate an experience with a specific account, it does not inherit experiences set at higher levels in the hierarchy. Users in the account will be governed by the experience and will only be allowed to procure products approved in the experience.

In summary, the experience that is **Live** and closest to an account in the organization hierarchy takes effect and governs that account.

The following example explains how experiences in an organization govern different accounts:
+ An organization has a default experience that is live and applies to the entire organization. All accounts within the organization are restricted to procuring only the products approved in this default experience.
+ The finance department has its own unit experience that is live and associated with its Organizational Unit (OU). All accounts under this OU are limited to procuring only the products approved in the finance unit experience. They cannot access products available in the default experience.
+ An individual account, let's call it account A, has its own experience that is live and specifically associated with it. Users in account A can only procure products approved in the account A experience.
+ Another department, marketing, has a unit experience created but not yet live. It is associated with the marketing department's OU. However, since this experience is not live, the accounts under the marketing OU continue to be governed by the default experience. They can only procure products approved in the default experience, not those in the marketing unit experience, which is not live.

## Managed products
<a name="managed-products"></a>

As an administrator, you can approve or decline products from experiences in your organization. These are referred to as managed products. A product could be approved in one of your experiences to allow a subset of users to procure the product. The same product could be denied in another experience to not allow a different set of users from procuring it.

Private Marketplace provides multiple ways to manage products and visualize the product availability in experiences. See the following topics for more details:
+ [View governance details and manage products](view-governance-details.md)
+ [Managing products in an experience](manage-experiences.md#manage-products-in-an-experience)
+ [Approval status of a product in experiences](approval-status-of-a-product-in-experience.md)

# Configuring Private Marketplace
<a name="configure-private-marketplace"></a>

You can create multiple Private Marketplace experiences with specific procurement controls and customized branding for different audiences in your organization. Private Marketplace provides a multi-step wizard for creating and configuring experiences.

**Topics**
+ [Configuring an experience](#configure-experience)
+ [Selecting audiences (optional)](#select-audiences)
+ [Selecting products (optional)](#select-products)
+ [Customizing branding (optional)](#configure-branding-settings)
+ [Reviewing and creating an experience](#review-and-create-experience)

**Note**  
You can skip the optional steps and update the experience after creation. If you skip the optional steps and use the default settings, your experience will be live without any approved products or associated audiences. Until you associate an audience with this experience, it will not take effect and govern any users. When associated with an audience, it will not allow the users in the audience to procure any products from AWS Marketplace. It will allow users to submit product procurement requests.

## Configuring an experience
<a name="configure-experience"></a>

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

   1. In the navigation pane, choose **Dashboard** under **Private Marketplace**.

   1. Choose **Create experience**.

1. Specify experience details such as name and description. This is the internal name and description used by administrators to keep track of this experience. End users will not see these fields.

   1. Enter a name for your experience.

   1. (Optional) Enter a description for your experience.

1. (Optional) Update status and requests

   1. By default, the experience will be created with **Live** status and will take effect when it is associated with an audience. Choose **Not live** as **Experience status** if you do not want the experience to take effect immediately.

   1. By default, product requests are enabled which allows users to request more products to be added to the experience. If you do not want to allow users to request products, choose disabled for **Product procurement requests**.

1. (Optional) Specify tags:

   A tag is a custom attribute label that you assign to an AWS resource. Use tags to identify and organize your AWS resources. Many AWS services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related.

   1. Under **Tags**, choose **Add new tag**.

   1. Specify a key and, optionally, a value for the new tag.

## Selecting audiences (optional)
<a name="select-audiences"></a>

This step is optional. Note that your experience will not govern any users until it is set to **Live** status and associated with an audience.

**To select audiences**

1. Navigate the tree structure to choose your target audiences. The hierarchy shown reflects your organization structure, displaying the organizational units (OUs) and accounts that you manage in Organizations.

1. You can choose the entire organization, organizational units (OUs), or accounts. If you choose an audience that is directly associated with another experience, it will be disassociated from that experience and associated with the experience being created.

1. After making your selections, choose **Next**.

**Note**  
When choosing audiences, do not choose audiences at lower levels of a hierarchy if you have already chosen the audience at the higher level. Experiences flow down through the hierarchy - when applied at a higher level, all lower levels inherit it automatically. For example, if you have chosen an OU as the audience, do not choose the accounts under the OU, as they will automatically inherit the experience.
Choose an audience at a lower level only if you want to override its governance and not have it inherit from a higher level.

## Selecting products (optional)
<a name="select-products"></a>

This step is optional. If you do not select any products, your experience will be created with an empty catalog of approved products. If you use such an experience to govern users, they will not be allowed to procure any products from AWS Marketplace.

**To select products**

1. Choose the AWS Marketplace products you want to approve in the experience you are creating. Users in the audience associated with the experience will be allowed to subscribe to these products.

1. After making your selections, choose **Next**.

## Customizing branding (optional)
<a name="configure-branding-settings"></a>

This step is optional.

**To customize branding**

1. Enter a name and optional description for branding the experience you are creating. This name and description is shown to users on their **Your Private Marketplace** page. You can use these to provide details to your users about the Private Marketplace experience you are curating for them.

1. Choose **Next** to continue.

## Reviewing and creating an experience
<a name="review-and-create-experience"></a>

Review the settings for your Private Marketplace experience, and edit the settings as needed. When you are satisfied with your settings, choose **Create experience**.

Private Marketplace starts a Catalog API change set with multiple change types to create and set up the experience. You can track the changes in the **Change sets** page. Your experience is ready when the **CreateExperience** change set shows **Succeeded** status. Depending on your selections and the size of your organization, your change set can take up to a few hours to complete. To view the updates, refresh the console after processing is complete.

# Managing Private Marketplace
<a name="manage-private-marketplace"></a>

You can manage requests from users, approve additional products to their experiences, associate experiences with additional audiences, and update branding to match the needs of your organization.
+ To manage user requests, see [Managing user requests](manage-user-requests.md).
+ To bulk approve or decline products in multiple experiences, see [Bulk managing products](bulk-manage-products.md).
+ To update experiences, see [Managing experiences](manage-experiences.md).
+ To update governance for your users, see [Managing audiences](manage-audiences.md).

For all administration actions, Private Marketplace starts a Catalog API change set with one or more change types. For more information, see [Viewing changes](view-changes.md) for details on how to track changes.

# Managing user requests
<a name="manage-user-requests"></a>

If you enabled product procurement requests for the experiences in your organization, the end users can request for additional products to be approved. You will receive Amazon EventBridge events when a user requests a product. Refer [Private Marketplace notifications](configuring-notifications.md) for details on how you can configure email notifications for these events.

Product procurement request is enabled by default for an experience. You can view and edit this setting for each experience.

**To update the product procurement request setting for an experience**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Experiences** under **Private Marketplace**.

1. Choose the experience you want to update.

1. Choose **View details** to view a page with all the details for the experience.

1. Choose **Edit** from the **Details** tab.

1. Choose **Enabled** in **Product procurement requests** if you want to allow your end users to request products for procurement. Otherwise, choose **Disabled**.

1. Choose **Save changes**.

**To take action on pending user requests**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Approval requests** under **Private Marketplace**.

1. You can approve or decline multiple requests from this page by first selecting the check box next to the name of each request, and then choosing **Approve** or **Decline**.

1. To view more information about the request, choose **View details** for that request.

   1. You can view the reason for request, optional purchase order number, and the Private Marketplace experience associated with the user.

   1. You can choose to **Approve** or **Decline** and inform your buyer about your decision using an optional approver note.

   1. All users associated with the Private Marketplace experience will be allowed to subscribe to the products in the request, if approved. If declined, all users associated with the Private Marketplace experience will not be able to subscribe to the products in the request.

**Note**  
Private Marketplace supports two user experiences: AWS Console and the legacy website.  
To view and manage Private Marketplace in the AWS Marketplace Console, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. See [Enabling Private Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/private-marketplace-current.html#enable-private-marketplace) for details. For end users, administrators must also grant the new permissions listed in [AWSPrivateMarketplaceRequests](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-security-iam-awsmanpol.html#security-iam-awsmanpol-awsprivatemarketplacerequests).  
Product requests created using the legacy website will be available at [Private Marketplace](https://aws.amazon.com/marketplace/privatemarketplace). **Important:** The legacy website will be deprecated on March 17, 2026.

# Bulk managing products
<a name="bulk-manage-products"></a>

You can bulk approve or decline products in multiple experiences using the bulk update wizard. This wizard can be launched using the **Bulk update products** action on the dashboard. You can also get to this wizard by choosing products in the **Managed products** or the **All products** tables and choosing **Approve** or **Deny**.

**To bulk manage products**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Dashboard** under **Private Marketplace**.

1. Choose **Bulk update products**.

1. Choose the bulk update action **Approve** or **Deny**.

1. Find products and select them from the **All products** table.

1. Choose **Next**.

1. Choose experiences from the **Active experiences** table.

1. Choose **Next**.

1. Review the selections, and edit as needed.

1. When you are satisfied, choose **Update**.

# Managing experiences
<a name="manage-experiences"></a>

You can create an experience, view a list of all the experiences, and make edits from the **Experiences** page. This includes active and archived experiences.

**Topics**
+ [Viewing and updating experiences](#view-and-update-experiences)
+ [Updating experience configuration](#update-experience-configuration)
+ [Managing audience associations for an experience](#manage-audience-associations-for-an-experience)
+ [Managing products in an experience](#manage-products-in-an-experience)
+ [Customizing branding settings](#customize-branding-settings)

## Viewing and updating experiences
<a name="view-and-update-experiences"></a>

**Active experiences** can be used to govern users. You can continue to make updates and manage products in active experiences. When an active experience is **Live** and associated with an audience, all users in that audience will be governed by the experience. When an active experience is **Not live**, it will not govern any users even when it is associated with an audience.

**Archived experiences** cannot be modified and used to govern users. An archived experience has to be reactivated, if you want to use it again.

**To view and update experiences**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Experiences** under **Private Marketplace**.

1. Choose the experience you want to update.

1. Choose **View details** to view a page with all the details for the experience. To edit, see [Updating experience configuration](#update-experience-configuration), [Managing audience associations for an experience](#manage-audience-associations-for-an-experience), [Managing products in an experience](#manage-products-in-an-experience), and [Customizing branding settings](#customize-branding-settings).

1. Choose **Save changes**.

## Updating experience configuration
<a name="update-experience-configuration"></a>

You can update the internal name and description for the experience, the status, and admin mode. You can also enable or disable product procurement requests.

Setting the status of an experience that is associated with an audience to **Live** does not disrupt existing subscriptions and usage for the users in that audience. For example, it does not disrupt active Amazon Machine Images (AMIs) running on Amazon Elastic Compute Cloud (Amazon EC2) instances. When an experience is **Live** and associated with an audience, all new subscriptions or renewals are limited to the products approved in the experience.

**To edit the configuration for an experience**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Experiences** under **Private Marketplace**.

1. Choose the experience you want to update.

1. Choose **View details** to view a page with all the details for the experience. To edit the configuration, choose **Edit** on the **Details** tab.

1. Choose **Live** as **Experience status** if you want the experience to take effect and govern the associated audience. Choose **Not live** as **Experience status** if you do not want the experience to take effect or turn off the experience.

1. You can update the admin mode of an experience only when the status is **Not live**. Choose **Active** to allow edits or **Archived** to disallow edits.

1. Choose **Enabled** in **Product procurement requests** if you want to allow your end users to request products for procurement. If you choose **Disabled**, your end users will not be able to create product procurement requests.

1. You can edit the name and description for the experience in the **Experience details** section. This is the internal name and description used by administrators to keep track of this experience. End users do not see these fields.

1. Choose **Save changes**.

## Managing audience associations for an experience
<a name="manage-audience-associations-for-an-experience"></a>

You can associate additional audiences with an experience or disassociate existing audiences from the experience. This section describes how you can associate and disassociate audiences from an experience using the experience details page.

**To associate additional audiences with an experience**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Experiences** under **Private Marketplace**.

1. Choose the experience you want to update.

1. Choose **View details** to view a page with all the details for the experience.

1. Choose **Associated audiences** tab and **Add additional audience**.

1. Navigate the tree structure to choose your target audiences. The hierarchy shown reflects your organization structure, displaying the organizational units (OUs) and accounts that you manage in Organizations.

1. You can choose the entire organization, organizational units (OUs), or accounts. If you choose an audience that is directly associated with another experience, it will be disassociated from that experience and associated with the current experience.

1. After making your selections, choose **Next**.

1. Review the selected audiences to associate with the experience, and edit as needed.

1. When you are satisfied with your selections, choose **Associate**.

## Managing products in an experience
<a name="manage-products-in-an-experience"></a>

You can manage the products in an experience in multiple ways. This section covers how you can approve or decline products in a specific experience using its details page.

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Experiences** under **Private Marketplace**.

1. Choose the experience you want to update.

1. Choose **View details** to view a page with all the details for the experience.

1. Choose **Products** tab.

1. Select products and choose **Approve** or **Deny** from the **Managed products** or **All products** tables.

1. In the modal, choose **Approve** or **Deny** to approve or decline the products.

You can also approve or decline products from experiences in following ways:
+ From the dashboard – see [Bulk managing products](bulk-manage-products.md).
+ From a product detail page – see [Approval status of a product in experiences](approval-status-of-a-product-in-experience.md).

## Customizing branding settings
<a name="customize-branding-settings"></a>

You can brand an experience with a name and description so your users know they're procuring products in an approved catalog.

**To customize branding for an experience**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Experiences** under **Private Marketplace**.

1. Choose the experience you want to update.

1. Choose **View details** to view a page with all the details for the experience.

1. Choose **Branding settings** tab.

1. Update the name and description for branding the experience you are creating. This name and description is shown to users on their **Your Private Marketplace** page. You can use these to provide details to your users about the Private Marketplace experience you are curating for them.

1. Choose **Save changes** to update the branding.

# Managing audiences
<a name="manage-audiences"></a>

Each hierarchical unit in Organizations — organization, organizational units (OUs), or accounts — can be an audience for an experience. When you associate an audience with a **Live** experience, all users in the audience will be governed by the experience and only allowed to procure products approved in the experience.

You can view all the audiences in your organization from the **Audiences** page. This page opens with a **Hierarchy** view displaying the name and ID of the audience, its current governing experience, and association relationship. You can switch to **Organizational unit** to view the list of organizational units (OUs). You can also switch to **Account** to view the list of accounts.

The **Governing experience** column shows the experience governing the audience, and the **Relationship** column shows whether the audience is directly associated with the experience (**Associated**) or if it inherits the experience from a higher level (**Inherited**). Audiences showing **Inherited** status are grayed out because inherited relationships can't be disassociated.

**To create a new audience association**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Audiences** under **Private Marketplace**.

1. Choose **Create association**.

1. Navigate the tree structure to choose your target audiences. The hierarchy shown reflects your organization structure, displaying the organizational units (OUs) and accounts that you manage in Organizations.

1. You can choose the entire organization, organizational units (OUs), or accounts. If you choose an audience that is directly associated with another experience, it will be disassociated from that experience and associated with the experience you select.

1. After making your selections, choose **Next**.

1. Choose an active experience. If the experience you choose is **Not live**, it will not take effect and govern the audience you associate. You can update the experience status to **Live** in this wizard.

1. After making your selections, choose **Next**.

1. Review the selected audiences to associate with experience, and edit as needed.

1. When you are satisfied with your selections, choose **Associate**.

**To disassociate an audience from an experience**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Audiences** under **Private Marketplace**.

1. Navigate the tree structure to choose the audiences you want to disassociate.

1. Choose **Disassociate from experience**.

1. Note that OUs and accounts at a lower level which inherit the experience will also be affected when you disassociate. To avoid accidentally disassociating audiences from their currently associated experiences, provide additional consent by entering **confirm** in the text box.

1. Choose **Disassociate**.

**To edit an audience association**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Audiences** under **Private Marketplace**.

1. Navigate the tree structure to choose the audiences you want to edit associations.

1. Choose **Edit association**.

1. Choose an active experience. All audiences will be disassociated from any previous experiences they were associated with and associated with the selected experience.

1. If the experience you choose is **Not live**, it will not take effect and govern the audience you associate. You can update the experience status to **Live** in this wizard.

1. After making your selections, choose **Save changes**.

# Monitor Private Marketplace
<a name="monitor-private-marketplace"></a>

Private Marketplace provides multiple ways to visualize the governance controls you have configured in your organization.
+ To view integration status, see [Viewing Private Marketplace settings](view-private-marketplace-settings.md).
+ To view governance details, see [View governance details and manage products](view-governance-details.md).
+ To view the governance for different audiences in your organization hierarchy, see [Viewing governance hierarchy](view-governance-hierarchy.md).
+ To view the approval status of a product in your active experiences, see [Approval status of a product in experiences](approval-status-of-a-product-in-experience.md).
+ To track progress of changes and view an audit trail of Private Marketplace management actions, see [Viewing changes](view-changes.md).

# Viewing Private Marketplace settings
<a name="view-private-marketplace-settings"></a>

To use all features in Private Marketplace, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. This is a prerequisite to use the AWS Marketplace console for managing Private Marketplace. The integration is also required to use the organizational unit (OU) support and user request notification features discussed in the following What’s New posts:
+ [AWS Marketplace now supports managing Private Marketplace catalogs for organizational units](https://aws.amazon.com/about-aws/whats-new/2024/02/aws-marketplace-private-marketplace-catalogs-organizational-units/)
+ [AWS Marketplace now supports notifications for Private Marketplace](https://aws.amazon.com/about-aws/whats-new/2024/10/aws-marketplace-notifications-private-marketplace/)

**To view integration status**
**Note**  
You must use the management account of your organization with a role or user that has the `AWSPrivateMarketplaceAdminFullAccess` managed policy. Attempting to view the integration status from a non-management account or with insufficient permissions will result in a "Status cannot be determined" message.

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Settings**.

1. Check the values for **Service-linked role** and **Trusted access**:
   + If they show **Successfully created**, your organization has created an integration for Private Marketplace.
   + If they show **Not created**, your organization has not created an integration for Private Marketplace.

# View governance details and manage products
<a name="view-governance-details"></a>

The **Dashboard** page provides an overview of Private Marketplace governance in your organization, displaying the default governing experience, the number of live experiences, and all products that you are managing in the experiences in your organization.

**To view the governance details and manage products**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Dashboard** under **Private Marketplace**.

1. View the default governing experience that governs your entire organization and the total number of live experiences in the **Governance details** container. It is recommended to use a default governing experience. For more information, see [Default governing experience](private-marketplace-concepts.md#default-governing-experience).

1. View a list of all products that you have approved or declined in any of your experiences in the **Managed products** tab.

1. You can also create a new experience, bulk manage products, and view user requests using actions on the dashboard.

# Viewing governance hierarchy
<a name="view-governance-hierarchy"></a>

Private Marketplace uses the hierarchy that you configured in Organizations to provide hierarchical governance. An experience associated with an audience governs all audiences at a lower level unless the lower level audience is directly associated with another experience. When you make updates to the hierarchy in Organizations, the changes are automatically synchronized and the governance is updated in Private Marketplace. To visualize the governance, refer to following sections:
+ For a hierarchical view of all audiences in your organization, see [Audiences](#audiences-view).
+ For governance details of an organizational unit (OU), see [Organizational unit (OU) details](#organizational-unit-details).
+ For governance details of an account, see [Account details](#account-details).

**Topics**
+ [Audiences](#audiences-view)
+ [Organizational unit (OU) details](#organizational-unit-details)
+ [Account details](#account-details)

## Audiences
<a name="audiences-view"></a>

The **Audiences** page displays all the audiences in your organization with their governing experiences and association relationship. To view this page:

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Audiences** under **Private Marketplace**.

1. Use the default **Hierarchy** view to navigate down your organization structure viewing nested organizational units (OUs) and accounts.

1. To view the list of OUs, switch to **Organizational unit**.

1. To view the list of accounts, switch to **Account**.

1. Search for an OU or account using its exact ID.

The **Governing experience** column shows the experience governing the audience. The **Relationship** column shows whether the audience is directly associated with the experience (**Associated**) or if it inherits the experience from a higher level (**Inherited**).

An audience is governed by the first **Live** experience on its path to root. For more information, see [Governance hierarchy](private-marketplace-concepts.md#governance-hierarchy). If you have nested OUs with accounts at different levels, it may not be straight-forward to deduce the governing experience for an audience. To visualize this, you can use the details pages for OUs and accounts.

## Organizational unit (OU) details
<a name="organizational-unit-details"></a>

**To view the governance of an OU**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Audiences** under **Private Marketplace**.

1. Search for an OU using its exact ID. You can also navigate the tree structure to find your OU.

1. Choose the OU name.

1. In the OU details page, you can view the current associated experience and the governing experience for the OU. They will be the same if the current associated experience is **Live**. If the current associated experience is **Not live** or if there isn't one, the governing experience will be inherited from a higher level.

1. View the direct child accounts of the OU in the **Child accounts** table.

1. View the direct child OUs of the OU in the **Child organizational units** table.

## Account details
<a name="account-details"></a>

**To view the governance of an account**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Audiences** under **Private Marketplace**.

1. Search for an account using its exact ID. You can also navigate the tree structure to find your account.

1. Choose the account name.

1. In the account details page, you can view the current associated experience and the governing experience for the account. They will be the same if the current associated experience is **Live**. If the current associated experience is **Not live** or if there isn't one, the governing experience will be inherited from a higher level.

1. View the hierarchy from the account up to the organization root in the **Hierarchy view** container. View the governing experience at each level. You can visualize how the governing experience for the account is resolved by traversing the tree from leaf to root.

# Approval status of a product in experiences
<a name="approval-status-of-a-product-in-experience"></a>

The links in **Product** column of all tables in Private Marketplace opens a page with a brief description of the product and a link to view additional details in AWS Marketplace product page. It allows you to view and manage the product approval status in your active experiences.

**To view and manage product approval status**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Private Marketplace**.

1. From any of the sub-sections under **Private Marketplace**, choose a product link. This opens up a product detail page.

1. The **Active experiences** tab shows all active experiences and the product approval status for each.

1. Choose **Experiences with product approved** tab to view all experiences where the product is approved.

1. Choose **Experiences with product declined** tab to view all experiences where the product is declined.

1. From any of the tabs, select experiences and choose **Approve product** or **Decline product** to approve or decline the product from the selected experiences.

# Viewing changes
<a name="view-changes"></a>

Private Marketplace administration actions are performed using Catalog API. Actions are started as change sets with one or more changes to create or update Private Marketplace entities. For details, see [Working with Private Marketplace](https://docs.aws.amazon.com/marketplace-catalog/latest/api-reference/private-marketplace.html) in the *AWS Marketplace API Reference*.

All Private Marketplace change sets are listed on the **Change sets** page. This also includes change sets which are started by directly calling the APIs.

**To track the status of Private Marketplace administration actions**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Change sets** under **Private Marketplace**.

1. To view a specific change set, filter using the change set ID. You can also filter using status **Succeeded**, **Failed**, **In progress**, or **Cancelled**.

1. Select a change type and choose **View details** to view all the changes.

1. Choose a change to view its details including the JSON response.

   1. When a change fails, **ErrorCode** and **ErrorMessage** fields in the JSON response provides details about the cause.

   1. When a change succeeds, refresh the console to view the updates from the change.

## AWS CloudTrail logging
<a name="cloudtrail-logging"></a>

Change sets are only retained for a period of 90 days. You can use AWS CloudTrail to capture all calls to the AWS Marketplace Catalog API as events. If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon Simple Storage Service (Amazon S3) bucket. For more information, see [Logging AWS Marketplace Catalog API calls with CloudTrail](https://docs.aws.amazon.com//marketplace/latest/APIReference/logging-catalog-api-calls-with-cloudtrail.html) in the *AWS Marketplace Catalog API Reference*.

# Best practices
<a name="best-practices"></a>

## Create a default experience
<a name="create-default-experience"></a>

It is recommended to configure a default governing experience to govern your entire organization. This experience should be associated with your organization root as the audience and curated with products that you approve for all your users. This ensures that any organizational unit (OU) or account that does not have a directly associated experience will automatically fall under the governance of this default experience.

## Register a delegated administrator
<a name="register-delegated-admin"></a>

The management account administrator can register a trusted member account to act as a delegated administrator for Private Marketplace. This reduces the operational burden on management account administrator by allowing the delegated administrator account to create and manage Private Marketplace experiences in your organization. It also minimizes the need to use the management account for security reasons.

## Leverage organizational units
<a name="leverage-organizational-units"></a>

When you build your organization hierarchy, structure your OUs to align with your procurement needs. With this, you can apply specific procurement controls by creating and associating experiences with OUs. This reduces the maintenance overhead allowing you to seamlessly reuse your structure from AWS Organizations. When you make updates to the hierarchy in AWS Organizations, the changes are automatically synchronized and the governance is updated in Private Marketplace.

## Customize governance of individual accounts
<a name="customize-governance"></a>

If you have individual accounts with specific procurement needs that do not align with the overarching organization or OU experience, you can create and customize an experience and associate it with the individual account. This provides flexibility and allows you to tailor governance based on specific account requirements.

## Audit experiences regularly
<a name="audit-experiences"></a>

Conduct regular audits of experiences, their associated audiences, and the list of approved products to prevent outdated products from lingering in the approved list. Periodic reviews help maintain the relevance and security of the Private Marketplace setup.

## Monitor all administration actions
<a name="monitor-actions"></a>

Track all Private Marketplace management actions through the **Change sets** page. You can also use AWS CloudTrail. For more information, see [Viewing changes](view-changes.md).

## Manage your approved product list
<a name="manage-product-list"></a>

Ensure that all AWS Marketplace products currently in use across your organization are included in your Private Marketplace experiences. Though Private Marketplace does not disrupt existing subscriptions, any changes to the subscription or new subscriptions will be allowed only if the product is approved in the user's experience. It's also recommended to have a plan in place to discontinue use of unapproved products before turning on Private Marketplace governance.

## Archive experiences that you no longer need
<a name="archive-experiences"></a>

If you create multiple experiences for testing, it is recommended to archive them. This ensures a streamlined list of experiences that allows better oversight.

## Integrate with AWS Organizations
<a name="integrate-organizations"></a>

If you have been using Private Marketplace without Organizations integration or using it to govern individual accounts that are not in Organizations, you will not be able to use the new features launched since February 16, 2024. To use the latest features, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. This is a prerequisite to use the AWS Marketplace console for managing Private Marketplace. The website for managing Private Marketplace will be deprecated on March 17, 2026. The integration is also required to use the features for organizational unit (OU) support and user request notifications discussed in the following What’s New posts:
+ [AWS Marketplace now supports managing Private Marketplace catalogs for organizational units](https://aws.amazon.com/about-aws/whats-new/2024/02/aws-marketplace-private-marketplace-catalogs-organizational-units/)
+ [AWS Marketplace now supports notifications for Private Marketplace](https://aws.amazon.com/about-aws/whats-new/2024/10/aws-marketplace-notifications-private-marketplace/)

# Private Marketplace for users
<a name="for-users"></a>

Users who are being governed by a Private Marketplace experience will only be allowed to procure AWS Marketplace products that are approved in their experience. They may have the ability to request an administrator to approve additional products in their Private Marketplace experience.

This section describes the procurement experience for a user who is governed by a Private Marketplace experience.

# Your Private Marketplace experience
<a name="your-private-marketplace-experience"></a>

An Organizations administrator may have created and provided you with a Private Marketplace experience that controls what you can procure from AWS Marketplace.

**To check if you are being governed by a Private Marketplace experience**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Your Marketplace** under **Private Marketplace**.

1. **Your Marketplace** page shows the details of the Private Marketplace experience that an administrator has configured to control your procurement from AWS Marketplace. This page is always visible to all users, including administrators, under **Private Marketplace** in the navigation pane.

1. If you are being governed by a Private Marketplace experience, you will see a Welcome message and a description of your experience that has been set by your admin. You will be limited to purchasing products approved in your experience.

   1. Choose **Explore your Private Marketplace** to browse products. Products approved for purchase have the **Approved Product** label.

   1. If **Product procurement requests** shows **Enabled** status, you can request your administrator to approve additional products for procurement. If it is **Disabled**, you will not be able to create product procurement requests.

1. If your administrator has not configured a Private Marketplace experience for you, you will see "You're not being governed by a Private Marketplace experience". You can browse and procure any product in AWS Marketplace.

# Viewing approved products
<a name="viewing-approved-products"></a>

If you are being governed by a Private Marketplace experience, you will be limited to purchasing products approved in your experience.

**To view approved products**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Your Marketplace** under **Private Marketplace**.

1. Choose **Explore your Private Marketplace**.

1. This opens the **Discover Products** page with a pre-selected **Approved Products** filter for Private Marketplace. You can also directly access **Discover Products** page in the navigation pane.

1. When **Approved Products** filter for Private Marketplace is selected, it displays the list of products that have been approved for purchase by your admin.

1. If you uncheck **Approved Products** filter for Private Marketplace, you can view all AWS Marketplace products. Products that have been approved for your purchase will have an **Approved Product** label.

# Subscribing to a product
<a name="subscribing-to-a-product"></a>

As a user being governed by a Private Marketplace experience, you will be allowed to subscribe to all products that are approved in your experience by your administrator.

**To subscribe to products**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Discover Products**.

1. For users being governed by a Private Marketplace experience, **Discover Products** page displays the list of products that have been approved for purchase by your admin.

1. Choose any approved product to visit the product's details page. Refer [Using AWS Marketplace as a buyer](https://docs.aws.amazon.com/marketplace/latest/buyerguide/using-aws-marketplace-as-a-subscriber.html) for details to purchase and deploy the product.

# Subscribing to a private product
<a name="subscribing-to-a-private-product"></a>

Some products are not publicly available to browse in AWS Marketplace. These products can only be seen when you are given a private offer from the seller. However, you can only subscribe if your Private Marketplace administrator approves the product in your experience. Because of this, the private offer must be extended to both your AWS account and your organization's management account or delegated administrator account for Private Marketplace.

After the private offer has been extended to both the user and the administrator accounts, a Private Marketplace administrator can approve the product in your experience. You will be able to request the product if your administrator has enabled product procurement requests. For more information, see [Your Private Marketplace experience](your-private-marketplace-experience.md) to check if you can create requests.

After the product has been approved directly by an administrator or via your request, you can subscribe to the product like any other private offer. Refer [Viewing and subscribing to a private offer](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html) for details.

# Requesting products for procurement
<a name="requesting-products-for-procurement"></a>

As a user, you can request that your administrator approve a product that is not in your Private Marketplace experience. You will be able to create requests only if your administrator has enabled product procurement requests. For more information, see [Your Private Marketplace experience](your-private-marketplace-experience.md) to check if you can create requests.

**To request a product**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Discover Products**.

1. Search for the product you want to purchase.

1. If the product is not approved in your Private Marketplace experience, you will see a red banner with **Request product** button.

1. Choose **Request product**.

1. Fill the details, and choose **Request product** to submit your request. If you are an administrator, you will be redirected to a the form that allows you to approve the product directly without creating a request.

1. You will receive Amazon EventBridge events when a user in your account requests a product and when an administrator approves or declines the request. For more information, see [Private Marketplace notifications](configuring-notifications.md) for details on how you can configure email notifications for these events.

# Monitoring product requests
<a name="monitoring-product-requests"></a>

You can view the status of your pending product requests and subscribe to products that are approved by your administrator. You can also cancel requests up to 30 days before they expire.

**To view your product requests**

1. Open the AWS Marketplace console at [https://console.aws.amazon.com/marketplace/](https://console.aws.amazon.com/marketplace/).

1. In the navigation pane, choose **Approval requests** under **Private Marketplace**.

1. You can cancel multiple requests from this page by first selecting the check box next to the name of each requested product, and then choosing **Cancel**.

1. To view more information about the request, choose **View details** for that request.

   1. You can view the reason for request and the optional purchase order number that you entered.

   1. If the request is approved or declined, you can optionally see the approver note entered by your administrator.

   1. You can choose to **Cancel** the request and enter an optional note with reason for cancellation.

**Note**  
Private Marketplace supports two user experiences: AWS Console and the legacy website.  
To view and manage Private Marketplace in the AWS Marketplace Console, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. See [Enabling Private Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/private-marketplace-current.html#enable-private-marketplace) for details. For end users, administrators must also grant the new permissions listed in [AWSPrivateMarketplaceRequests](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-security-iam-awsmanpol.html#security-iam-awsmanpol-awsprivatemarketplacerequests).  
Product requests created using the legacy website will be available at [Private Marketplace](https://aws.amazon.com/marketplace/privatemarketplace). **Important:** The legacy website will be deprecated on March 17, 2026.

# Private Marketplace notifications
<a name="configuring-notifications"></a>

Private Marketplace administrators and buyers receive notification events from AWS Marketplace when a buyer requests a product, and when a request is approved or declined. Administrators receive notifications for requests from any account in their AWS organization. Buyers only receive notifications for requests from their accounts. The notification events include product details and the seller's name.

For information about the Private Marketplace notification events, see [Amazon EventBridge notifications for AWS Marketplace events](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-notifications-eventbridge.html), later in this guide.

You can create EventBridge rules with different target types by following the steps in [Amazon EventBridge rules](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html), in the *Amazon EventBridge User Guide*.

## Creating email notification configurations
<a name="creating-email-notification-configurations"></a>

You can use the AWS User Notifications service to get notifications for events through multiple channels, including email. The following steps explain how to create an email notification configuration. Notification configurations act as containers for the services and event rules that you want to be notified about. An event rule specifies the events that generate a notification in the AWS console, and which delivery channels to use.

**To create a notification configuration**

1. Sign in to the AWS Management Console and navigate to AWS User Notifications.

1. Choose **Notification configurations**, then choose **Create notification configuration**.

1. In the **Name** box, enter a name for the configuration.

1. In the **Event rules** section of the page, enter the following values:

   1. For **AWS service name**, choose **AWS Marketplace Private Marketplace**.

   1. For **Event type**, choose one or more of the following:

      1. **Product Request Created**

      1. **Product Request Approved**

      1. **Product Request Declined**

      1. **Product Request Cancelled**

      1. **Product Request Expired**

   1. For **Regions**, select **us-east-1**. Private marketplace only operates in that Region.

1. Under **Aggregation settings**, we recommend choosing **Receive within 5 minutes**.

1. Under **Delivery channels**, select the **email** checkbox, then do the following:

   1. In the **Recipient** box, enter the email address of the notification recipient.

   1. As needed, choose **Add another recipient**, the enter another email address in the **Recipient** box. You can enter a maximum of 99 recipients.

   1. (Optional) Under **Manage tags**, choose **Add new tag**, enter values in the **Key** and **Value** boxes.

1. When finished, choose **Create notification configuration**.

In addition to using an email delivery channel, you can also use the AWS Console Mobile App and Chat delivery channels. The following links take you to more information about those channels and about User Notifications.
+ [What is the AWS Console Mobile Application](https://docs.aws.amazon.com/consolemobileapp/latest/userguide/what-is-consolemobileapp.html), in the *AWS Console Mobile Application User Guide*.
+ [What is AWS Chatbot](https://docs.aws.amazon.com/chatbot/latest/adminguide/what-is.html), in the *Amazon Q Developer in chat applications Administrator Guide*.
+ [Creating a notification configuration](https://docs.aws.amazon.com/notifications/latest/userguide/getting-started.html#getting-started-step1), in the *User Notifications User Guide*.

**Note**  
Private Marketplace supports two user experiences: AWS Console and the legacy website.  
To view and manage Private Marketplace in the AWS Marketplace Console, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. See [Enabling Private Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/private-marketplace-current.html#enable-private-marketplace) for details. For end users, administrators must also grant the new permissions listed in [AWSPrivateMarketplaceRequests](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-security-iam-awsmanpol.html#security-iam-awsmanpol-awsprivatemarketplacerequests).  
Product requests created using the legacy website will be available at [Private Marketplace](https://aws.amazon.com/marketplace/privatemarketplace). **Important:** The legacy website will be deprecated on March 17, 2026.

# Private marketplaces in AWS Marketplace (legacy version)
<a name="private-marketplace"></a>

**Important**  
This documentation is for legacy version of Private Marketplace, which will be deprecated on March 17, 2026. For documentation of the current version, see [Private Marketplace](private-marketplace-current.md). To use the current version, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. To check integration status, see [Viewing Private Marketplace settings](view-private-marketplace-settings.md).

A private marketplace controls which products users in your AWS account, such as business users and engineering teams, can procure from AWS Marketplace. It is built on top of AWS Marketplace, and enables your administrators to create and customize curated digital catalogs of approved independent software vendors (ISVs) and products that conform to their in-house policies. Users in your AWS account can find, buy, and deploy approved products from your private marketplace, and ensure that all available products comply with your organization’s policies and standards. 

With [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/), you can centralize management of all of your accounts, group your accounts into organizational units (OUs), and attach different access policies to each OU. You can create multiple private marketplace experiences that are associated with your entire organization, one or more OUs, or one or more accounts in your organization, each with its own set of approved products. Your AWS administrators can also apply company branding to each private marketplace experience with your company or team’s logo, messaging, and color scheme.

**Notes**  
You can add private products that have been shared with you (through a [ private offer](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers.html)) to a private marketplace. For more information, see [Subscribing to a private product in a private marketplace](subscribing-to-a-private-product-in-a-private-marketplace.md).
In a private marketplace, customers are automatically entitled to any products whose EULAs are governed by the AWS Customer Agreement or other agreement with AWS governing use of AWS services. Customers are already entitled to these products by default; therefore, they are not included in the list of products that you approved within your private marketplace. 

**Topics**
+ [Viewing product detail pages](#product-detail-page-visit)
+ [Configuring notifications](#pmp-notifications)
+ [Private marketplaces for users](subscribing-to-a-product-in-a-private-marketplace.md)
+ [Private marketplaces for administrators](private-catalog-administration.md)

## Viewing product detail pages
<a name="product-detail-page-visit"></a>

Users can only subscribe to products that you allow in the private marketplace that governs the account. They can browse and see the detail page for any product, but subscription is enabled only for products you have added to your private marketplace. If a product is not currently in your private marketplace, the user sees a red banner at the top of the page, noting that the product is not approved for procurement in AWS Marketplace.

If software requests are enabled, users can choose **Create request** on the product details page. When users choose **Create request**, they submit a request to the administrator to make the product available on your private marketplace. For more information about this feature, see [Managing user requests for products in a private marketplace](manage-user-requests-private-marketplace.md).

## Configuring notifications
<a name="pmp-notifications"></a>

Private Marketplace administrators and buyers receive notification events from AWS Marketplace when a buyer requests a product, and when a request is approved or denied. Administrators receive notifications for requests from any account in their AWS organization. Buyers only receive notifications for requests from their accounts. The notification events include product details and the seller's name.

For information about the Private Marketplace notification events, see [Amazon EventBridge notifications for AWS Marketplace events](buyer-notifications-eventbridge.md), later in this guide.

You can create EventBridge rules with different target types by following the steps in [Amazon EventBridge rules](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html), in the *Amazon EventBridge User Guide*.

### Creating email notification configurations
<a name="pmp-create-configurations"></a>

You can use the AWS User Notifications service to receive notifications for events through multiple channels, including email. The following steps explain how to create an email notification configuration. Notification configurations act as containers for the services and event rules that you want to be notified about. An event rule specifies the events that generate a notification in the AWS console, and which delivery channels to use.

**To create a notification configuration**

1. Sign in to the AWS Management Console and navigate to AWS User Notifications.

1. Choose **Notification configurations**, then choose **Create notification configuration**.

1. In the **Name** box, enter a name for the configuration.

1. In the **Event rules** section of the page, enter the following values:
   + For **AWS service name**, choose **AWS Marketplace Private Marketplace**.
   + For **Event type**, choose one of the following:
     + **Product Request Created**
     + **Product Request Approved**
     + **Product Request Declined**
**Note**  
As needed, you can create notification configurations for each event type.
   + For **Regions**, select **us-east-1**. Private marketplace only operates in that Region.

1. Under **Aggregation settings**, we recommend choosing **Receive within 5 minutes**.

1. Under **Delivery channels**, select the **email** checkbox, then do the following:

   1. In the **Recipient** box, enter the email address of the notification recipient.

   1. As needed, choose **Add another recipient**, the enter another email address in the **Recipient** box. You can enter a maximum of 99 recipients.

   1. (Optional) Under **Manage tags**, choose **Add new tag**, enter values in the **Key** and **Value** boxes.
**Note**  
For more information about using the **AWS Console Mobile App** and **Chat channels** delivery options, see the links below.

1. When finished, choose **Create notification configuration**.

In addition to using an email delivery channel, you can also use the AWS Console Mobile App and Chat delivery channels. The following links take you to more information about those channels and about User Notifications.
+ [What is the AWS Console Mobile Application](https://docs.aws.amazon.com/consolemobileapp/latest/userguide/what-is-consolemobileapp.html), in the *AWS Console Mobile Application User Guide*.
+ [What is AWS Chatbot](https://docs.aws.amazon.com/chatbot/latest/adminguide/what-is.html), in the *Amazon Q Developer in chat applications Administrator Guide*.
+ [ Creating a notification configuration](https://docs.aws.amazon.com/notifications/latest/userguide/getting-started.html#getting-started-step1), in the *User Notifications User Guide*.

# Private marketplaces for users
<a name="subscribing-to-a-product-in-a-private-marketplace"></a>

To subscribe to a product in your private marketplace as a user, navigate to the product's details page and choose **Continue**. This redirects you to the product's subscription page. On the subscription page, you can make your configuration selections, and then choose **Subscribe**.

If the product is not approved in your private marketplace, **Subscribe** isn't available. A red banner at the top of the page indicates that the product is not currently approved for procurement. If software requests are enabled, you can choose **Create request** to submit a request to your administrator requesting that the product be added to your private marketplace.

# Subscribing to a private product in a private marketplace
<a name="subscribing-to-a-private-product-in-a-private-marketplace"></a>

Some products are not publicly available to browse in AWS Marketplace. These products can only be seen when you are given a private offer from the seller. However, you can only subscribe if your private marketplace administrator first adds the product to your private marketplace. Because of this, the private offer must be extended to both your AWS account and the account that includes your organization's private marketplace administrator. After the private offer has been extended to both the user and the administrator, the private marketplace administrator can add the product to your private marketplace. After the product has been approved, you can subscribe to the product like any other private offer.

# Requesting a product for your private marketplace
<a name="request-adding-a-product-to-your-private-marketplace"></a>

As a user, you can request that your administrator add a product that is not in your private marketplace. To make a request, navigate to the product's details page, choose **Create request**, enter a request to your administrator that the product be added to your private marketplace, and then submit your request. To track your request status, on the left dropdown menu, choose **Your Private Marketplace Requests**.

# Private marketplaces for administrators
<a name="private-catalog-administration"></a>

To create and manage a private marketplace, you must be signed into the management account or the delegated administrator account for private marketplace. You must also have the AWS Identity and Access Management (IAM) permissions in the AWSPrivateMarketplaceAdminFullAccess IAM policy. For more information about applying this policy to users, groups, and roles, see [Creating a private marketplace administrator](it-administrator.md).

**Note**  
If you're a current private marketplace customer without the AWS Organizations integration for private marketplace, you can create and manage a private marketplace from any account in your organization that has the AWSPrivateMarketplaceAdminFullAccess IAM policy.

This section includes tasks that you can complete as a private marketplace administrator through the AWS Marketplace website. You can also manage private marketplaces using the AWS Marketplace Catalog API. For more information, see [Working with a private marketplace](https://docs.aws.amazon.com/marketplace-catalog/latest/api-reference/private-marketplace.html) in the *AWS Marketplace Catalog API Reference*.

## Getting started with private marketplace
<a name="private-marketplace-getting-started"></a>

To get started with private marketplace, ensure you're signed into your AWS management account, navigate to [Private Marketplace](https://aws.amazon.com/marketplace/pmp/getstarted), and then enable the following prerequisites:
+ **Trusted access** – You must enable trusted access for AWS Organizations, which allows the management account of an organization to provide or revoke access for their AWS Organizations data for an AWS service. Enabling trusted access is critical for private marketplace to integrate with AWS Organizations and designate private marketplace as a trusted service in your organization.
+ **Service-linked role** – You must enable the private marketplace service-linked role, which resides in the management account and includes all the permissions that private marketplace requires to describe AWS Organizations and update private marketplace resources on your behalf. For more information on the service-linked role, see [Using roles to configure Private Marketplace in AWS Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/using-service-linked-roles-private-marketplace.html).

**Note**  
Current private marketplace customers can enable settings for your private marketplace by navigating to the **Private Marketplace** administrator's page and choosing **Settings**. By enabling trusted access for AWS Organizations and creating a service-linked role, you can utilize features, such as associating OUs to private marketplace experiences and registering a delegated administrator. When enabled, only the management account and delegated administrator account can create and manage marketplace experiences, with existing resources transferred to the management account and shared only with the delegated administrator. Disabling trusted access will remove private marketplace governance for your organization. There are no account groups displayed in your private marketplace. To view your organization’s governance at different levels, use the **Organization structure** page. For questions or support, [contact us](https://aws.amazon.com/contact-us/).

# Managing a private marketplace
<a name="private-marketplace-managing"></a>

You can manage your private marketplace from the **Private Marketplace** administrator's page under **Settings** in the left pane. The management account administrator and delegated administrators can use this page to view private marketplace details, including the default private marketplace and number of live experiences.

Management account administrators can also use this page to manage the following settings.

## Delegated administrators
<a name="delegated-administrators"></a>

The management account administrator can delegate private marketplace administrative permissions to a designated member account known as delegated administrator. To register an account as a delegated administrator for the private marketplace, the management account administrator must ensure trusted access and the service-linked role are enabled, choose **Register a new administrator**, provide the 12-digit AWS account number, and choose **Submit**.

Management accounts and delegated administrator accounts can perform private marketplace administrative tasks, such as creating experiences, updating branding settings, associating or disassociating audiences, adding or removing products, and approving or declining pending requests.

## Trusted access and service-linked role
<a name="trusted-access-slr"></a>

The management account administrator can enable the following features for your private marketplace.

**Note**  
Current private marketplace customers can enable settings for your private marketplace by navigating to the **Private Marketplace** administrator's page and choosing **Settings**. By enabling trusted access for AWS Organizations and creating a service-linked role, you can utilize features, such as associating OUs to private marketplace experiences and registering a delegated administrator. When enabled, only the management account and delegated administrator account can create and manage marketplace experiences, with existing resources transferred to the management account and shared only with the delegated administrator. Disabling trusted access will remove private marketplace governance for your organization. There are no account groups displayed in your private marketplace. To view your organization’s governance at different levels, use the **Organization structure** page. For questions or support, [contact us](https://aws.amazon.com/contact-us/).
+ **Trusted access** – You must enable trusted access for AWS Organizations, which allows the management account of an organization to provide or revoke access for their AWS Organizations data for an AWS service. Enabling trusted access is critical for private marketplace to integrate with AWS Organizations and designate private marketplace as a trusted service in your organization.
+ **Service-linked role** – You must enable the private marketplace service-linked role, which resides in the management account and includes all the permissions that private marketplace requires to describe AWS Organizations and update private marketplace resources on your behalf. For more information on the service-linked role, see [Using roles to configure Private Marketplace in AWS Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/using-service-linked-roles-private-marketplace.html).

# Creating a private marketplace experience
<a name="create-your-private-marketplace"></a>

Your private marketplace is made up of one or more private marketplace experiences. Experiences are subsets of products and associated branding that can have one or more associated audiences. An experience can be associated with your entire organization, one or more OUs, or one or more accounts in your organization. If your AWS account is not a member of an organization, then you have one private marketplace experience associated with one account. To create your private marketplace, navigate to [Private Marketplace](https://aws.amazon.com/marketplace/pmp/getstarted), select the **Experiences** page on the left, and choose **Create experience**. For each experience, you can add a logo, add a title, and customize the user interface to use your organization’s color scheme. 

**Note**  
To use private marketplace with AWS Organizations, you need to enable all features for the organization. For more information, see [Enabling all features in your organization](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_org_support-all-features.html) in the *AWS Organizations User Guide*.  
If your AWS account is not a member of an organization, you do not need any prerequisite steps to use private marketplace.

**To create a private marketplace experience**

1. Navigate to [Private Marketplace](https://aws.amazon.com/marketplace/pmp/getstarted).

1. From the navigation pane on the left, select **Experiences**, and then choose **Create experience**.

1. Specify a name for the experience, and then choose **Create experience**.

Your private marketplace experience is created with no approved products, no branding elements, and is associated with no accounts in your organization. It's not live by default. The next steps for your marketplace experience are:

1. [Manage the audience for your private marketplace](private-marketplace-audiences.md)

1. [Add products](add-products-to-your-private-marketplace.md)

1. [Change your private marketplace status to Live](configure-your-private-marketplace.md)

# Managing audiences for private marketplace experiences
<a name="private-marketplace-audiences"></a>

An audience is an organization or a group of organizational units (OUs) or accounts that you can associate with a private marketplace experience. You can create an audience from the **Private Marketplace** administrator's page under **Experiences** in the left pane.

You can associate one or more audiences to an experience. When you associate or disassociate an audience, it may change the governing experience of child OUs and accounts. Use the **Organization structure** page to see the accounts and OUs affected by the association. If you disable trusted access, your audiences will be disassociated and all governance will be removed.

**Note**  
You can view your AWS Organizations hierarchy and manage governance for your organization from private marketplace. To govern your private marketplace at an organizational unit level and register delegated administrators, enable trusted access and the service-linked role from the **Settings** page. For questions or support, [contact us](https://aws.amazon.com/contact-us/).

# Adding products to a private marketplace
<a name="add-products-to-your-private-marketplace"></a>

A private marketplace provides you with a broad catalog of products available in AWS Marketplace, along with fine-grained control of those products. 

**Note**  
In a private marketplace, customers are automatically entitled to any products whose EULAs are governed by the AWS Customer Agreement or other agreement with AWS governing use of AWS services. Customers are already entitled to these products by default; therefore, they are not included in the list of products that you approved within your private marketplace.

**To add products to a private marketplace experience**

1. From the **Private Marketplace** administrator's page, select **Experiences** in the left navigation pane. Then, on the **Products** tab, choose **All AWS Marketplace products**. You can search by product name or seller name.

1. Select the check box next to each product to add to your private marketplace and then choose **Add to Private Marketplace**.

**Note**  
You can also add a product directly from the product details page by choosing the **Add to Private Marketplace** button on the red banner. If the red banner is not on the product's detail page, the product is already in your private marketplace.

You can also add multiple products to multiple experiences at one time by choosing **Bulk add/remove products** from the left navigation pane.

## Verifying products in your private marketplace experience
<a name="verify-product-in-marketplace"></a>

**To verify a product is approved in your private marketplace experience**

1. From the **Private Marketplace** administrator's page, select **Experiences** in the left navigation pane.

1. Choose **Approved products**. All approved products display in the approved list.

**Note**  
If you are using an account that has been associated with the experience you are editing, and the experience is enabled, then you can also view the products directly in the AWS Marketplace console ([https://console.aws.amazon.com/marketplace](https://console.aws.amazon.com/marketplace)). All products in any search results show an *approved for procurement* badge if they are part of your private marketplace.

## Working with private products
<a name="private-products-in-a-private-marketplace"></a>

Some products are not publicly available to browse in AWS Marketplace. These products can only be seen when you are given a private offer from the seller. The private offer from the seller includes a link to the product. You can add the product to the private marketplace from the banner at the top of the page.

**Note**  
If you want to subscribe to a private product from a different account in your organization, the seller must include both your AWS account (to add the product to the private marketplace) and the user's account (to subscribe to the product) in the private offer.

To remove a private product from your private marketplace, you must [contact AWS Marketplace Support](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-support.html).

# Changing your private marketplace status
<a name="configure-your-private-marketplace"></a>

After you are satisfied with the experience's product list, the marketplace's branding settings, and the associated account groups, then you can make your private marketplace live. From the **AWS Private Marketplace** administrator's page, select **Experience** in the left navigation pane, then select the experience you want to enable. On the **Settings** tab, you can change the private marketplace status between **Live** (enabled) and **Not live** (disabled).

When your private marketplace is live, end users can buy only the products that you have approved. When your private marketplace is disabled, you retain the list of products. However, disabling a private marketplace removes the restriction from users in your AWS Organizations organization. As a result, they can subscribe to any products in the public AWS Marketplace. 

Making a private marketplace live does not disrupt active Amazon Machine Images (AMIs) running on Amazon Elastic Compute Cloud (Amazon EC2) instances. As a best practice, ensure that all AWS Marketplace products currently in use across your organization are included in your private marketplace. It's also a best practice to have a plan in place to discontinue use of unapproved products before making the private marketplace live. After the private marketplace is live, all new subscriptions or renewals are governed by the products approved in the private marketplace catalog.

# Managing user requests for products in a private marketplace
<a name="manage-user-requests-private-marketplace"></a>

You can allow users to submit requests for products to be added to their private marketplace catalog with the software request feature. Software requests are enabled by default, and the setting can only be modified while the private marketplace is enabled.

You can add any number of requested products from this page by first selecting the check box next to the name of each requested product, and then choosing **Add to Private Marketplace**. Similarly, you can also decline one or more selected requests by choosing **Decline**. To view more information about a product (or its software request), choose **View details** in the **Details** column for that request.

When you decline a product request, you can add a reason and prevent future requests (block) for this product. Blocking a product won't prevent you from adding the product to your private marketplace, but it does prevent your users from requesting the product.

**To manage user requests**

1. From the **Private Marketplace** administrator's page, select **Experiences** in the left navigation pane.

1. Choose the experience you want to manage.

1. To enable or disable user requests, choose the **Settings** tab.

1. To view product requests, choose the **Products** tab. From here you can review requests your users have made for products to be added to their private marketplace catalog.

**Note**  
Private Marketplace supports two user experiences: AWS Console and the legacy website.  
To view and manage Private Marketplace in the AWS Marketplace Console, an administrator in the management account of your AWS Organizations must create an integration for Private Marketplace. See [Enabling Private Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/private-marketplace-current.html#enable-private-marketplace) for details. For end users, administrators must also grant the new permissions listed in [AWSPrivateMarketplaceRequests](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-security-iam-awsmanpol.html#security-iam-awsmanpol-awsprivatemarketplacerequests).  
Product requests created using the legacy website will be available at [Private Marketplace](https://aws.amazon.com/marketplace/privatemarketplace). **Important:** The legacy website will be deprecated on March 17, 2026.

# Archiving a private marketplace experience
<a name="archiving-a-private-marketplace-experience"></a>

You can remove a private marketplace experience by archiving it. Archived experiences can’t be updated or used to govern accounts in your organization. If you have audiences associated with an archived experience, you can associate them with a different experience. If you decide to use the experience at a later time, you can always [reactivate it](reactivating-a-private-marketplace-experience.md). Management account administrators or delegated administrators have permissions to archive experiences.

**Note**  
Before archiving an experience, you must disable it. For information about disabling an experience, see [Changing your private marketplace status](https://docs.aws.amazon.com/marketplace/latest/buyerguide/private-catalog-administration.html#configure-your-private-marketplace).  
If you're a current private marketplace customer without the AWS Organizations integration for private marketplace, administrators from the account that created the experience have permissions to archive experiences.

**To archive one or more private marketplace experiences**

1. From the **Private Marketplace** administrator's page, select **Experiences** in the left navigation pane.

1. On the **Active experiences** tab, select one or more experiences.

1. Choose **Archive experience**.
**Note**  
If one or more of the experiences has a Live status, you must take them offline by choosing **Take experience(s) offline**. 

1. To verify that you want to archive the experience, type **confirm** (all lowercase) in the text box.

1. Choose **Archive**.
**Note**  
You can also archive an experience by selecting the experience, choosing **Archive experience** under **Admin** mode on the **Settings** tab, and then choosing **Save**.

# Reactivating a private marketplace experience
<a name="reactivating-a-private-marketplace-experience"></a>

If you decide you want to use an [archived](archiving-a-private-marketplace-experience.md) marketplace experience, you can always reactivate it. Management account administrators or delegated administrators have permissions to reactivate experiences.

**Note**  
If you're a current private marketplace customer without the AWS Organizations integration for private marketplace, administrators from the account that created the experience have permissions to reactivate experiences.

**To reactivate one or more private marketplace experiences**

1. From the Private Marketplace administrator's page, select **Experiences** in the left navigation pane.

1. On the **Archived experiences** tab, select one or more experiences.

1. Choose **Reactivate**.

1. To verify that you want to reactivate the experience, type **confirm** in the text box.

1. Choose **Reactivate**. 
**Note**  
You can also reactive an experience by selecting the experience, choosing **Reactivate experience** under **Admin** mode in the **Settings** tab, and then choosing **Save**.