[BUG]: Missing context of delete comment under cases sub-future.

[ghost]

Description:
Missing context of delete comment under cases sub-future.

URL:
https://www.elastic.co/guide/en/security/current/case-permissions.html

Expected:

Screenshot:

[nastasha-solomon]

@jonathan-buttner can users be given privs to delete case comments only? Or, are they only able to delete case comments
if their role has Read or higher case feature privs + the Delete sub-feature priv enabled?

Also, moving forward, will theDelete sub-feature priv encompass all other case sub-features? For example, will the scope of this sub-feature priv eventually expand to include deleting elements like user actions and alerts?

cc: @lcawl

[lcawl]

According to the current docs, the prerequisites for the delete comments and delete cases are the same. My preference would be for these reference pages to be the source of truth rather than going into that level of detail in the Security, Observability, and Stack Management prerequisite overviews.

[jonathan-buttner]

@jonathan-buttner can users be given privs to delete case comments only?

No, you can't give users privileges to only delete case comments. Once they are given deletion privileges they can delete all entities within cases (most notably cases and comments).

Or, are they only able to delete case comments if their role has Read or higher case feature privs + the Delete sub-feature priv enabled?

Users can delete case entities if they have the deletion sub feature privilege granted to them. Theoretically it'd be possible for them to only have deletion privileges (even if they have no read access, they'd have to create the role through the core security APIs directly though) and they'd be able to delete cases and comments through the cases APIs.

[nastasha-solomon]

Thanks @jonathan-buttner and @lcawl!

@lcawl I agree that the case API docs can be the source of truth and provide more granular details about the access privs provide.

[lcawl]

I ultimately added mention of the ability to delete comments and alerts in the setup docs via elastic/observability-docs#2333 and #2678