# What governs visibility of configured rules in Rules and Connectors tab?

**URL:** <https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297>\
**Category:** Kibana\
**Tags:** elastic-stack-alerting\
**Created:** [August 17, 2022, 2:31pm UTC](https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297 "2022-08-17T14:31:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [August 17, 2022, 2:31pm UTC](https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297/1 "2022-08-17T14:31:39Z")

</div>

Hello,

I wanted to allow low lvl user to see configured rules. The rules are configured in separated to user main dashboard so I had to start by adding rights to see the rules's dashboard. So I added the right to check "stack rules" in that dashboard

Added rights to check "Rules and Connectors"the to user role.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/e/4edcc0dbb0379ff3a798b2786180d41e0535a7f8.png)

**This is what the user can see**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/a/4a7c6adc18824d4b64a92a985552bc038810903d.png)

**This is what is there**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/8/18371bb12c5500c5c675943726723eb821e20c14.png)

When I was setting this rules I was using "elastic" user

This are the overall rights of the user

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/9/a99978473d52d8d36b0f9a6ee2c9f7d4a9ee600a.png)

Current Stack ver is 7.17-5

I also think that I was adding the alerts that are not visible on the Kib version 7.17-1 and the one that are visible on the 7.17-5 maybe 7.17-4.

---

<div class="post-metadata">

**Author:** ![EricDavisX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ericdavisx/32/73456_2.png) [@EricDavisX](https://discuss.elastic.co/u/EricDavisX)\
**Post date:** [August 17, 2022, 5:09pm UTC](https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297/2 "2022-08-17T17:09:57Z")

</div>

Hi - thanks for writing in. Let me cite the following:

- The 'Stack Rules' Privilege determines if you can see the Rules management at all, and also allows the non-solution-specific rules to display (as you are seeing)
- The 'Security' privilege in a role determines if a user can see the Security App and any rules in it.
- The Analytics level privilege 'Machine Learning' governs if a user can see the ML relating rules

Then, the Observability group of rules is broken into 2 sections:

- the built in role 'monitoring\_user' is required for users to see any Stack Monitoring UI and its relating Rules
- and finally the individual Observability feature sets govern the access/use of their relating rules, APM, Uptime, Logs, Metrics, are required to see the rules of those specific types.

So it is a combination of up to 7 privileges and the 'monitoring\_user' role (if you wish to use stack monitoring rules)

see screenshot below. If you set it to 'read' the user can see any existing rules, and when set to 'all' they can create and edit them. Hope this helps!

 ![Screen Shot 2022-08-17 at 1.03.39 PM](https://us1.discourse-cdn.com/elastic/original/3X/e/a/eafd90be6ff22e03f24ab8dc677cb64b5280b343.png)

 ![Screen Shot 2022-08-17 at 12.52.57 PM](https://us1.discourse-cdn.com/elastic/original/3X/3/4/34360787c20f5ed45e90e261553e0b2526f4197e.png)

---

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [August 18, 2022, 8:17am UTC](https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297/3 "2022-08-18T08:17:03Z")

</div>

Thank you Eric. Without your help, I would probably use a lot of time figuring this out.

I can confirm that this works as explained by you

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e1530a105b69d71774c9052305e68e4df71f8bc.png)

What bothers me is why I did not get this from the documentation. Did I miss or misunderstand some part of It or is it just lacking?

---

<div class="post-metadata">

**Author:** ![EricDavisX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ericdavisx/32/73456_2.png) [@EricDavisX](https://discuss.elastic.co/u/EricDavisX)\
**Post date:** [August 18, 2022, 12:34pm UTC](https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297/4 "2022-08-18T12:34:03Z")

</div>

Hi - I think you have found a documentation bug, it wasn't fully clear to me either. I have put this ticket in to the Kibana repo and raised it to the Documentation team for review:

> <https://github.com/elastic/kibana/issues/139099>
>
> \*\*Kibana version:\*\* 8.5 and prior
> 
> \*\*Describe the bug:\*\*
> Kibana doesn't have …documentation that cites which privileges are required to see which Alert types.
> 
> In more detail: It isn't immediately clear that the the Uptime (monitoring) and Logs, Metrics, Stack, Security, and ML rules are all governed by separate different feature level options. We have had Discuss questions arise from this.
> 
> \*\*Steps to reproduce:\*\*
> 1. Create a Monitoring rule, a security rule, a Log rule and an ES Query rule, as Elastic user
> 2. With a user with only 'Stack Rules' privilege in their role log in and note you cannot see the other rules
> 3. This is fairly confusing without more detail in the rule documentation to explain it
> 
> \*\*Expected behavior:\*\*
> Product behavior is ok, just need better docs to explain how to use it
> 
> \*\*Screenshots (if relevant):\*\*
> Here are the 7 privileges, not including the built-in separate monitoring\_user role required:
> !\[Alert-relating-privileges\](https://user-images.githubusercontent.com/12970373/185395067-abae63a3-5546-445f-8f16-762e6d76cc26.png)
> 
> Here is the example showing which privs map to the different Alert types. This explicitly could be added to docs somewhere, maybe a new section in Kibana Alerting if one doesn't exist.
> !\[privileges-go-to-rules\](https://user-images.githubusercontent.com/12970373/185395177-19924447-8abd-44e3-9862-fcaa86474c98.png)
> 
> showing the monitoring\_user built in role, fyi:
> !\[monitoring\_user\_role\](https://user-images.githubusercontent.com/12970373/185395363-dc67bdc9-6d82-4aba-bde1-0bdb5dea0325.png)
> 
> 
> \*\*Any additional context:\*\*
> Relating discuss link: https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297

Please feel free to add more context or add any separate concerns you have now or in the future.

Regards

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 15, 2022, 12:34pm UTC](https://discuss.elastic.co/t/what-governs-visibility-of-configured-rules-in-rules-and-connectors-tab/312297/5 "2022-09-15T12:34:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
