RBAC for ChatOPS should also apply to help

Just finished watching the AHH and when you get to RBAC for ChatOPS (I know it's awhile off) I though it should really cover help too as with different levels of technical and non-technical users possibility being in ChatOPS having things like the following:

! st2 executions get {{ id }} - Retrieve details for a single execution.
! st2 executions re-run {{ id }} - Re-run an action execution.
! st2 executions show {{ id }} - Retrieve details for a single execution.
! st2 get execution {{ id }} - Retrieve details for a single execution.
! st2 list actions - List available StackStorm actions.
! st2 list actions from {{ pack }} - List available StackStorm actions.
! st2 list executions - List available StackStorm executions.
! st2 list executions for action {{ action }} - List available StackStorm executions.
! st2 list executions with status {{ status }} - List available StackStorm executions.
! st2 list rules - List available StackStorm rules.
! st2 list rules from {{ pack }} - List available StackStorm rules.
! st2 list sensors - List available StackStorm sensors.
! st2 list sensors from {{ pack }} - List available StackStorm sensors.
! st2 re-run execution {{ id }} - Re-run an action execution.
! st2 show execution {{ id }} - Retrieve details for a single execution.

Showing up in help it would be really confusing for someone from say from finance, also deployment of packs via these commands could lead to rather bad things if the user did not really understand the impact.

! pack deploy {{packs}} - Download StackStorm packs via ChatOps
! pack deploy {{packs}} from {{repo_url}} - Download StackStorm packs via ChatOps

Jon.

Start by locating StackStorm's ChatOps command and help handling, then trace the existing RBAC behavior; the issue names no files or tests. Define which help entries and pack deployment commands each role may see or invoke, with completion meaning unauthorized commands and sensitive help are consistently excluded.