# New category permission - "cannot see"/"exclude"

**URL:** <https://meta.discourse.org/t/new-category-permission-cannot-see-exclude/50044>\
**Category:** Feature\
**Created:** [September 12, 2016, 10:46pm UTC](https://meta.discourse.org/t/new-category-permission-cannot-see-exclude/50044 "2016-09-12T22:46:14Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [May 28, 2022, 9:52pm UTC](https://meta.discourse.org/t/new-category-permission-cannot-see-exclude/50044/32 "2022-05-28T21:52:21Z")

</div>

> [@jimkleiber](#):
>
> Makes me wonder how conflicting permissions work right now: if a user belongs to group A and group B and group A can create topics in that category but group B cannot create topics, can the user create a topic in that category? In other words, which takes precedence?

Permissions are effectively cumulative, there’s no such thing as a conflict in that sense. The highest inherited permission always wins. I can be added to one group which lets me see a category, and also another which lets me contribute.

> [@jimkleiber](#):
>
> maybe it can be relatively simple: just allow us to add a group to the security settings of a category and let us uncheck the See box.

Why would you need to exclude a group unless you’ve also explicitly given access through another membership?

---

_[View the full topic](https://meta.discourse.org/t/new-category-permission-cannot-see-exclude/50044)._