# 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:** [16 Outubro , 2017 22:04 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:** 6
**Page:** 2

<div class="post-metadata">

### Author: ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [22 Janeiro , 2018 03:11 UTC](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227/23 "2018-01-22T03:11:33Z")

</div>

PR is up: [enable New Topic button when user can post to subcategory by pmusaraj · Pull Request #5516 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/5516)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [19 Fevereiro , 2018 02:45 UTC](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227/25 "2018-02-19T02:45:25Z")

</div>

I reviewed the PR but unfortunately it introduces another AJAX call for the “standard case” which is not acceptable.

I also question not selecting anything, if someone clicks “New Topic” on “Feature” and then it goes to the “first item” in the category list, well it will cause “different” confusion.

- Why is it selecting “bug” when I do “new topic” in feature?

I think the correct way to go about this @Drew_Warwick is simply to allow creation of topics on “feature” and add a topic template there that warns them to select a proper feature subcategory.

 ![image](https://global.discourse-cdn.com/meta/original/3X/d/f/df006524931991d4e7fcfb23e7ca1f2f41af75ab.png)

---

<div class="post-metadata">

### Author: ![McBlu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcblu/32/91128_2.png) [@McBlu](https://meta.discourse.org/u/McBlu)
#### Post date: [19 Fevereiro , 2018 03:02 UTC](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227/26 "2018-02-19T03:02:18Z")

</div>

Gday,

One way to solve this might be to not show topics under the category, just subcategories. Then members would be more likely to go to the subcategories. I want that for a different reason as discussed here. 🙂

[https://meta.discourse.org/t/remove-topics-listed-under-sub-categories-that-are-also-in-the-sub-categrories/80901](https://meta.discourse.org/t/remove-topics-listed-under-sub-categories-that-are-also-in-the-sub-categrories/80901)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [19 Fevereiro , 2018 05:29 UTC](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227/28 "2018-02-19T05:29:08Z")

</div>

> [@McBlu](#):
>
> One way to solve this might be to not show topics under the category, just subcategories.

Hmmm interesting. Maybe a theme component like this would help. But you lose out on being able to browse all of the parent category in one spot which may be a problem for some people.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [19 Fevereiro , 2018 06:40 UTC](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227/29 "2018-02-19T06:40:21Z")

</div>

Looking at:

[https://meta.discourse.org/t/remove-topics-listed-under-sub-categories-that-are-also-in-the-sub-categrories/80901/16?u=sam](https://meta.discourse.org/t/remove-topics-listed-under-sub-categories-that-are-also-in-the-sub-categrories/80901/16)

I think this is quite a great solution for your problem here @Drew_Warwick , it very much simplifies stuff for end users.

---

<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: [16 Abril , 2018 01:47 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 …

[Previous page](https://meta.discourse.org/t/users-mistake-top-level-categories-for-lack-of-permissions/72227.md?page=1)
