# Assign topics to non-staff users

**URL:** <https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419>\
**Category:** Feature\
**Tags:** assign\
**Created:** [8 במרץ,‏ 2018,‏ 2:13pm UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419 "2018-03-08T14:13:53Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [4 בדצמבר,‏ 2018,‏ 12:14am UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/5 "2018-12-04T00:14:29Z")

</div>

@danekhollas I am actually very mixed on this:

Take for example the following implementation:

- New site setting `assign_allowed_on_all_users` (will have to be a client setting) **default off**

- Client and server site tests that confirm the behavior.

- Staff still is the only type of user that can either assign or unassign.

This restriction that only staff can assign is very likely to break workflows, and then we end up needing even more settings for the wormcan:

`assign_groups_allowed_to_assign` , `assign_assigned_user_can_always_unassign` and so on.

Plus non staff don’t get whispers so then even more goes into this can.

I am tempted to just reject this as something that would just increase the scope of the plugin too much.

---

_[View the full topic](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419)._
