# Role assignment with resource filters

**URL:** <https://community.auth0.com/t/role-assignment-with-resource-filters/51288>\
**Category:** Get Help\
**Tags:** authorization-core, authorization, rbac\
**Created:** [October 8, 2020, 8:44pm UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288 "2020-10-08T20:44:48Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanjeevchopra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sanjeevchopra/32/24808_2.png) [@sanjeevchopra](https://community.auth0.com/u/sanjeevchopra)\
**Post date:** [October 8, 2020, 8:44pm UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288/1 "2020-10-08T20:44:48Z")

</div>

Hello,

I have seen Kim Maida’s posts on RBAC and Authorization extension. Wanted to know if Auth0 is considering the use case of resource filtering.

Specifically, let’s say a group of users has role `Device Operator`, but only for devices with classification of `xyz`. In this case, I would like to store an opaque “filter string” with the assignment which is made available at the time of authorization (in a rule context or token).

Then the resource service can use this filter to further restrict which devices, a user in that group will be allowed to access.

Thanks

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 9, 2020, 10:30am UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288/2 "2020-10-09T10:30:31Z")

</div>

Hey there,

As far as I know it’s not doable as of now using our stack unfortunately. I would highly suggest filing in a feature request to our product managers using our product form:

> **[Auth0: Secure access for everyone. But not just anyone.](https://auth0.com/feedback)**
>
> Rapidly integrate authentication and authorization for web, mobile, and legacy applications so you can focus on your core business.

---

<div class="post-metadata">

**Author:** ![sanjeevchopra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sanjeevchopra/32/24808_2.png) [@sanjeevchopra](https://community.auth0.com/u/sanjeevchopra)\
**Post date:** [October 9, 2020, 5:06pm UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288/3 "2020-10-09T17:06:25Z")

</div>

Thanks @konrad.sopala. I will do that.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 12, 2020, 9:35am UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288/4 "2020-10-12T09:35:06Z")

</div>

Thanks! The more people advocating for certain feature and filing in feature requests we have the more likely that feature will get implemented

---

<div class="post-metadata">

**Author:** ![sanjeevchopra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sanjeevchopra/32/24808_2.png) [@sanjeevchopra](https://community.auth0.com/u/sanjeevchopra)\
**Post date:** [August 27, 2021, 5:07pm UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288/5 "2021-08-27T17:07:18Z")

</div>

If you’d like to vote, feature request for this is at: [Role assignments with a resource filter](https://community.auth0.com/t/role-assignments-with-a-resource-filter/68700)

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [August 30, 2021, 12:20pm UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288/6 "2021-08-30T12:20:16Z")

</div>

Thanks for sharing the link with the rest of community!

---

<div class="post-metadata">

**Author:** ![cyrilchapon](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/cyrilchapon/32/11392_2.png) [@cyrilchapon](https://community.auth0.com/u/cyrilchapon)\
**Post date:** [July 29, 2022, 11:58am UTC](https://community.auth0.com/t/role-assignment-with-resource-filters/51288/7 "2022-07-29T11:58:17Z")

</div>

While the resource-filter might not be the only approach to this; the use-case in itself seems so obvious that it’s actually shocking it’s not achievable in the current state of art of Auth0. (and it’s been a while now).

Some use-cases :

- Facebook-like groups / pages management. A user is owner of a group, some others are admin — with specific permissions, moderators. Some users are simple consumers.
- Google Drive-like file management. A user (or a domain) is owner of a file, some others are editors, some others are readers
- Auth0 backoffice itself : a user can be superadmin of a tenant, and simple admin of another

In any of those use-cases, the topic remains the same : a role is tightly coupled with a “resource instance” and not only a “resource type”. That’s what is called a “relation” on that post and others about the same topic.

NB : Please note that there is a common confusion and misuse of langage out there with the term “resource”. Browsing the web about that topic, using “resource” is sometimes related to the “resource type” (Dogs), sometimes to the “resource instance” (Dog with id: 1234). We’re talking here about “resource instance”
