Issue 437: Maintenance permission

[narcher7]

No description provided.

[spong]

Referenced images will need to be updated as well:

[spong]

So the intent behind elastic/kibana#87761 was to allow the creation of a user (role) that can change alert state (open/in-progress/closed), but not have the ability to create/edit rules. Can we create a third group like Access and use Detections for this role and call out this behavior? It'd essentially be what the newly updated Access and use Detections section (w/ maintenance) and a change of Kibana space privileges to Security Solution read, if I recall correctly.

[narcher7]

Preview

[spong]

There's a bit to un-pack here @Donnater @jmikell821, so please do reach out as I'm happy to pair on this one.

Notes:

[1] As of elastic/kibana#90895 the Saved Objects Management feature privilege is no longer necessary, and can be removed from both sections. This change is for 7.12, not 7.11

[2] For the Enable Detections section maintenance isn't necessary as the manage privilege will satisfy the same permissions.

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
5f8e162, 660ccfc

Please, read and sign the above mentioned agreement if you want to contribute to this project

[narcher7]

Preview

[spong]

LGTM! Thanks for pairing on this one to get everything just right @Donnater, appreciate it! 🙂