diff --git a/content/en/docs/control-center/marketplace/company-approved.md b/content/en/docs/control-center/marketplace/company-approved.md
new file mode 100644
index 00000000000..4359d0e538f
--- /dev/null
+++ b/content/en/docs/control-center/marketplace/company-approved.md
@@ -0,0 +1,68 @@
+---
+title: "Company-Approved"
+url: /control-center/company-approved/
+description: "Describes the Company-Approved page in the Mendix Control Center."
+weight: 10
+no_list: true
+aliases:
+ - /control-center/marketplace-curation/
+---
+
+## Introduction
+
+The **Company-Approved** page provides governance capabilities within the Mendix Platform. It allows you to translate the company's policies and guidelines for public and private Marketplace content to curation settings. Marketplace components that meet these requirements get a company-approved label: {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED. This way, developers from your company can easily see which public content is company-approved according to your company policies and guidelines. This functionality provides several key benefits:
+
+* Developer guidance – Developers can easily identify Marketplace content suitable for their apps by filtering Marketplace content by the company-approved label in Studio Pro's Marketplace section or on the Marketplace website. This helps developers find valuable and relevant content for app development in your company.
+ For more information, see [Displaying Company Approved Marketplace Content in Studio Pro](#display-company-approved-marketplace-content).
+* Enhanced marketplace exploration – By specifying criteria for company-approved content, developers can explore a wider array of public content, enabling them to leverage resources for their apps.
+* Governance control – Centralized curation allows Mendix Admins to translate offline policies and guidelines to an in-platform experience, establishing efficient communication and time-saving processes between developers and Mendix Admins.
+
+The **Company-Approved** page contains the following tabs:
+
+* [Components](#marketplace-content-list)
+* [Settings](#curation-settings)
+
+## Components {#marketplace-content-list}
+
+The **Components** tab lists all Marketplace content, be it public or private. It includes information about whether a component carries the company-approved label, and if so, it shows the source of the label. These are the details displayed in the list:
+
+* **Component Name** – The name of the component.
+* **Support Type** – The support type of the component.
+* **Visibility** – The visibility of the component, which can be **Public** or **Private**.
+* **Updated on** – The date when the component was most recently updated.
+* **License** – The license of the component.
+* **Label** – This shows whether the content has a company approved label.
+* **Authorised by** – This indicates the origin of the label:
+
+ * **Marked via Setting** – The company-approved label is added automatically based on the curation settings.
+ * **[Admin Name]** – The company-approved label is added manually by a Mendix Admin.
+
+### Managing the Company-Approved Label
+
+For components that are not company-approved based on your [curation settings](#curation-settings), you can manually add the company-approved label.
+The **Manage Company-Approved Label** page allows you to manually add and remove the company-approved label for your company's components. To access it, click **Add Company-Approved Label** in the top right of the component list.
+
+The **Manage Company-Approved Label** page includes the same fields as the component list, with the additional **Company Approval** field, which shows whether the component has been marked as company-approved or not.
+
+You can click the contextual actions menu next to each component to change its company approval status.
+Additionally, you can select multiple components to change their company approval status simultaneously.
+
+{{% alert color="info" %}}If you manually add a company-approved label to a Marketplace component, this Marketplace component will always keep the label, even if the curation settings get changed later. However, if you manually remove a company-approved label from a Marketplace component, then the label will automatically appear again if the curation settings get changed later, and the Marketplace component meets the new requirements. {{% /alert %}}
+
+## Settings {#curation-settings}
+
+On the **Settings** tab, you can configure company policies and guidelines for public and private Marketplace content.
+
+Select the support types and license types that you deem relevant. Marketplace components that meet your requirements will be automatically labeled as company-approved.
+
+For instance, if you select **Community** and **Platform** under **Based on Support Types**, and **MIT** under **Based on License**, then any component supported by the **Community** or **Platform** and licensed under **MIT** will be labeled as company-approved.
+
+{{% alert color="info" %}}Partner License: this license covers all custom licenses generated by partner companies. {{% /alert %}}
+
+## Displaying Company-Approved Marketplace Content in Studio Pro {#display-company-approved-marketplace-content}
+
+In Studio Pro's Marketplace section, developers can view all Marketplace components, company approved content or not. To only see company approved content, select the **Show {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED** check box.
+
+The company approved label is also visible on the details page in the main panel.
+
+{{< figure src="/attachments/control-center/marketplace/marketplace-curation/displaying-company-approved-content.png" max-width=100% alt=''displaying-company-approved-mp-content'' >}}
diff --git a/content/en/docs/control-center/marketplace/marketplace-curation.md b/content/en/docs/control-center/marketplace/marketplace-curation.md
deleted file mode 100644
index 3511524fd9d..00000000000
--- a/content/en/docs/control-center/marketplace/marketplace-curation.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: "Public Marketplace"
-url: /control-center/marketplace-curation/
-description: "Describes the Marketplace Curation page in the Mendix Control Center."
-weight: 10
-no_list: true
----
-
-## Introduction
-
-The **Marketplace Curation** feature is a governance capability within the Mendix Platform. With this feature, you can translate the company's policies and guidelines for public Marketplace content to curation settings. Marketplace components that meet these requirements get a company approved label: {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED. This way, developers from your company can easily see which public content is company approved according to your company policies and guidelines. This functionality provides several key benefits:
-
-* Developer guidance – Developers can easily identify Marketplace content suitable for their apps by filtering Marketplace content by the company approved label in Studio Pro's Marketplace section or on the Marketplace website. This helps developers find valuable and relevant content for app development in your company.
- For more information, see [Displaying Company Approved Marketplace Content in Studio Pro](#display-company-approved-marketplace-content).
-* Enhanced marketplace exploration – By specifying criteria for company approved content, developers can explore a wider array of public content, enabling them to leverage resources for their apps.
-* Governance control – Centralized curation allows Mendix Admins to translate offline policies and guidelines to an in-platform experience, establishing efficient communication and time-saving processes between developers and Mendix Admins.
-
-The **Marketplace Curation** page contains two tabs: [Curation Settings](#curation-settings) and [Marketplace Content List](#marketplace-content-list).
-
-## Curation Settings {#curation-settings}
-
-On the **Curation Settings** tab, you can configure company policies and guidelines for public Marketplace content.
-
-Select the support types and license types. Public Marketplace components that meet your requirements will be automatically labeled as company approved. For instance, in the following example, any component supported by the **Community** or **Platform** and licensed under **Apache v2** or **BSD 2.0** will be labeled as company approved.
-
-{{< figure src="/attachments/control-center/marketplace/marketplace-curation/curation_settings.png" max-width=100% >}}
-
-{{% alert color="info" %}}Partner License: this license covers all custom licenses generated by partner companies. {{% /alert %}}
-
-## Marketplace Content List {#marketplace-content-list}
-
-The **Marketplace Content List** tab lists all public Marketplace content. It includes information about whether a component carries the company approved label, and if so, it shows the source of the label. These are the details displayed in the list:
-
-* **Content Name** – This shows the name of the content.
-* **Support** – This shows the support type of the content.
-* **Updated on** – This shows the date when the content was most recently updated.
-* **License** – This shows the license of the content.
-* **Label** – This shows whether the content has a company approved label.
-* **Source** – This indicates the origin of the label:
-
- * **Curation Setting** – The company approved label is added automatically based on the curation settings.
- * **Manual** – The company approved label is added manually by a Mendix Admin.
-
-You can manually add or remove a label after selecting the content from the list. For content that is not company approved based on your curation settings, you can manually add the label by clicking the **Add Label** button. Conversely, for content that is company approved based on the curation settings, you can manually remove the label by clicking the **Remove Label** button.
-
-{{% alert color="info" %}}If you manually add a company approved label to a Marketplace component, this Marketplace component will always keep the label, even if the curation settings get changed later. However, if you manually remove a company approved label from a Marketplace component, then the label will automatically appear again if the curation settings get changed later and the Marketplace component meets the new requirements. {{% /alert %}}
-
-{{< figure src="/attachments/control-center/marketplace/marketplace-curation/marketplace_content_list.png" max-width=100% alt=''marketplace-content-list'' >}}
-
-## Displaying Company Approved Marketplace Content in Studio Pro {#display-company-approved-marketplace-content}
-
-In Studio Pro's Marketplace section, developers can view all Marketplace components, company approved content or not. To only see company approved content, select the **Show {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED** check box.
-
-The company approved label is also visible on the details page in the main panel.
-
-{{< figure src="/attachments/control-center/marketplace/marketplace-curation/displaying-company-approved-content.png" max-width=100% alt=''displaying-company-approved-mp-content'' >}}
diff --git a/content/en/docs/control-center/marketplace/private-marketplace.md b/content/en/docs/control-center/marketplace/private-marketplace.md
deleted file mode 100644
index 0140dfa6233..00000000000
--- a/content/en/docs/control-center/marketplace/private-marketplace.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: "Private Marketplace"
-url: /control-center/private-marketplace/
-description: "Describes the Private Marketplace page in the Mendix Control Center."
-weight: 20
-no_list: true
----
-
-## Introduction
-
-The **Private Marketplace** page gives you the governance capabilities to approve or decline a request for adding a new component or a new version of an existing component to your organization's private Marketplace. It gives you the following benefits:
-
-* Enhanced security: It allows you to mitigate security risks by ensuring that only vetted and approved components are added to the company’s Private Marketplace.
-* Company guidelines assurance: It enables you to meet regulatory requirements and internal policies by thoroughly reviewing components.
-* Efficient management: It offers a centralized approval process to save time and resources, preventing additional communication outside of the platform.
-
-{{% alert color="info" %}}As a Mendix Admin, you can always unpublish content from the private Marketplace of your organization. This can help your organization keep its private Marketplace neat, with only relevant company content. To do so, go to [Company Content](/appstore/home-page/#company-content) in the Marketplace home page, click the {{% icon name="three-dots-menu-horizontal" %}} icon on the component card, and then select **Unpublish all versions**. {{% /alert %}}
-
-The **Private Marketplace** page contains two tabs: the [Approval Requests](#approval-requests) tab and the [Approval History](#approval-history) tab.
-
-## Approval Requests {#approval-requests}
-
-On the **Approval Requests** tab, you can configure the governance settings for publishing private Marketplace content and also manage all the pending requests.
-
-{{< figure src="/attachments/control-center/marketplace/private-marketplace/approval-requests.png" max-width=100% alt=''private-marketplace'' >}}
-
-### Approval Requests Settings
-
-Under the **Approvals Requests** section, you can configure settings for the following governance capabilities:
-
-{{% alert color="info" %}}All the settings are turned off by default.{{% /alert %}}
-
-* **Mendix Admins must approve submissions for new components** – If you turn on this toggle, when a new component is submitted to the private Marketplace, a Mendix Admin needs to approve the submission before the component is added to the private Marketplace. The submission appears on the [Pending Approvals](#pending-approvals) list before it gets approved or declined.
-
- {{% alert color="info" %}}This setting only affects only the submission of a new component. After you approve the submission, developers can later directly add new versions of the component to the private Marketplace without an approval from a Mendix Admin, unless you also turn on the toggle **Mendix Admins must approve submissions of new component's versions**. {{% /alert %}}
-
- If you turn off this toggle, there will be the following consequences:
-
- * The toggle **Mendix Admins must approve submissions of new component's versions** will be turned off automatically.
- * All the pending requests will get approved automatically.
-
- * Developers will be able to directly add component to the private Marketplace without an approval from a Mendix Admin.
-
-* **Mendix Admins must approve submissions of new component's versions** – If you turn on this toggle, when a new version of a component is submitted to the private Marketplace, a Mendix Admin needs to approve the submission before the new version is added to the private Marketplace. The submission appears on the [Pending Approvals](#pending-approvals) list before it gets approved or declined.
-
- If you turn off this toggle, developers can directly add new versions of an existing component to the private Marketplace without an approval from a Mendix Admin.
-
-* **I'd like to create a notification when an approval request is waiting to be approved** – If you turn on this toggle, when there is a new submission request, you get a notification.
-
- {{% alert color="info" %}}This setting only affects your notifications, not the notifications of other Mendix Admins in your organization.{{% /alert %}}
-
-### Pending Approvals List {#pending-approvals}
-
-The **Pending Approvals** list shows all the submission requests that need to be approved or rejected, with the following details:
-
-* **Component Name** – This shows the name of the component in the pending request.
-* **Content Type** – This shows the type of the component in the pending request.
-* **Version** – This shows the version of the component in the pending request.
-* **Mendix Version** – This shows the compatible Mendix version for the component in the pending request.
-* **Submitter** – This shows the name of the submitter.
-* **Submission Date** – This shows the date when the request is submitted.
-
-#### Request Details
-
-If you click the component name in a request on the **Pending Approvals** list, the details of the request open in a new page. Here you can check all the provided information about the component, download the *•mpk* file, and approve or decline the request.
-
-{{< figure src="/attachments/control-center/marketplace/private-marketplace/request-details.png" max-width=100% alt=''request-details'' >}}
-
-On the top, you can find following buttons:
-
-* **Approve** – Click this button to approve the request. After you approve the request, the submitter will receive a notification, and the component will be published in the private Marketplace of your company.
-* **Decline** – Click this button to reject the request. You can also add a reason. After you decline the request, the submitter will receive a notification.
-* **Download** – Click this button to download the *.mpk* file of the component.
-
-The request details page also has the following tabs:
-
-* **General** – This tab shows the general information about the component, such as content type, category, license, description, and cover image. The right side of the screen shows the submitter's name and email, the activity log, and the technical details of the component, such as the compatible Mendix version, component ID, and UUID.
-
-* **Package** – This tab shows the information and the version of the *.mpk* file and the release notes.
-
- {{% alert color="info" %}}If the content type of the component is **Industry Template**, this tab is optional. If the content type of the component is **Solution Content type**, the tab is unavailable.{{% /alert %}}
-
-* **Documentation** – This tab shows the documentation and screenshots, as well as the link to the demo if there is a demo.
-
-* **Capabilities** – This tab shows additional information about content types such as **Solution** and **Industry Template**.
-
-## Approval History {#approval-history}
-
-The **Approval History** tab lists all the requests that were approved or declined in the history.
-
-{{< figure src="/attachments/control-center/marketplace/private-marketplace/approval-history.png" max-width=100% alt=''approval-history'' >}}
-
-The list shows the following details:
-
-* **Component Name** – This shows the name of the component in the request.
-* **Content Type** – This shows the type of the component in the request.
-* **Action** – This shows whether the component in the request got **Published** or **Declined**.
-* **Admin** – This shows the name of the Mendix Admin who approved or declined the request.
-* **Date** – This shows the date when the request got approved or declined.
-* **Reason** – This shows the reason why the request got approved or declined.
diff --git a/content/en/docs/control-center/marketplace/submitted-requests.md b/content/en/docs/control-center/marketplace/submitted-requests.md
new file mode 100644
index 00000000000..ecc0e02dff0
--- /dev/null
+++ b/content/en/docs/control-center/marketplace/submitted-requests.md
@@ -0,0 +1,98 @@
+---
+title: "Submitted Requests"
+url: /control-center/submitted-requests/
+description: "Describes the Submitted Requests page in the Mendix Control Center."
+weight: 20
+no_list: true
+aliases:
+ - /control-center/private-marketplace/
+---
+
+## Introduction
+
+The **Submitted Requests** page gives you the governance capabilities to approve or decline a request for adding a new component or a new version of an existing component to your organization's Marketplace. It gives you the following benefits:
+
+* Enhanced security: It allows you to mitigate security risks by ensuring that only vetted and approved components are added to the company’s Marketplace.
+* Company guidelines assurance: It enables you to meet regulatory requirements and internal policies by thoroughly reviewing components.
+* Efficient management: It offers a centralized approval process to save time and resources, preventing additional communication outside of the platform.
+
+{{% alert color="info" %}}As a Mendix Admin or component owner, you can always unpublish content from the Marketplace of your organization. This can help your organization keep its private Marketplace neat, with only relevant company content. To do so, go to [Company Content](/appstore/home-page/#company-content) in the Marketplace home page, click the {{% icon name="three-dots-menu-horizontal" %}} icon on the component card, then select **Unpublish all versions**. {{% /alert %}}
+
+The **Submitted Requests** page contains the following tabs:
+
+* [Pending Approvals](#pending-approvals)
+* [Approval Settings](#approval-settings)
+* [Approval History](#approval-history)
+
+## Pending Approvals {#pending-approvals}
+
+On the **Pending Approvals** tab, you can manage all pending requests.
+
+The **Pending Approvals** list shows all the submission requests that need to be approved or rejected, with the following details:
+
+* **Component Name** – The name of the component for which there is a pending request.
+* **Content Type** – The type of the component for which there is a pending request.
+* **Version** – The version of the component for which there is a pending request.
+* **Studio Pro Version** – The Studio Pro version which is compatible with the component for which there is a pending request.
+* **Submitter** – Te name of the request submitter.
+* **Submitted on** – The date when the request is submitted.
+
+### Request Details
+
+If you click the component name of a request in the **Pending Approvals** list, the details of the request open in a new page. Here, you can check all the provided information about the component, download the *•mpk* file, and approve or decline the request.
+
+At the top of the page, you can find following buttons:
+
+* **Approve** – Click this button to approve the request. After you approve the request, the submitter receives a notification, and the component is published on your company's Marketplace.
+ From the approval confirmation window, you can add the company-approved label to the approved component.
+* **Decline** – Click this button to reject the request. You can also add a reason. After you decline the request, the submitter receives a notification.
+* **Download** – Click this button to download the *.mpk* file of the component.
+
+The request details page also includes the following tabs:
+
+* **General** – This tab shows general information about the component, such as content type, category, license, description, and cover image. The right side of the screen shows the submitter's name and email, the activity log, and the technical details of the component, such as the compatible Mendix version, component ID, and UUID.
+
+* **Package** – This tab shows the information and the version of the *.mpk* file and the release notes.
+
+ {{% alert color="info" %}}If the content type of the component is **Industry Template**, this tab is optional. If the content type of the component is **Solution Content type**, the tab is unavailable.{{% /alert %}}
+
+* **Documentation** – This tab shows the documentation and screenshots, as well as the link to the demo if there is one.
+
+* **Capabilities** – This tab shows additional information about content types such as **Solution** and **Industry Template**.
+
+## Approval Settings {#approval-settings}
+
+The **Approval Settings** tab allows you to configure settings for the following governance capabilities:
+
+{{% alert color="info" %}}All the settings are turned off by default.{{% /alert %}}
+
+* **Company Admin must approve submissions of new components** – If you turn on this toggle, when a new component is submitted to the Marketplace, a company Admin needs to approve the submission before the component is published to the Marketplace. The submission is displayed on the [Pending Approvals](#pending-approvals) tab before it gets approved or declined.
+
+ {{% alert color="info" %}}This setting only affects the submission of a new component. After you approve the submission, developers can later directly add new versions of the component to the Marketplace without an approval from a company Admin, unless you also turn on the toggle **Company Admin must approve submissions of new component versions**. {{% /alert %}}
+
+ Turning off this toggle has the following consequences:
+
+ * The **Company Admin must approve submissions of new component versions** toggle is turned off automatically.
+ * All pending requests get approved automatically.
+ * Developers can directly add components to the Marketplace, without an approval from a company Admin.
+
+* **Company Admin must approve submissions of new component versions** – If you turn on this toggle, when a new version of a component is submitted to the Marketplace, a company Admin needs to approve the submission before the new version is published to the Marketplace. The submission is displayed on the [Pending Approvals](#pending-approvals) tab before it gets approved or declined.
+
+ If you turn off this toggle, developers can directly add new versions of an existing component to the Marketplace, without approval from a company Admin.
+
+* **Receive emails notifications when a submission is waiting to be approved** – If you turn on this toggle, when there is a new submission request, you get a notification.
+
+ {{% alert color="info" %}}This setting only affects your notifications, not the notifications of other Mendix Admins in your organization.{{% /alert %}}
+
+## Approval History {#approval-history}
+
+The **Approval History** tab lists all the requests that were approved or declined in the history.
+
+The list shows the following details:
+
+* **Component Name** – This shows the name of the component in the request.
+* **Content Type** – This shows the type of the component in the request.
+* **Action** – This shows whether the component in the request got **Published** or **Declined**.
+* **Admin** – This shows the name of the Mendix Admin who approved or declined the request.
+* **Date** – This shows the date when the request got approved or declined.
+* **Reason** – This shows the reason why the request got approved or declined.
diff --git a/content/en/docs/developerportal/digital-execution/implement-mendix/governance.md b/content/en/docs/developerportal/digital-execution/implement-mendix/governance.md
index 9c2430fb661..8104759fbfc 100755
--- a/content/en/docs/developerportal/digital-execution/implement-mendix/governance.md
+++ b/content/en/docs/developerportal/digital-execution/implement-mendix/governance.md
@@ -31,7 +31,7 @@ There are several advanced capabilities in the Control Center to help you manage
* [Health dashboard](/control-center/application-health-dashboard/) provides an insight into the running status of your app landscape.
* [Entitlements](/control-center/entitlements/) shows the resources you’ve bought and used.
* You can add, resize or remove environments in the [Deployed apps](/control-center/deployed-apps/) view.
-* Additional curation settings are available for [Marketplace](/control-center/private-marketplace/), [Portfolios](/control-center/portfolios/), and [Data Catalog](/control-center/catalog-admin/), which apply to all your developers.
+* Additional curation settings are available for [Marketplace](/control-center/company-approved/), [Portfolios](/control-center/portfolios/), and [Data Catalog](/control-center/catalog-admin/), which apply to all your developers.
If you would like to learn more about our governance features, you can check out the [Control Center Guide](/control-center/) and the [Control Center Learning Path](https://academy.mendix.com/link/paths/116/Govern-and-Scale-your-App-Landscape-with-Mendix-Control-Center).
diff --git a/content/en/docs/releasenotes/control-center/2024.md b/content/en/docs/releasenotes/control-center/2024.md
index 82d39737b59..8823e464b86 100644
--- a/content/en/docs/releasenotes/control-center/2024.md
+++ b/content/en/docs/releasenotes/control-center/2024.md
@@ -93,7 +93,7 @@ numberless_headings: true
#### New Features
-* We have introduced a [Marketplace content curation feature](/control-center/marketplace-curation/) for public Marketplace components. If your organization has established governance policies and guidelines for using Marketplace components, you can now translate them to curation settings. Components that meet these requirements will get a RECOMMENDED label.
+* We have introduced a [Marketplace content curation feature](/control-center/company-approved/) for public Marketplace components. If your organization has established governance policies and guidelines for using Marketplace components, you can now translate them to curation settings. Components that meet these requirements will get a RECOMMENDED label.
#### Improvements
@@ -119,4 +119,4 @@ numberless_headings: true
#### New Features
-* We introduced the [Private Marketplace](/control-center/private-marketplace/) page in Control Center, which allows Mendix Admins to approve or decline requests for publishing content to your organization's private Marketplace.
+* We introduced the [Private Marketplace](/control-center/submitted-requests/) page in Control Center, which allows Mendix Admins to approve or decline requests for publishing content to your organization's private Marketplace.
diff --git a/content/en/docs/releasenotes/control-center/2025.md b/content/en/docs/releasenotes/control-center/2025.md
index 626f392dcbe..e5dbbe96434 100644
--- a/content/en/docs/releasenotes/control-center/2025.md
+++ b/content/en/docs/releasenotes/control-center/2025.md
@@ -89,7 +89,7 @@ For more information, see [Allowing External User Invites to Projects](/control-
#### Improvements
-* We have replaced the [Marketplace Curation](/control-center/marketplace-curation/) RECOMMENDED label with {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED. The new label indicates Marketplace components that meet company policies and guidelines.
+* We have replaced the [Marketplace Curation](/control-center/company-approved/) RECOMMENDED label with {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED. The new label indicates Marketplace components that meet company policies and guidelines.
## March 2025
diff --git a/content/en/docs/releasenotes/control-center/2026.md b/content/en/docs/releasenotes/control-center/2026.md
index d82bf2c1196..8da00701b01 100644
--- a/content/en/docs/releasenotes/control-center/2026.md
+++ b/content/en/docs/releasenotes/control-center/2026.md
@@ -9,6 +9,20 @@ numberless_headings: true
## January 2026
+### January 15, 2026
+
+#### New Features
+
+* We have revamped the Marketplace section of Control Center, and have added a few new features and improvements meant to help you more efficiently manage and govern component approvals:
+
+ * You can now add the company-approved ( {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED) label to private Marketplace components as well.
+ * We have updated page names in an effort to better convey their purpose:
+
+ * **Public Marketplace** is now **Company-Approved**. For details, refer to [Company-Approved](/control-center/company-approved/).
+ * **Private Marketplace** is now **Submitted Requests**. For details, refer to [Submitted Requests](/control-center/submitted-requests/).
+
+ * The **Submitted Requests** page is now split up into three tabs instead of two. The newly added tab is **Approval Settings**, and it includes the approval options that were previously displayed at the top of the **Pending Approvals** tab.
+
### January 5, 2026
#### New Features
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md
index df3d5a2fbd0..b81ff5f640b 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md
@@ -3,7 +3,7 @@ title: "2017 Marketplace Release Notes"
linktitle: "2017"
url: /releasenotes/marketplace/2017/
description: "2017 release notes for Marketplace"
-weight: 9
+weight: 10
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md
index a614b5886c1..6472165b2e3 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md
@@ -3,7 +3,7 @@ title: "2018 Marketplace Release Notes"
linktitle: "2018"
url: /releasenotes/marketplace/2018/
description: "2018 release notes for Marketplace"
-weight: 8
+weight: 9
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2019.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2019.md
index 1e0d770e13a..66d38c03e4d 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2019.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2019.md
@@ -3,7 +3,7 @@ title: "2019 Marketplace Release Notes"
linktitle: "2019"
url: /releasenotes/marketplace/2019/
description: "2019 release notes for Marketplace"
-weight: 7
+weight: 8
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2020.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2020.md
index 4315fcdc13f..98d25da461d 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2020.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2020.md
@@ -3,7 +3,7 @@ title: "2020 Marketplace Release Notes"
linktitle: "2020"
url: /releasenotes/marketplace/2020/
description: "2020 release notes for Marketplace"
-weight: 6
+weight: 7
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2021.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2021.md
index a2199d3c4b1..18fba109c7d 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2021.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2021.md
@@ -3,7 +3,7 @@ title: "2021 Marketplace Release Notes"
linktitle: "2021"
url: /releasenotes/marketplace/2021/
description: "2021 release notes for Marketplace"
-weight: 5
+weight: 6
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2022.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2022.md
index 9ccfc0257cc..ee3c8cf9aa6 100755
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2022.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2022.md
@@ -3,7 +3,7 @@ title: "2022 Marketplace Release Notes"
linktitle: "2022"
url: /releasenotes/marketplace/2022/
description: "2022 release notes for Marketplace"
-weight: 4
+weight: 5
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2023.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2023.md
index e3e259ef233..bb82c68089d 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2023.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2023.md
@@ -3,7 +3,7 @@ title: "2023 Marketplace Release Notes"
linktitle: "2023"
url: /releasenotes/marketplace/2023/
description: "2023 release notes for Marketplace"
-weight: 3
+weight: 4
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2024.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2024.md
index cac696d8e9d..4b5228ff88c 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2024.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2024.md
@@ -3,7 +3,7 @@ title: "2024 Marketplace Release Notes"
linktitle: "2024"
url: /releasenotes/marketplace/2024/
description: "2024 release notes for Marketplace"
-weight: 2
+weight: 3
numberless_headings: true
---
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md
index ebeeb07d58e..544b4d3f6fa 100755
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md
@@ -3,7 +3,7 @@ title: "2025 Marketplace Release Notes"
linktitle: "2025"
url: /releasenotes/marketplace/2025/
description: "2025 release notes for Marketplace"
-weight: 1
+weight: 2
numberless_headings: true
---
@@ -122,7 +122,7 @@ The new layout prominently displays the latest LTS and MTS releases, allowing yo
#### Improvements
-* We have replaced the [Marketplace Curation](/control-center/marketplace-curation/) RECOMMENDED label with {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED. The new label indicates Marketplace components that meet company policies and guidelines.
+* We have replaced the [Marketplace Curation](/control-center/company-approved/) RECOMMENDED label with {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED. The new label indicates Marketplace components that meet company policies and guidelines.
## January 2025
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2026.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2026.md
new file mode 100644
index 00000000000..d0be56e5b34
--- /dev/null
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2026.md
@@ -0,0 +1,24 @@
+---
+title: "2026 Marketplace Release Notes"
+linktitle: "2026"
+url: /releasenotes/marketplace/2026/
+description: "2026 release notes for Marketplace"
+weight: 1
+numberless_headings: true
+---
+
+## January 2026
+
+### January 15, 2026
+
+#### New Features
+
+* We have revamped the Marketplace section of Control Center, and have added a few new features and improvements meant to help you more efficiently manage and govern component approvals:
+
+ * You can now add the company-approved ( {{% icon name="checkmark-shield-filled" color="green" %}}COMPANY APPROVED) label to private Marketplace components as well.
+ * We have updated page names in an effort to better convey their purpose:
+
+ * **Public Marketplace** is now **Company-Approved**. For details, refer to [Company-Approved](/control-center/company-approved/).
+ * **Private Marketplace** is now **Submitted Requests**. For details, refer to [Submitted Requests](/control-center/submitted-requests/).
+
+ * The **Submitted Requests** page is now split up into three tabs instead of two. The newly added tab is **Approval Settings**, and it includes the approval options that were previously displayed at the top of the **Pending Approvals** tab.
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md b/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md
index 3aa1028214a..07aff3e724c 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md
@@ -14,6 +14,7 @@ These release notes cover changes made to the [Mendix Marketplace](/appstore/).
Click the link corresponding to the year for which you want to read release notes:
+* [2026](/releasenotes/marketplace/2026/)
* [2025](/releasenotes/marketplace/2025/)
* [2024](/releasenotes/marketplace/2024/)
* [2023](/releasenotes/marketplace/2023/)