Protect sensitive features and configurations from modifications

[Jipegien]

Use case

Some administrative actions and change of configuration through the UI may cause data loss during ingestion, loss of data visibility for users, breaking predefined automation, etc. without sending proper warning to users taking these administrative actions.

We must implement a way to flag elements of the platform to protect them from unwanted and unpondered modifications.

Elements to protect:

• Configuration of specific users, groups, roles
• activation/deactivation of inference rules
• Main platform Organization setting
• Default marking definitions
• Enterprise Edition deactivation
• File indexing pause/reset

Defining and Using a "Protected" element can only be done with a specific Capability. This capability is not bypassable.

Protected Elements can clearly be identified in the UI.

• If you don't have the right capability, the Protected Element is visible but is disabled
• If you have the right capability, the Protected Element is highlighted in strong color, you can use the feature but it needs you to confirm the action (with explicit warning), and you can unprotect the element (explicit warning)