# RBAC permission required to silence check or entity

**URL:** <https://discourse.sensu.io/t/rbac-permission-required-to-silence-check-or-entity/1265>\
**Category:** Sensu Go\
**Created:** [July 17, 2019, 5:07pm UTC](https://discourse.sensu.io/t/rbac-permission-required-to-silence-check-or-entity/1265 "2019-07-17T17:07:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [July 25, 2019, 7:00am UTC](https://discourse.sensu.io/t/rbac-permission-required-to-silence-check-or-entity/1265/3 "2019-07-25T07:00:48Z")

</div>

Hey,  
I put together a gist with the start for a reusable pattern for good RBAC practice. Can you take a look at it. Now that you have successfully produced an RBAC scheme do you any suggestion on my pattern to make it better?

> [@Jef Practice: Reusable RBAC to setup team namespace for self-service monitoring](https://discourse.sensu.io/t/jef-practise-reusable-rbac-to-setup-team-namespace-for-self-service-monitoring/1204):
>
> Here’s a practical example of using RBAC to provide self-service monitoring for distinct teams in your organization using a single Sensu server configuration. The premise is each team will be running its own agents and will need its own check,assets, and handlers… all the things in a self-service manner…without bumping into each other. Before diving in to this practical example, take a look at this blog post describing how Sensu RBAC works: [https://blog.sensu.io/understanding-rbac-in-sensu-…](https://blog.sensu.io/understanding-rbac-in-sensu-go)

---

_[View the full topic](https://discourse.sensu.io/t/rbac-permission-required-to-silence-check-or-entity/1265)._