This is an IBM Automation portal for Cloud Platform 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.
Specific links you will want to bookmark for future use
As of today, RAM permission model doesn't offer many customization as it only offers the following role permissions: create assets, delete assets, download assets, forums administration, publishing administration, read asset details, search assets, subscribe to assets and update assets. Other than that we must implement policies if we need more fine control, but doing so implies dealing with lifecycle customization that may not apply to all assets inside a community and many other complicated workaround may be needed to achieve a simple permission constraint. As an example, we have the need to allow asset update in matter of attributes, relationship and/or flowing on its lifecycle, but forbidding changes to the asset content itself.
Besides role permissions, given an asset type, we only have constraints for the artifact it contains and its relationship, without any relation to any role/permission. We need more control to deal with asset types, its lifecycle and its attributes accordingly to a given role/permission. Also, it may be needed to be able to set permission not only for communities, but also for asset types and its specific states on the asset lifecycle.
Do not place IBM confidential, company confidential, or personal information into any field.