From b071a2b8ab4baf5d2878cfb67f8b5502102a4903 Mon Sep 17 00:00:00 2001 From: Olufunke Moronfolu Date: Tue, 14 Oct 2025 13:58:40 +0200 Subject: [PATCH] feat: info about access violoation --- .../deployment/mendix-cloud-deploy/access-restrictions.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md b/content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md index 4412816105d..91d241e54ea 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md @@ -115,6 +115,10 @@ These are the default settings: * All paths ending in `-doc` have a preset **Deny all access** profile set by default * All the remaining paths have no restriction applied by default +{{% alert color="info" %}} +Following the migration from Cloud Foundry to Kubernetes, access rule violations are now logged in the **Access Log** instead of the **App Log**. For more details on logs, refer to the [Apps Deployed to Mendix Cloud](/developerportal/operate/logs/#apps-deployed-to-mendix-cloud) section of *Logs*. +{{% /alert %}} + ## Use Cases for Access Restrictions Two scenarios in which you can use access restrictions are described below.