# Tabs in Tabs **URL:** \ **Category:** Ask for Help\ **Created:** [February 20, 2020, 12:14pm UTC](https://community.glideapps.com/t/tabs-in-tabs/4795 "2020-02-20T12:14:48Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jules\_Renaud](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jules_renaud/32/91_2.png) [@Jules\_Renaud](https://community.glideapps.com/u/Jules_Renaud)\ **Post date:** [February 20, 2020, 12:14pm UTC](https://community.glideapps.com/t/tabs-in-tabs/4795/1 "2020-02-20T12:14:48Z")
Hello the community. I want to create a tabs where we can see two differents people : user and prospect ![Capture d’écran 2020-02-20 à 13.00.12](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/6/6b87782225dd78b2c6a1193e6500cb240c4fcd1c.png) I find something like this with favorite, but I don’t find if is possible to do this for what I try to do. I want on one side actual user, and the other side the prospect. I try to just put favorite for prospect but I have 2 issues : - because is favorite, the prospect is on the 2 sides - I don’t have an excel column for favorite to tell who is favorite or not Thanks for all ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [February 20, 2020, 1:59pm UTC](https://community.glideapps.com/t/tabs-in-tabs/4795/2 "2020-02-20T13:59:01Z")
This would be a feature request. I’ve wanted something similar as well for my to-do app. New and Completed, for example. The best I’ve been able to do is use the detail screen with the same inline list twice but with different filters…but they’re stacked on top of one another. ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [February 20, 2020, 5:08pm UTC](https://community.glideapps.com/t/tabs-in-tabs/4795/3 "2020-02-20T17:08:17Z")
i would create a sheet by getting unique emails from the app:logins sheet. This will allow for per user records that you can display in details style view and filtered by signed in user. On this new sheet, add a column that will contain the value of the view you want each user to have (User/Prospect). Next create a sheet that contains a header and the values ‘User’ and ‘Prospect’. This will be used for a choice component. Now create 2 inline lists. One to display User’s and one to display Prospects. Use any filters you need to get each list to display the proper data. Create a choice component with the horizontal segmented layout at the top of the screen. Fill it with the the sheet that contains the User/Prospect values. Selecting User or Prospect will set the value in the New user specific sheet. This value will be used to set visibility to determine which inline list you want to view on the screen. If you want, you can set this up with relations and use one list, but that all depends on how you have things set up. Look at the Dynamic List Filter in [https://concepts.glideapp.io/](https://concepts.glideapp.io/). It’s a very similar concept that actually combines visibility with relations. This is recent post that is very similar: > [@Donation button](https://community.glideapps.com/t/donation-button/4709/2): > > I think it’s possible. The simplest way would be to create a number entry component on a donate page. Let the user type in a number, then pass that column value into the buy button. To make this better and prevent multiple users from updating the same column value at a time, create user specific donation pages using per user data and filtering. This will allow each individual user to set their own donate value. This will require a Public with Email or Whitelist privacy setting. The third op… I really want to stop suggesting this method, because I believe a new function to help this will be released soon. The new function is a User Specific Data column that will allow for per user values saved in a single column. This would allow for a single row instead of a row for each user.