Skip to content

Commit 8989d4f

Browse files
Merge pull request mendix#10718 from mendix/nc-private-connectivity-updates
Add self-service note to Private Connectivity
2 parents c23c27e + 88d8799 commit 8989d4f

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

  • content/en/docs/control-center/security/private-connectivity

content/en/docs/control-center/security/private-connectivity/_index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ This feature is in Public Beta. For more information, refer to [Release Status](
1515

1616
The **Private Connectivity** page allows you to view and manage your company's Private Connectivity assets: networks, agents, resources, and connections.
1717

18+
{{% alert color="info" %}}
19+
If you cannot access the **Private Connectivity** page, contact your CSM or Mendix Support.
20+
{{% /alert %}}
21+
1822
## Use Cases
1923

2024
Many apps running on Mendix Cloud have integrations with external resources, such as databases, services, and other applications. Some of these resources are public, accessible via the public internet. Others are running on your internal networks, either on-premises or on cloud infrastructure, as PaaS/SaaS. You can connect to these resources over the public internet as well, [securing](/developerportal/deploy/securing-outgoing-connections-from-your-application/) them with HTTPS, a reverse proxy, and client certificates. This scenario requires you to expose your internal resource to the public internet. However, due to security, compliance, or legacy reasons, not everyone wants to or is able to do this.

0 commit comments

Comments
 (0)