diff --git a/docs/acap-sdk-version-3/develop-applications/vapix-access-for-acap-applications.md b/docs/acap-sdk-version-3/develop-applications/vapix-access-for-acap-applications.md
index 4b4053a..e248e21 100644
--- a/docs/acap-sdk-version-3/develop-applications/vapix-access-for-acap-applications.md
+++ b/docs/acap-sdk-version-3/develop-applications/vapix-access-for-acap-applications.md
@@ -8,7 +8,7 @@ nav_order: 4
 
 # VAPIX access for ACAP applications
 
-From AXIS OS 11.6, ACAP applications can acquire VAPIX service account credentials in runtime. With these credentials, the ACAP application can call a local virtual host to make VAPIX requests on the device. A username and a password with high complexity are created for every credential acquisition. These credentials are only valid on the local virtual host (127.0.0.12) and aren't stored in any file. It should only be kept in memory by the ACAP application.
+From AXIS OS 11.6, ACAP applications can acquire VAPIX service account credentials with "admin" access level in runtime. With these credentials, the ACAP application can call a local virtual host to make VAPIX requests on the device. A username and a password with high complexity are created for every credential acquisition. These credentials are only valid on the local virtual host (127.0.0.12) and aren't stored in any file. It should only be kept in memory by the ACAP application.
 
 > **Important**
 >
diff --git a/docs/api/native-sdk-api.md b/docs/api/native-sdk-api.md
index c759284..e477f0f 100644
--- a/docs/api/native-sdk-api.md
+++ b/docs/api/native-sdk-api.md
@@ -568,7 +568,7 @@ The curl API was introduced in Native SDK 1.14.
 
 ## VAPIX access for ACAP
 
-ACAP applications can request for VAPIX service account credentials in runtime. With these credentials, the ACAP application can call a local virtual host to make VAPIX requests on the device. See [VAPIX access for ACAP](../develop/VAPIX-access-for-ACAP-applications).
+ACAP applications can request for VAPIX service account credentials with "admin" access level in runtime. With these credentials, the ACAP application can call a local virtual host to make VAPIX requests on the device. See [VAPIX access for ACAP](../develop/VAPIX-access-for-ACAP-applications).
 
 ### Code Examples
 
diff --git a/docs/develop/VAPIX-access-for-ACAP-applications.md b/docs/develop/VAPIX-access-for-ACAP-applications.md
index f806cd4..bee1cec 100644
--- a/docs/develop/VAPIX-access-for-ACAP-applications.md
+++ b/docs/develop/VAPIX-access-for-ACAP-applications.md
@@ -7,7 +7,7 @@ nav_order: 7
 
 # VAPIX access for ACAP applications
 
-From AXIS OS 11.6, ACAP applications can acquire VAPIX service account credentials in runtime. With these credentials, the ACAP application can call a local virtual host to make VAPIX requests on the device. A username and a password with high complexity are created for every credential acquisition. These credentials are only valid on the local virtual host (127.0.0.12) and aren't stored in any file. It should only be kept in memory by the ACAP application.
+From AXIS OS 11.6, ACAP applications can acquire VAPIX service account credentials with "admin" access level in runtime. With these credentials, the ACAP application can call a local virtual host to make VAPIX requests on the device. A username and a password with high complexity are created for every credential acquisition. These credentials are only valid on the local virtual host (127.0.0.12) and aren't stored in any file. It should only be kept in memory by the ACAP application.
 
 > **Important**
 >