From 2e42c9e2ba9249e9b70ebda745eb88f6619015de Mon Sep 17 00:00:00 2001 From: arooshlele Date: Mon, 27 Oct 2025 18:42:08 +0530 Subject: [PATCH] Updating configuring-security.md Signed-off-by: arooshlele --- .../version-v3.0.x/user-guide/configuring-security.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/versioned_docs/version-v3.0.x/user-guide/configuring-security.md b/versioned_docs/version-v3.0.x/user-guide/configuring-security.md index 520c5622e8..232a691036 100644 --- a/versioned_docs/version-v3.0.x/user-guide/configuring-security.md +++ b/versioned_docs/version-v3.0.x/user-guide/configuring-security.md @@ -10,6 +10,15 @@ For initial tasks to be performed by the security administrator before Zowe serv ::: +:::note +For the users of Zowe who are not database administrators, administrators, or superusers, the minimum access requirements are as follows: + +- z/OSMF Access: The user must be a member of the IZUUSER group (membership in IZUADMIN is optional and provides additional privileges if required). +- USS Access: The user ID must have an ** OMVS segment defined to interact with UNIX System Services. +- Dataset and USS Permissions: The user requires the standard RACF/ACF2/Top Secret permissions to access datasets and USS files. + +::: + ## Validate and re-run `zwe init` commands During installation, the system programmer customizes values in the zowe.yaml file. However, due to insufficient permissions of the system programmer, the `zwe init security` command may fail without sufficient user authorization.