# Interacting with Discobot
**URL:** https://meta.discourse.org/t/interacting-with-discobot/96574
**Category:** Bug
**Created:** [9월 6, 2018, 11:36오후 UTC](https://meta.discourse.org/t/interacting-with-discobot/96574 "2018-09-06T23:36:19Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@permacultureProgram](https://meta.discourse.org/u/permacultureProgram)
#### Post date: [9월 6, 2018, 11:36오후 UTC](https://meta.discourse.org/t/interacting-with-discobot/96574/1 "2018-09-06T23:36:19Z")
I’m testing out a new Discourse instance I installed and as part of that process, I am going through the `@discobot` tutorial. One thing that `@discobot` requests is that the user flag one of `@discobot's` posts. However, I was only able to do this after enabling the `allow flagging staff` setting, which, for various reasons, I would like to leave disabled for this instance. This makes the `@discobot` greeting a bit wonky for new users and, to me, feels like a bug. Not sure if there is any way to fix that?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [9월 6, 2018, 11:47오후 UTC](https://meta.discourse.org/t/interacting-with-discobot/96574/3 "2018-09-06T23:47:23Z")
Hmm, this is another release blocking bug @sam – I guess it’s an edge condition since discobot is considered “staff” .. how easy is this to fix @tgxworld?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [9월 7, 2018, 12:18오전 UTC](https://meta.discourse.org/t/interacting-with-discobot/96574/4 "2018-09-07T00:18:13Z")
Discobot has to be staff for lots of reasons. What we would need to do to fix this properly is to make another “non admin” discobot user, we can call it “baddiscobot” or something and have it make the post that gets flagged.
For the release I guess the simplest thing to do here is to omit the flagging step from the flow IF `allow flagging staff` is disabled.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [9월 7, 2018, 2:10오전 UTC](https://meta.discourse.org/t/interacting-with-discobot/96574/6 "2018-09-07T02:10:04Z")
> [@sam](#):
>
> What we would need to do to fix this properly is to make another “non admin” discobot user, we can call it “baddiscobot” or something and have it make the post that gets flagged.
Hmm perhaps we should not apply `allow_flagging_staff` to non-human staff users excluding the system user?
For now, we skip the tutorial if allow\_flagging\_staff is disabled,
[https://github.com/discourse/discourse/commit/c1c9637b3959a8b188a33e2da50e66c31e187a41](https://github.com/discourse/discourse/commit/c1c9637b3959a8b188a33e2da50e66c31e187a41)
> [@charles\_b](#):
>
> Additionally, the advanced tutorial doesn’t work right if delete\_removed\_posts\_after is set to zero since you can’t undelete a post.
This has been handled previously and we actually provide a different narrative if `delete_removed_posts_after` is configured to 0.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [9월 12, 2018, 4:00오후 UTC](https://meta.discourse.org/t/interacting-with-discobot/96574/7 "2018-09-12T16:00:12Z")
This topic was automatically closed after 5 hours. New replies are no longer allowed.