From f452ba9c4ac9d25d2a05ce878284eca4502116e8 Mon Sep 17 00:00:00 2001
From: nunosmcf <41275244+nunosmcf@users.noreply.github.com>
Date: Tue, 17 Jun 2025 15:20:18 +0100
Subject: [PATCH] Update
 content-transport-using-cloud-transport-management-d458b17.md

Understood this is a prerequisite not mentioned along the setup activities of CTMS for Integration Suite content transport
---
 ...content-transport-using-cloud-transport-management-d458b17.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/ISuite/50-Development/content-transport-using-cloud-transport-management-d458b17.md b/docs/ISuite/50-Development/content-transport-using-cloud-transport-management-d458b17.md
index d95df648..cbb8d085 100644
--- a/docs/ISuite/50-Development/content-transport-using-cloud-transport-management-d458b17.md
+++ b/docs/ISuite/50-Development/content-transport-using-cloud-transport-management-d458b17.md
@@ -11,6 +11,7 @@
 -   You've set the *Transport Mode* as *Transport Management Service* in the tenant *Transport* settings. For more information, see [Enabling Content Transport, Cloud Foundry Environment](enabling-content-transport-cloud-foundry-environment-452c677.md).
 -   You've created necessary HTTP destinations and transport routes. For more information, see [Creating HTTP Destinations and Transport Route](creating-http-destinations-and-transport-route-94057be.md).
 -   You've the role *WorkspacePackagesTransport* for CF or *IntegrationContent.Transport* for Neo assigned.
+-   The "Process Integration Runtime" service (plan: "API") *entitlement* is provisioned for all subaccounts targeted for imports.