Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Feb 10, 2017

Need a way to restrict user job lists based on user groups

This is a request for the new Application Centre release.

The requirement is to enable the admins to separate the users based on LSF groups and be able to use that separation and prevent users from peaking into other user's jobs in the list, unless they are allowed to.

  • Guest
    Reply
    |
    Feb 15, 2017

    This is currently supported within the scheduler to restrict what information is visible via the cli and api

    SECURE_JOB_INFO_LEVEL=0|1|2|3|4
    Defines an access control level for all users. Specify a level (0 to 4) to control which jobs users and administrators (except the primary administrator) can see.
    0=all information is visible
    1=user can only see summary info for jobs not in their group
    2=user can see their own jobs, and details of jobs in the same group
    3=User can see their own jobs, and summary info from users in the same group
    4=User can only see their own jobs

    ENABLE_JOB_INFO_BY_ADMIN_ROLE = [usergroup] [queue] [cluster]
    By default, an administrator's access to job details is determined by the setting of SECURE_JOB_INFO_LEVEL, the same as a regular user. The parameter ENABLE_JOB_INFO_BY_ADMIN_ROLE in lsb.params allows you to enable the user group, queue, and cluster administrators the right to access job detail information for jobs in the user group, queue, and clusters they manage, even when the administrator has no right based on the configuration of SECURE_JOB_INFO_LEVEL. You may define one or more of the values, usergroup, queue, or cluster.