# Category \> Security \> Permission type \> Author-only

**URL:** <https://meta.discourse.org/t/category-security-permission-type-author-only/60805>\
**Category:** Feature\
**Created:** [2017 年 4 月 11 日午後 8:39 UTC](https://meta.discourse.org/t/category-security-permission-type-author-only/60805 "2017-04-11T20:39:19Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![trudat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trudat/32/104354_2.png) [@trudat](https://meta.discourse.org/u/trudat)\
**Post date:** [2017 年 4 月 11 日午後 8:39 UTC](https://meta.discourse.org/t/category-security-permission-type-author-only/60805/1 "2017-04-11T20:39:19Z")

</div>

This is a suggestion to add a feature to the category security, to restrict access to a topic to the author. By adding other groups to the category security, e.g. author & tech\_support\_group, you can easily create customized messaging experiences.

In my use case, I would like to have a tech support ticketing system, so a user can report some issue, which may be sensitive or boring to other users, and the topic will only be visible to themselves and anyone in the service group. The ticketing workflow is a common usage pattern that might be called orders, requests, submissions, etc., depending on the community needs

Another use-case of this feature would be to create a Drafts category, for situations when you are not ready to post but want to save your work.

---

_[View the full topic](https://meta.discourse.org/t/category-security-permission-type-author-only/60805)._