# Create/See and Create Permissions (again)

**URL:** https://meta.discourse.org/t/create-see-and-create-permissions-again/33150
**Category:** Feature
**Created:** [September 11, 2015, 11:43pm UTC](https://meta.discourse.org/t/create-see-and-create-permissions-again/33150 "2015-09-11T23:43:22Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [September 12, 2015, 1:03pm UTC](https://meta.discourse.org/t/create-see-and-create-permissions-again/33150/13 "2015-09-12T13:03:07Z")

</div>

Here’s a random idea:

PMs could be _a_ category. Just one. A special, default one, part of the package like Lounge and Meta.

It could use the same principles as the approach suggested for topic archives:

> [@How should category archiving work?](https://meta.discourse.org/t/how-should-category-archiving-work/32895/6):
>
> If you just don’t want your searches getting polluted & slowed down with deprecated posts, and you don’t want archived categories cluttering up your category list, then a “do not search” flag on archived post and a special category that doesn’t show even in staff lists (but retrievable through admin panel somehow) would suffice. Essentially making all topics Unlisted, plus special treatment of the category visibility.

So when you PM someone, your topic ends up in this special “PM Category” that isn’t visible in the normal drop-downs, not even to Admins. So besides the fact that it’s essentially an unlisted topic shared with whichever participants have been invited, you can tag it, wikify it etc., just like you could with any other topic.

(sorry if this seems off-topic, but I think it’s very much _on_-topic, since we’re discussing whether OP’s suggestion is better off dismissed in favor of PMs, which I’m arguing is not the right way to go).

---

_[View the full topic](https://meta.discourse.org/t/create-see-and-create-permissions-again/33150)._
