Hello community. Hope you are well today.
I have create an app with Users & Admins.
1 - Users can check by using collections component. The column is user specific of course, every user can follow is own checks.
2 - I’m creating a screen where admin can overview all users checks.
2.1 - First, I use a component to display all users (call teams)
Then, when you enter in one team, you have all details, included checks. But it’s not display the checks of the actual team, but the check of the viewer account (so the admin in fact). How can I arrive to provide the date of the user ?
Thanks a lot for your help on this little case. I have
1 Like
Hi @Maxime_Im_Nomade 
I’m afraid User-specific columns (USC) aren’t designed to let you do that.
Each user has their own isolated data in these columns, and there’s no way to access another user’s values.
My source is Glide’s docs here: User-specific columns | Glide Docs
However, you could consider storing the data in the Users table instead.
The data will be accessible by other users — Admins in your case.
Instead of targeting the User-Specific Column (USC), you’ll reference the column from the User Profile table.
This would allow you to use Row Ownership, so that only admins can access all user data — which is a good option from a security standpoint.
By the way, great screenshots! 
3 Likes
I hope you like the purple color hahahah.
Thanks for you answer, I was afraid of that.
It’s could be complicated for me to store thoses data in the users table, as I have the table :
etapes_onboarding_complet Related to sous-parties table
To create sub-categories
OR
Can I, make the user store the date in the table Users in the same time? Then I register the data in my table Etapes and in Users table in the same time, for the admin?
Based on your explanation and screenshots, it looks like you want your users to access a checklist of various technical check-ups, right?
Each check-up type is already defined in the etapes_onboarding_complet table, and the Partie & Sous-partie columns let you display a sublist depending on the check-up selected.
If that’s correct, you don’t need to change this part 
What you could evolve: in Data
Make sure to duplicate your app before proceeding — better safe than sorry!
You’ll need to adjust a few elements (see the details below), and while I’m quite confident in the approach, it’s always a good idea to test things in a copy first.
- Add a column in the
Users table called Etapes réalisées (Text) to store the Row IDs of steps that have been marked as completed by the team.
- Add a column
Etape actuelle (Text) to store the step the user is interacting with.
- Create two new computed columns:
Etapes réalisées moins étape actuelle (Replace All)Etapes réalisées plus étape actuelle (Template)
These will simulate a toggle mechanism, depending on whether the step is already marked as done or not. Later on, in the Workflow, you’ll Set column values depending on the step status:
- if the step is already completed,
Etape actuelle will become Etapes réalisées moins étape actuelle
- otherwise
Etapes réalisées plus étape actuelle will be the new value of Etape actuelle
This way, you’ll have a text list of completed steps for each user/team.
Now, in etapes_onboarding_complet, fetch related completed steps thanks to a Query column associated to an If → Then → Else one to check if the current step exists in the completed list.
You could use emoji such as 
to indicate the status instead of a text 
In Layout
- Replace the Checklist collection (which doesn’t support this kind of logic) with a List or another type.
- Create a Workflow on row click to Set column values — toggle the step between done and not done using the logic described above.
- Optionally: prevent unchecking once a step is completed (totally up to you).
Screen for admins
The big benefit of this structure is that Admins can access data for specific Teams.
Here’s how:
- When an Admin selects a team, store the selected Team ID in a column of the
Users table using a Set column values action.
- Then use a
Query in etapes_onboarding_complet to fetch and display the related steps for that team.
And that’s it — scalable, admin-friendly, and flexible! 
This is a very brief explanation. Let us know if there are any points that aren’t detailed enough
2 Likes
Hello Nicolas, I have tried to follow your explanations, but I’m not following the logic of it, and I think we have a little misscommunication on the tables etc…
So, I have record a loom vidéo, I guess that’s will be more precisly
Again, a hudge thanks.
I also answered in a video — in my terrible English 
