User specific list appears to other strangely


I am quite new to glide, and I am creating my first app. I created a table of “child” that are created by their parents. So each user profile, ie parents, must create and see their own child.

But when I switch from one user profile to another one, they can acess to others child (they do not see the avatar of the child, just a grey box, but they can click on it) :

Is it a bug ? or something I missed ?

Many thanks !


User specific columns don’t make rows disappear. They just hold a value that is specific to the signed in user. It allows multiple people to have different values in the same cell in the same row.

What is sounds like you need is a filter or row owners.

Filters are not very secure, but they will hide data in a list/collection.

The better and more secure way is to use Row Owners.


Thanks Jeff for your quick reply !

I have 2 comments:

I have created a very basic app to understand how the “user specific” would work, ie an app with 1 table of child profile, and 2 buttons to create the child, and the other to open a screen with an inline list showing the child profiles.

And it does what I want : the list show only rows that are created by the login users :

So I don’t know if I am missing something or I can try to recreate that behavior for my app.

Second is the row owners solution, I understood it would mean that I should assign to each user a specific right to see their owns that they create ? While I would like not to do anything :slight_smile: ie login user create their own rows and see only them ?

Many thanks,

ps : i am french so excusez moi for the english mistakes

It doesn’t really.
All rows will be available to all users, it’s just that some rows will appear empty to some users.

This is not the correct way to use User Specific Columns, and it is not what they are intended for.

As Jeff mentioned, there are two options to achieve what you want. Either use filters, or use Row Owners. Row Owners should be used if there is private/sensitive data involved that needs to be kept secure. Otherwise, filters are fine.

In either case, you need a column in your table that will store the email of the user that created the record. This should be populated when the record is created by including the “Users Email” special value as a form field.

You can then use that value to filter the list of records. Or, you can apply Row Owners to that column and filtering won’t be necessary.


Bonjour Bruno,

N’hésitez pas à vous exprimer en français si c’est pour simple pour vous. Jeff et Darren utilisent Google Translate ou deepL, ils comprendront la langue de Molière parfaitement.

Pour ajouter mon petit grain de sel :

  • User-specific columns (USC): Comme l’a indiqué Darren, vous n’avez pas à utiliser USC ici, le cas d’usage est tout autre. Utilisez ce type de colonne pour personnaliser un composant, typiquement sur une Details Screen, c’est-à-dire quand vous êtes déjà sur l’écran d’un élément d’une liste. Imaginons par exemple que tous les parents voient une liste de tous les enseignants. Un parent pourrait cliquer sur un enseignant, cela nous amènerait à la Details Screen de l’enseignant, et là imaginons que chaque parent pourrait laisser une note personnelle concernant l’enseignant. Chaque parent pourrait laisser sa note, mais si l’on veut que chaque note demeure personnalisée pour chaque parent (les autres parents ne voient pas les notes des autres), alors on utiliserait une USC. Les USC sont utilisées pour la personnalisation d’un élément et s’applique à une colonne (un attribut) dans une table. Contrairement aux Row Owner et Filter qui s’appliquent aux lignes …

  • Row owners : c’est un filtre qu’on pourrait appeler de sécurité qui agit au niveau l’app, c’est quasi un filtre universel. Row owners

  • Filter : c’est un filtre au niveau de chaque collection/liste (dans les options). Si vous avez besoin un moment qu’un parent2 voient des enfants qui ne sont pas les siens, alors cette approche serait la bonne. Filter

Comme l’a indiqué Darren, dans les deux cas Row Owner et Filter, notez qu’on aura besoin de l’adresse email des parents dans la table des enfants.

  • Relation : si vous vous retrouvez sur une Details Screen d’un parent, par exemple sur sa page de profil, et là vous voulez voir la liste de ses enfants, alors dans le Data Editor dans la table Parents vous pourrez créer une Relation (multiple) qui pointe de chaque parent vers ses enfants. La clé de la relation serait l’email. Si ce n’est pas clair, tout ceci sera expliqué sur la page Relations.

Data Editor

Layout Editor

  • Hiérarchisation de listes : vous avez créé deux tables, à savoir une table Parents et une table Enfants. Notez que que si les attributs (colonnes) des parents et enfants sont les mêmes, alors on est en mesure de se demander pourquoi on utiliserait pas une seule table qu’on pourrait appeler Personnes. Il s’agirait alors d’avoir une colonne Parent pour hiérarchiser les éléments de cette table et indiquer l’appartenance Parent-Enfants. Je vous laisse découvrir cette approche de hiérarchisation : subcategories & hierarchies

Well, many thanks for these replies nathanaelb, Jeff_Hager and Darren_Murphy ! :+1:

It’s really helpfull and I really appreciate the level of details into your answers :smile:

I am starting to understand what are really row owner and user specific column.

For my app, I want that the parent ie login user can create several child profiles (child table), and also some tasks for them ( tasks table) : so they will create several numbers or row as they continue to use the app. But I do not want that each time they have to write their own email that would be store into the table, that would quite a very bad user experience.

So I have created an email entry that is filled with default value with the user profile email, and I created a stupid condition that is never true so they do not see that email entry : (no condition set up in the picture below obviously).

It seems to work in my test behavior app… is it ok or a totally wrong and ugly way to do that ? :cold_face:

many thanks


1 Like

Darren shared documentation on this. Your users do not need to enter an email manually, and you do not need to create a hidden entry component with a default value. There is a User Email Special Value component that will do this automatically. There is also a User Profile email component that does the same thing. Either should work and neither need to be hidden as they are already hidden components. You add them just like any other component to the screen.


Many thanks to all,

As we say in french " je comprends vite mais il faut m’expliquer longtemps " :smile:, but I managed to make it work thanks to you !

merci beaucoup,