I understand your solution, thank you.
I am still very confused, because on my other Glide app, this works
(when admin adds another user, and dedicates a role)
Yes, this is the difference between two apps.
In my other app (where adding roles to new users does work), the “Role” is unmarked (as in picture above). I understand this could be very dangerous, because of lack of control.
Thank you very much for your time and your solution
@Jeff_Hager would you say that the role functionality is only really needed when using row owners?
I’m working on something where each user type only dictates the actions and components they should have access to. There’s no need to limit rows that are accessible for a staff member compared to a manager - it’s more that only the manager can delete items or something like that. All staff should be able to see entries for all staff.
Turning off the role setting in your screenshot would allow the manager to create new staff and assign them any user type (not just their own as is currently possible with the role set).
Sounds like this is the easiest solution for my case, rather than using Make or the API, right?
Yes, primarily Role functionality is designed to be used with row owners to secure data and make that data accessible to a group of users instead of a single user.
If your only goal is to use a psuedo role for visibility/filters, or control which action a user can call, then you are correct, you are not required to use the true role functionality in Glide.
Let’s say you do not establish Role functionality through the user profile configuration, and then have a column in any table with the word ‘Admin’ and set that column as a row owner column. Who owns it??? Who is the Admin???
If you don’t set that up in the configuration, how is the app supposed to know who is an Admin and who is not, to then determine if a person should have access to that row of data?
Setting a Role column is like setting an Email column. It tells the app which columns contain the vital pieces of information, to get the signed in user’s info, to use for controlling row ownership.
