# Possible to Restrict Wildcards Per User?

**URL:** <https://community.hivemq.com/t/possible-to-restrict-wildcards-per-user/452>\
**Category:** Uncategorized\
**Created:** [February 24, 2021, 4:52pm UTC](https://community.hivemq.com/t/possible-to-restrict-wildcards-per-user/452 "2021-02-24T16:52:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnHive](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@JohnHive](https://community.hivemq.com/u/JohnHive)\
**Post date:** [February 24, 2021, 4:52pm UTC](https://community.hivemq.com/t/possible-to-restrict-wildcards-per-user/452/1 "2021-02-24T16:52:12Z")

</div>

I know there is a way to disallow wildcard subscriptions. Is there a way to do this that restricts wildcards for some users but not others?

Thanks!

---

<div class="post-metadata">

**Author:** ![abdullah.imal](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/abdullah.imal/32/16_2.png) [@abdullah.imal](https://community.hivemq.com/u/abdullah.imal)\
**Post date:** [February 25, 2021, 9:42am UTC](https://community.hivemq.com/t/possible-to-restrict-wildcards-per-user/452/2 "2021-02-25T09:42:51Z")

</div>

This can be done easily with the [File RBAC Extension](https://github.com/hivemq/hivemq-file-rbac-extension). There is an example in the readme file how to set the required permissions.

You can also create your own extension by using the [HiveMQ Extension System](https://www.hivemq.com/docs/hivemq/4.5/extensions/authorization.html).

Hope that helps,  
Abdullah

---

<div class="post-metadata">

**Author:** ![JohnHive](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@JohnHive](https://community.hivemq.com/u/JohnHive)\
**Post date:** [February 25, 2021, 3:27pm UTC](https://community.hivemq.com/t/possible-to-restrict-wildcards-per-user/452/3 "2021-02-25T15:27:06Z")

</div>

Hi Abdullah,

Thanks for responding! I am using that plugin, however I notice that you can specify wildcards that indicate which topics a client can subscribe to, but you cannot specify a client should not be able to subscribe to a wildcard. Does that difference make sense, for example, I am able to specify a user can subscribe to:

home/+ (which would allow them to subscribe to home/t1, home/t2, etc)

but I want each client to have to concretely subscribe to home/t1, not home/+.