# Ability to group and tag/name components **URL:** \ **Category:** Feature Requests\ **Created:** [July 10, 2020, 9:47am UTC](https://community.glideapps.com/t/ability-to-group-and-tag-name-components/12252 "2020-07-10T09:47:57Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![zeki](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/zeki/32/9068_2.png) [@zeki](https://community.glideapps.com/u/zeki)\ **Post date:** [July 10, 2020, 9:47am UTC](https://community.glideapps.com/t/ability-to-group-and-tag-name-components/12252/1 "2020-07-10T09:47:57Z")
It would be great If we can have the ability of grouping or/and tagging/naming the components list in designer view on the right side. Or maybe a section like grouping layers in Photoshop Because sometimes your home tab (mostly) or any other tab is to much loaded with lost of components which has dependent visibilities. I have deleted the wrong components many times when I’m working on a project. Show All / Hide All switch would be good as well. Thanks ---
**Author:** ![Glider](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/glider/32/9699_2.png) [@Glider](https://community.glideapps.com/u/Glider)\ **Post date:** [July 10, 2020, 10:46am UTC](https://community.glideapps.com/t/ability-to-group-and-tag-name-components/12252/2 "2020-07-10T10:46:17Z")
that is a great idea for a show all hide all switch we can just set visibility settings to if the switch is true ---
**Author:** ![BlakeWS](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blakews/32/24377_2.png) [@BlakeWS](https://community.glideapps.com/u/BlakeWS)\ **Post date:** [April 16, 2021, 3:26am UTC](https://community.glideapps.com/t/ability-to-group-and-tag-name-components/12252/3 "2021-04-16T03:26:32Z")
Yes, I’m going through this right now, adding the same visibility conditions over and over. It definitely seems redundant and could be solved with some visual hierarchy and grouping. Once you have lots of screen items it becomes challenging to keep all the rules straight and consistent. ---
**Author:** ![Apto\_Cincodos](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/apto_cincodos/32/18458_2.png) [@Apto\_Cincodos](https://community.glideapps.com/u/Apto_Cincodos)\ **Post date:** [June 29, 2021, 7:28pm UTC](https://community.glideapps.com/t/ability-to-group-and-tag-name-components/12252/4 "2021-06-29T19:28:03Z")
This is something we should be talking about now (: Having dozens of components blocks in several languages with their visibility conditions to be easily moved and modified would be a game-changer. I would really love to see the same applied for the columns such as the grouping columns option in spreadsheets. My scrolling is getting me more exhausted every time 😅 ---
**Author:** ![BlakeWS](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blakews/32/24377_2.png) [@BlakeWS](https://community.glideapps.com/u/BlakeWS)\ **Post date:** [June 29, 2021, 8:16pm UTC](https://community.glideapps.com/t/ability-to-group-and-tag-name-components/12252/5 "2021-06-29T20:16:43Z")
> [@Apto\_Cincodos](#): > > Having dozens of components blocks in several languages with their visibility conditions to be easily moved and modified would be a game-changer. I believe this is solved a few ways by auto-populating the components with the language that the user selects up-front - rather than duplicating the components and using visibility/filters. > [@Apto\_Cincodos](#): > > I would really love to see the same applied for the columns such as the grouping columns option in spreadsheets. This is also solved by the new column naming convention, whereas you format it like - data/ userValue - and then search for the first part. Both of these are in recent discussion that you can find. ---
**Author:** ![Apto\_Cincodos](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/apto_cincodos/32/18458_2.png) [@Apto\_Cincodos](https://community.glideapps.com/u/Apto_Cincodos)\ **Post date:** [June 29, 2021, 10:04pm UTC](https://community.glideapps.com/t/ability-to-group-and-tag-name-components/12252/6 "2021-06-29T22:04:49Z")
> [@BlakeWS](#): > > I believe this is solved a few ways by auto-populating the components with the language that the user selects up-front - rather than duplicating the components and using visibility/filters. I didn’t knew that I needed this so bad > [@BlakeWS](#): > > This is also solved by the new column naming convention, whereas you format it like - data/ userValue - and then search for the first part. > > Both of these are in recent discussion that you can find. I think that I saw something similar, although I don’t know which topic is. However the request by having groups in the data editor. The main idea is to collapse these columns in both panels to avoid infinite scrolling (down and sides) Thanks in advance!