# Tab visibility conditions are not effective - breach of sensitive data and/or creates bad UX **URL:** \ **Category:** Report a Bug\ **Created:** [September 8, 2020, 6:04pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466 "2020-09-08T18:04:35Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\ **Post date:** [September 8, 2020, 6:04pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466/1 "2020-09-08T18:04:36Z")
Onboarding screen is flashing for a few looong seconds upon every login. Any ideas how to reduce/fix this? @Mark Tab visibility should not flash hidden tabs like this because it breaches confidential sensitive data in the case of my other app, and here it’s just creating confusion/bad ux. Can you guys fix this? My app is public with email - I am trying to hide the onboarding screen when sign up process is completed. ---
**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\ **Post date:** [September 8, 2020, 6:36pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466/2 "2020-09-08T18:36:27Z")
I believe @Mark fixed this a few weeks ago, but it seems to be back! I haven’t been experiencing it since the fix rolled out a while ago, but based on your video, it seems like there’s still something going on with some apps. > [@Wrong tab loading on Sign-in](https://community.glideapps.com/t/wrong-tab-loading-on-sign-in/13047/21): > > This will be fixed later this week. Sorry for the delay. ---
**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\ **Post date:** [September 8, 2020, 8:07pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466/3 "2020-09-08T20:07:12Z")
@Mark I was able to fix this by putting in a long list of conditions instead of using the profile done column in the GDE (Check if profile is done). Instead of 1 condition, I had to set 5 - but the problem went away. That’s a clue to help you guys, perhaps, fix the lag of checking the number column in the data editor. Of course we would all prefer to set fewer conditions than more, if possible. Thanks! ---
**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\ **Post date:** [September 8, 2020, 8:21pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466/4 "2020-09-08T20:21:54Z")
FYI, we just had an all-company meeting about a better group-level permissions system, that is easier to get right and gives you more confidence than using filters. We have some exciting ideas! ---
**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\ **Post date:** [September 8, 2020, 8:23pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466/5 "2020-09-08T20:23:47Z")
That’s amazing to hear! I will be sleeping better at night when we have ability to secure data for groups/companies! 😅 🤩 😍 😊 😁 ---
**Author:** ![Mark](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark/32/125_2.png) [@Mark](https://community.glideapps.com/u/Mark)\ **Post date:** [September 8, 2020, 8:27pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466/6 "2020-09-08T20:27:01Z")
@Deena do you still have a reproducible test case for this? When is the “profile is done” column set? ---
**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\ **Post date:** [September 8, 2020, 8:40pm UTC](https://community.glideapps.com/t/tab-visibility-conditions-are-not-effective-breach-of-sensitive-data-and-or-creates-bad-ux/15466/7 "2020-09-08T20:40:57Z")
I have changed the conditions so I cannot reproduce it without changing them back…but I will do it if it will help. In the meantime, to answer your question, the condition was set here: ![Screen Shot 2020-09-08 at 4.38.56 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/c/c2115653d582ae95c9b0bb9ab78b8f51e0bce05c.png) I tried using a couple of different conditions, (one at a time) such as Show tab when Profile Done Value is empty, and used the column ProfileDone (before the number column in the screenshot), Show tab when ProfileDone is False or is empty. Both conditions worked, but both create the flashing sign up screen issue. When I changed the conditions to Show tab when username is not empty AND gender is not empty AND Country is not empty AND date of birth is not empty, then the issue was resolved.