Approve posts before they go public | Feature Requests

Approve posts before they go public

closed

Sarah Hum

Send posts to an approval queue. Admins can decide if they want to make it public.

Sarah Hum

marked this post as

closed

Pinned

We've thought about this quite a bit and have decided that turning off new posts is a better solution here. Instead of building an entire inbox/queue system in Canny, most teams already use support solutions like Intercom or Zendesk that are effective inboxes. If you felt strongly about this feature, we recommend turning off new posts and having people contact you to get new ideas on the list. Hope this makes sense!

Southern Snake

we have 25,000 professional users, and we are afraid of having too many personal requests or that do nothing for the community

So we prefered approve pots befor they go public.

Strong Emu

Why cant we just have a simple toggle on post if its public & all new posts should not be visible for all users, until admin approves it.

Sarah Hum

marked this post as

closed

Sharp Mandrill

Sarah Hum: Glad you discussed but this isn't really a solution!
Whole idea of paying for a tool like Canny is to get users to post feedback themselves and reduce as many barriers to that as possible (so we use the widget to embed it in our app, use SSO so they don't need to login to a separate system etc).
To turn off posting and make them send feedback  to another platform for us to manually copy into Canny seems like more work for us than skimming posts for any inappropriate/confidential content and clicking approve. It also just adds complexity for the user if we say, here's the feedback portal, comment and vote on others ideas but you have to send an email to us to add new feedback.
Can I ask, is it about effort to deliver the feature or disagreeing with the concept of adding moderation? Because personally I think an extra status that is only visible to admins and the post author would be enough, no need to worry about a whole other admin UI for it or anything.

Desperate Kite

Sarah Hum: This is a disappointing decision. I agree with Baffour.

Peach Gorilla

Sarah Hum: I'll throw my agreement on the list as well. I think Baffour described it best.

Jolly Bass

Sarah Hum: This is quite frustrating and it's clear from this thread that your customers don't agree with your position. Turning off posts is a very harsh response to a widespread issue (judging by the number of votes) that has a simple solution. There's a middle ground here. We want people to post but with the ability to moderate content that doesn't belong in Canny before it ends up wasting people's time/distracting our users. W.r.t. "If you felt strongly about this feature, we recommend turning off new posts...," I'm fairly certain everyone here is aware that we can turn off new posts which is not a feature substitute -- it's a different feature. 
Support is an obvious example here: Inevitably, users are going to submit one-off support tickets to Canny even if they are instructed not to. I've seen this on practically every Canny site I've ever stumbled upon. 
Discourse does a great job flagging spam, inappropriate posts, etc., especially from first-time users. I recommend checking that out. 
I don't get how Intercom and Zendesk inboxes are related here. Yes, those tools exist but what does that have to do with the issue at hand? Canny posts do not go through those systems. 
There's no downside here other than the feature work. I get that this is work and it's a grind to get through requests like these but the reason tools like Discourse are so widely popular is because organizations are not blocked in using them. 
In any case, I feel strongly that this topic merits more discussion and shutting it down is not the right response.

Peach Gorilla

This feature is very important to us. We need to ensure that anyone posting content to Canny doesn't accidentally expose sensitive or business critical information. If one of our customers makes a post containing critical information about tech deals or architecture that isn't public knowledge, they could get in trouble and it could put us at risk as well.

Olive Beaver

Post Approval will definitely help us keep our Canny requests organized and clutter free. We often receive posts about features we already have or users asking questions which results in more workload. We'd appreciate if you guys could work on adding this feature on your upcoming updates.

Ivory Shark

Our software has a lot of features. This means users are writing in and leaving what we call "support" Canny posts, which are posts about features we already have or just asking questions. It would be great to not have these posts slip by us or end up being voted on. Since we can't customize statuses yet we choose to mark these as complete instead of closed (users didn't like it as much), but it makes it look like we just added the feature since it goes to our roadmap.

Being able to approve posts before they hit the real board would be amazing!

Wee Blackbird

We'd like this too - it's a way of enabling safe-but-anonymous feedback mechanisms.

Zeroth Damselfly

Our company really needs this functionality. Here in Brazil, we usually say the following "Brazilians have no limits, they need to be studied by NASA." That's because there will certainly be abusive and even malicious posts and comments.

Zygomorphic Grasshopper

This is an important use case for us —we want to provide the transparency of sharing feature requests but want it to flow through an account manager so we fully understand the issue or potentially resolve the feedback before it gets added. In addition we have a mix of both highly technical and non-technical users which can lead to inappropriate posts being added. Moderating after the fact would require much more constant effort than an approval queue.

Valid Alligator

This way we can filter out inappropriate feature requests before they are being published on our feature request page :)

→