# Visually Disable Features that aren't Available at a Given Trust Level

**URL:** <https://meta.discourse.org/t/visually-disable-features-that-arent-available-at-a-given-trust-level/66529>\
**Category:** Product Support\
**Created:** [20 Julio, 2017 16:13 UTC](https://meta.discourse.org/t/visually-disable-features-that-arent-available-at-a-given-trust-level/66529 "2017-07-20T16:13:30Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![RyanK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ryank/32/297314_2.png) [@RyanK](https://meta.discourse.org/u/RyanK)\
**Post date:** [20 Julio, 2017 16:13 UTC](https://meta.discourse.org/t/visually-disable-features-that-arent-available-at-a-given-trust-level/66529/1 "2017-07-20T16:13:30Z")

</div>

We have pretty low thresholds for moving to Trust Level 1, but we are still getting frustrated feedback from users who are not yet able to create a topic but don’t realize until after they compose their post.

Is it possible to provide clearer indication to users who do not have appropriate permissions prior to starting a task? For example, if a user is not able to create a topic, the create topic button would be disabled and if they tried to access it they would get an optional trigger about trust levels and such.

---

_[View the full topic](https://meta.discourse.org/t/visually-disable-features-that-arent-available-at-a-given-trust-level/66529)._