This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
The account data approvals feature has been released which should address this requirement. https://www.ibm.com/docs/en/envizi-esg-suite?topic=managing-approving-account-data
Please reach out to our support team if you have any questions on the new feature. We welcome feedback and suggestions for further improvement via the ideas portal.
Hi @Guest - it depends what the purpose is of the data locking.
The account data approvals feature (due for release in a couple of weeks) will allow already created account records to be locked by changing the approval status of the record. This is good for preventing records from being changed, but it doesn't prevent new records from being added. However even if new records are added, these can always be filtered out by excluding unapproved data in reports.
The data locking epic in discovery is more generic with the intent of allowing a lockdown date to be set at an account, location or group level. The main difference being this would prevent new records from being entered. We may also use this opportunity to expand the scope of the locking to cover other entities that can impact reporting, like tagging or factors.
If the main goal for a client is to lock already entered account records, then the account data approvals feature may be sufficient.
This idea has been linked to an epic in discovery around updating our lockdown function for activity data and emissions. The requirements will also be partially addressed by the account data approvals feature planned for Q2 2025.
Thank you for raising this idea. The ability to implement more granular levels of record locking compared to the organization wide record lock date is being actively investigated. We will update this idea once the discovery work has been completed and the feature has been added to our roadmap.