Safeguard before publishing or unpublishing an entire channel/web tree

How: Add an additional safeguard when a user publishes or unpublishes a channel or top-level node that affects a large part of the web tree. For example, require a confirmation dialog that clearly states what will be affected and asks the user to explicitly confirm the action. Adding clear warning colors/icons (red text/warning banner) and requiring a double confirmation.

For high-impact actions, the confirmation could show the number of affected nodes/entities and use more explicit wording such as:
"You are about to unpublish the entire WEB channel. This will affect X nodes. Do you want to continue?"

Why: In the new inriver UI, the publish/unpublish action is placed prominently in the top-right corner and is easy to trigger accidentally. The visual difference between performing an action on an individual item and on a whole channel/tree is not clear enough considering the difference in impact.

A simple user mistake can therefore have very large consequences.

For Who: Users responsible for managing channels, web trees and publication in inriver, especially organizations where multiple users have publishing permissions.

Impact: An accidental unpublish of a top-level channel can make a large part of, or potentially the entire, website assortment unavailable.

Additional context: In our case, a user accidentally unpublished the WEB channel/node, which is the foundation of the complete web tree. Restoring the publication required support assistance and created unnecessary operational risk and work.

This became more noticeable after moving to the new inriver UI, where the publish/unpublish controls are positioned in the upper-right corner.

We have already reviewed and limited publishing permissions internally, but users who legitimately need publishing rights still need access to this functionality. Therefore, permission management alone does not fully mitigate the risk.

Please, add your suggestion and feedback above to add to the insights used by Product team when deciding priorities and direction of the Inriver PIM.