# 非スタッフユーザーへのトピック割り当て
**URL:** https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419
**Category:** Feature
**Tags:** assign
**Created:** [2018 年 3 月 8 日午後 2:13 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419 "2018-03-08T14:13:53Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@danekhollas](https://meta.discourse.org/u/danekhollas)
#### Post date: [2018 年 3 月 8 日午後 2:13 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/1 "2018-03-08T14:13:53Z")
> Is it possible to add the possibility of assigning topics to users of other groups than staff?
I would be very much interested in this as well.
In a [recent Discourse blog post](https://blog.discourse.org/2018/03/how-does-team-discourse-use-discourse/), there is an allusion to such functionality
> We use a category on our internal instance of Discourse to manage tasks. New tasks are written up in the `todo` category. In some cases they are immediately assigned and in others, we tag a group to give visibility of the task so that a team member can claim it using Discourse Assign.
It does not make sense to me that everybody in their internal Discourse instance is a Staff member…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018 年 3 月 8 日午後 11:08 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/2 "2018-03-08T23:08:21Z")
> [@Discourse Assign](https://meta.discourse.org/t/discourse-assign/58044/78):
>
> It does not make sense to me that everybody in their internal Discourse instance is a Staff member
All our staff on our internal instance are staff barring a few part time people, we may expand the functionality cause we already have assign-public so adding this is not a huge change #pr-welcome for the time being just let me know what you want to call the site setting.
---
### Author:  [@Boubacar\_Sidy\_Diallo](https://meta.discourse.org/u/Boubacar_Sidy_Diallo)
#### Post date: [2018 年 7 月 30 日午後 6:08 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/3 "2018-07-30T18:08:07Z")
Hello,
I have installed the assign plugin 0.1, but it is only accessibles for administrators or moderators. How can I make all users assign their question to anyone ? and see the topic assigned to them
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018 年 7 月 31 日午前 12:07 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/4 "2018-07-31T00:07:04Z")
Not possible at this time.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018 年 12 月 4 日午前 12:14 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/5 "2018-12-04T00:14:29Z")
@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.
---
### Author:  [@danekhollas](https://meta.discourse.org/u/danekhollas)
#### Post date: [2018 年 12 月 4 日午前 10:34 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/6 "2018-12-04T10:34:39Z")
Got it. What if instead of `assign_allow_on_all_users` you’d have something like `assign_allowed_on_groups` where you would explicitly list the user groups? I think in that case you could leave the can of worms closed and just let everybody assign/unassign by default?
To better explain my use case: I run a small non-profit and we use Discourse mainly for internal communication. We have a small stable core team and then lots of volunteers coming in and helping us, possibly for a limited time. It doesn’t make sense for us to make them all staff users, but it would still be nice if we could use this plugin (I am not exactly eager to introduce yet another tool like Trello into our workflow). 🙂
That being said, I completely get your concerns here. 🙂
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018 年 12 月 4 日午後 10:56 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/7 "2018-12-04T22:56:34Z")
I am kind of OK with a setting for `assign_allowed_on_groups` that defaults to `staff` and provides full access to all assign features for the groups selected. I guess from a security perspective this would be nice but I think it is a reasonably big change.
---
### Author:  [@downey](https://meta.discourse.org/u/downey)
#### Post date: [2019 年 4 月 16 日午後 7:41 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/8 "2019-04-16T19:41:24Z")
I have a project that would like to expand the scope of Discourse utility to include a task management tool as outlined in
> [@How we use Discourse as a superior ..... management tool](https://meta.discourse.org/t/how-we-use-discourse-as-a-superior-management-tool/113029):
>
> This post is in reply to @sam’s question, but I think it merits a new topic. I’m the co-founder of an industrial robotics consultancy & training startup from Holland. In many cases, we are flown in once proverbial sh\*t has hit some industrial fan. Once we’ve cleaned stuff up, we train clients to make sure no more fans are hit in that particular location. (As contradictory as it seems, this business model actually works very well. But that for another topic.) We really had to set up a system…
But this feature is pretty much blocking that from happening given the “must be a moderator to get assignments” situation:
> [@How we use Discourse as a superior ..... management tool](https://meta.discourse.org/t/how-we-use-discourse-as-a-superior-management-tool/113029/1):
>
> _Note: it would be great if we could assign tasks to users who are non-Admin/Moderator users. For us it’s a bit unfortunate that we have to make someone a moderator to be able to assign them tasks)._
Curious if anyone is working on this currently? Or anyone else is thinking about it?
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [2019 年 4 月 16 日午後 8:39 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/9 "2019-04-16T20:39:31Z")
Really hoping this happens too.
My temporary workaround has been to deploy a whole additional discourse instance to avoid any problems relating to making users Moderators of the main instance.
---
### Author:  [@Cozdabuch](https://meta.discourse.org/u/Cozdabuch)
#### Post date: [2019 年 4 月 17 日午前 1:56 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/10 "2019-04-17T01:56:52Z")
Please do! Assign to users is fantastic when discourse is used as an internal closed employee collaboration board for project or a specific thread/topic management!
Not too useful IMO for public boards, but employee collaboration boards it is for sure
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2019 年 4 月 17 日午前 1:56 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/11 "2019-04-17T01:56:59Z")
@Roman adding this to your list after you are done with the current pipeline of tasks for assign.
In particular `assign_allowed_on_groups` site setting. Any members of those groups can also participate in assign.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [2019 年 4 月 22 日午後 7:34 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/12 "2019-04-22T19:34:12Z")
Awesome timing, that means I can demote those users before too many more get involved.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [2019 年 5 月 12 日午後 8:38 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/13 "2019-05-12T20:38:26Z")
Just a thought, but as category moderation is now a thing can that also be tied into `assign allowed` for those categories? It could be a substitute too for having separate assign allowed groups who don’t have moderation ability.
---
### Author:  [@Roman](https://meta.discourse.org/u/Roman)
#### Post date: [2019 年 5 月 13 日午後 7:26 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/14 "2019-05-13T19:26:04Z")
I just finished working on some PRs to add this feature.
[https://github.com/discourse/discourse-assign/pull/31](https://github.com/discourse/discourse-assign/pull/31)
Most of the heavy-lifting was done here because I had to change the _admin OR moderator_ scope to _user of an allowed group_
* * *
[https://github.com/discourse/discourse/pull/7538](https://github.com/discourse/discourse/pull/7538)
Here I added support for multi-group user search which is used by the assign modal. Sadly, older discourse instances running the plugin will only be able to search for `staff` members since it will be the fallback option.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [2019 年 6 月 3 日午後 9:01 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/15 "2019-06-03T21:01:32Z")
Just wanted to get an update, are we still waiting on this one?
[https://github.com/discourse/discourse-assign/pull/31](https://github.com/discourse/discourse-assign/pull/31)
---
### Author:  [@Roman](https://meta.discourse.org/u/Roman)
#### Post date: [2019 年 6 月 3 日午後 9:48 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/16 "2019-06-03T21:48:17Z")
Sorry for keeping everyone out of the loop regarding the state of this feature.
The only reason for this not being merged yet is because I want to improve how the setting works. Right now, if a group gets renamed or deleted, the list of allowed groups will be in an inconsistent state.
Hopefully, I’ll make the necessary changes this week and merge it. I’ll keep everyone posted
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [2019 年 6 月 3 日午後 10:02 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/17 "2019-06-03T22:02:09Z")
No worries, had been following the two PRs on github and could see the back-and-forth on the other one. Just wanted to understand if there was some form of blocking issue or bigger problem.
---
### Author:  [@Roman](https://meta.discourse.org/u/Roman)
#### Post date: [2019 年 6 月 4 日午後 3:38 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/18 "2019-06-04T15:38:40Z")
I did the changes and merged it this morning. I have been using the feature a little bit here on meta without problems so far.
To fully work, the feature depends on `.beta10` changes. Otherwise, It’ll only work for staff members.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [2019 年 6 月 7 日午後 9:20 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/19 "2019-06-07T21:20:34Z")
Updated and testing, looks great so far.
---
### Author:  [@Roman](https://meta.discourse.org/u/Roman)
#### Post date: [2019 年 6 月 11 日午後 2:49 UTC](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419/20 "2019-06-11T14:49:10Z")
The following PR allows staff members to always be able to assign:
[https://github.com/discourse/discourse-assign/pull/36](https://github.com/discourse/discourse-assign/pull/36)
There are cases where the `staff` group is renamed.
I’m leaving this here in case someone has any comments. cc @featheredtoast
[次のページ](https://meta.discourse.org/t/assign-topics-to-non-staff-users/103419.md?page=2)