This is an IBM Automation portal for Digital Business Automation 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - including Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - including Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Automation Decision Services (ADS) - including ADS, Operational Decision Manager
Robotic Process Automation
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
Specific links you will want to bookmark for future use
Allow option for space permissions to be inherited by default
Currently it is a manual process to make a child space inherit user permissions by default. It can become quite a time intensive task to change all the permissions in all the nodes in a section of the space structure, if one decides to change the user permissions for a section.
Our good practices guidelines for account structuring follow the APQC framework, with account structure separated by eg. project or department, with increasing levels of granularity created via nested spaces. This design is clearly much better suited to assuming a space inherits the parent space permissions by default.
I propose: 1) an option at the parent level space to decide if the child (and all further generation) spaces are to inherit permissions by default. You can still go through and override this in lower generation spaces, it just changes the default option from not inheriting, to inheriting. 1) The ability to turn this feature off and on in the admin panel.
Do not place IBM confidential, company confidential, or personal information into any field.