# Users mistake top-level categories for lack of permissions

**URL:** https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227
**Category:** UX
**Created:** [October 16, 2017, 10:04pm UTC](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227 "2017-10-16T22:04:03Z")
**Posts on this page:** 1
**Showing post:** 30

<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: [April 16, 2018, 1:47am UTC](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227/30 "2018-04-16T01:47:50Z")

</div>

Could we reuse this work here?

> [@Require category selection before writing topic](https://meta.discourse.org/t/require-category-selection-before-writing-topic/66236):
>
> When allow uncategorized topics is disabled, I’d like to propose requiring the user to select a category before they are allowed to start writing the body of the post. The use case for this is a site that makes significant use of topic templates. As users are not required to select a category, many go right to writing their post, and only select a category after they’ve written their post. As there is content in the composer, the topic template is not added, thus negating the usefulness of the …

---

_[View the full topic](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227)._