# Label Components by Filter/Visibility

**URL:** <https://community.glideapps.com/t/label-components-by-filter-visibility/11332>\
**Category:** Feature Requests\
**Created:** [June 23, 2020, 6:31pm UTC](https://community.glideapps.com/t/label-components-by-filter-visibility/11332 "2020-06-23T18:31:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathon\_Kohn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jonathon_kohn/32/8593_2.png) [@Jonathon\_Kohn](https://community.glideapps.com/u/Jonathon_Kohn)\
**Post date:** [June 23, 2020, 6:31pm UTC](https://community.glideapps.com/t/label-components-by-filter-visibility/11332/1 "2020-06-23T18:31:05Z")

</div>

Hey everyone! I’ve been using charts a LOT lately and have run into an issue that when generating reports with a number of different filters I am left with a LOT of charts and no easy way to tell the difference between them unless I work on them in a specific order. Lord help me if i leave an app for a few weeks and come back to it. I propose a way to label our components that would make it easier to see what they are filtering or when they are visible at a glance…

 ![Screen Shot 2020-06-23 at 1.26.55 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/d/d33f8a6b0a596b1ce44adc1caffc322cee07f1f4.png)

---

<div class="post-metadata">

**Author:** ![Cmstewart42](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/cmstewart42/32/7319_2.png) [@Cmstewart42](https://community.glideapps.com/u/Cmstewart42)\
**Post date:** [June 25, 2020, 7:10am UTC](https://community.glideapps.com/t/label-components-by-filter-visibility/11332/2 "2020-06-25T07:10:38Z")

</div>

Hi @Jonathon_Kohn,

As a stop gap, although somewhat inefficient, you could add a text field above each graph and then change the visibility to some always false condition. Then fill the text to give a “title” to the graph immediately below it. It would allow visibility in the editor only in the component list, but would not show up in “runtime”.

Until a time that such a feature exists, I have used this myself to help organize components that don’t have any of their content visible on the page level.