Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace IBM Z ChatOps
Created by Guest
Created on Jan 16, 2025

Restricting access to specific bot commands and command options for specific users and/or globally.

Introduce "read-only" access mode limited to getting system status. Blocking any possibility to perform any task (like stopping resources) which could change system state.

Idea priority High
  • Admin
    Wolfgang Schäberle
    Reply
    |
    Jan 17, 2025

    Thanks for opening this Idea. We will evaluate it.
    Just one comment upfront. Actions like starting/stopping resources driven through the chatbot do have additional security built in. The chatbot will prompt for a TSO user ID and password that the user has to provide when trying to submit such a command via the chatbot. The given credentials will then be checked against the security backend on z/OS - such as RACF.
    I agree that on top of that we could add a property that already hides these kind of actions at the chatbot level and we will consider that as a usability improvement.
    But the current implementation should not be a security issue and prevent using the solution.
    Please let me know your thoughts on this aspect. Thanks.