Drag and Drop articles to get confirmation before action is performed.
under review
Vikram Krishna Kannan
Raising this request on behalf of Curtis:
Currently, Draft Writers, Reviewers, and other roles have the option to move articles and categories using drag-and-drop.
This presents an issue when an article or category is moved to a different location where the destination has access controls that may not be relevant. It becomes a security concern to move content into areas with different permission sets.
To address this, we should implement a notification popup that appears when articles or categories are moved. This popup should include a note stating that the destination's access controls will be inherited once the action is performed, along with an option to confirm the movement. This will help limit the accidental relocation of content and ensure the user is aware that the destination access rights will be applied.
Log In
Mohamed Shakheen
marked this post as
under review
Mohamed Shakheen
HI Vikram
Thank you for raising this request on behalf of Curtis.
Currently, users with roles such as Draft Writers, Reviewers, and other permitted roles can move articles and categories through the drag-and-drop functionality. When content is moved to a different category, it automatically inherits the access controls configured for the destination category.
We understand the concern regarding unintentional movement of content into categories with different permission configurations, which could lead to unintended visibility or access changes.
Introducing a confirmation notification before completing the drag-and-drop action, clearly informing the user that the destination category’s access controls will be inherited, is a valid enhancement from both a usability and governance standpoint. This would help reduce accidental relocations and ensure users are aware of the potential access control impact before confirming the move.
We will review this request internally to evaluate feasibility and determine how it can be incorporated into the roadmap. Once we have more clarity on the approach and prioritization, we will share an update.