Skip to content

Conversation

@ArooshLele
Copy link
Collaborator

Describe your pull request here:
As discussed with @DivergentEuropeans Lenny, a Note related to Security permissions is added into this file.

List the file(s) included in this PR:
configuring-security.md

After creating the PR, follow the instructions in the comments.
CC: @ArooshLele @DivergentEuropeans @1000TurquoisePogs @gauravs-20

@github-actions
Copy link

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

  • Add the label review: doc.
  • Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
  • Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
    • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
  • Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
  • Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

@ArooshLele ArooshLele added review: sme Needs review by an SME area: docs Documentation issue or issues that have documentation impact release: V3 Zowe V3 content area: install and config Issues related to z/OS install and config priority-medium labels Oct 27, 2025
@github-actions
Copy link

@github-actions github-actions bot temporarily deployed to pull request October 27, 2025 13:27 Inactive
Copy link
Member

@1000TurquoisePogs 1000TurquoisePogs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good topic to improve, but I don't think it will be seen or understood in the place you put your info.

  1. you have only made a v3.0.0 doc, but if you're trying to update documentation people will see, you need to do a v3 latest doc, and then to get the widest audience, update all the versioned_docs (like this, but all the others too)

  2. The page you've edited is in the context of action items for admins to do to set up the zowe server security setup. You've added a section talking about zowe user security setup. I just don't think this is in the right section.
    I'm not sure there is a good place to put this currently, you may need to create a new page to better represent this, and reorg the more visible pages to point ot it.
    Check out

https://github.com/zowe/docs-site/blob/master/docs/user-guide/address-security-requirements.md

it (and the page you edited) reference

https://github.com/zowe/docs-site/blob/master/docs/user-guide/assign-security-permissions-to-users.md

At the bottom of that, there's a section about users.

As it is, that page saying 'users' at the top is misleading, because most of the page is about permissions of the STC account, not users. The bottom of the page is however about users.

I suggest

  1. renaming https://github.com/zowe/docs-site/blob/master/docs/user-guide/assign-security-permissions-to-users.md to 'assign security permissions to STC accounts'
  2. make a page that's actually about users, and populate it with content like you wrote, among other things.

Copy link
Collaborator

@anaxceron anaxceron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sean's comments seem very pertinent.

I also left some comment re: minor edits.

:::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).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest moving the parenthetical into a sub-bullet (and removing the parentheses)

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the asterisks be in backticks? Like: "... have an ** OMVS segment defined ... "


- 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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Data set should be two words.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation issue or issues that have documentation impact area: install and config Issues related to z/OS install and config priority-medium release: V3 Zowe V3 content review: doc Needs review by Doc Squad member review: sme Needs review by an SME

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants