Row Owners would be the secure way to restrict which data a user has access to.
Only if you have a whitelist table restricting who can sign in, or assign Role functionality to a user.
Assigning Row Owners to a table does not make a user private on its own.
You can either build everything into a single app and assign multiple row owners to each table (maybe using Roles for BO employees), or you can have separate FO and BO apps with different row ownership. Maybe no row ownership for BO employees, but use row ownership for FO users.
@Jeff_Hager I managed to create 2 working samples using Row Owners.
What really bugs me is the use of E-Mail Addresses as Row Owners, if the User changes his E-Mail Address in his Profile all of his Records will become orphaned!
Yeah, that wonât work as you have it.
The only way you could get that to work would be if you defined the RowID column in your Users table as the Role column in your User Profiles configuration. But Iâm not even sure if Glide will allow that.
It does however sound like what you need is to be using Roles as Row Owners. Have a read of the below, it might help to clarify how this can be configured.