How to limit access to data?

Ask for Help
1

Hello!

I would like to make a restaurant listing app. I am interested in how to make a database so that each restaurant can edit its own data and does not have access to the data of other restaurants.

Thank you!

2

row owner, role, or filters

3

How do I determine who is the row owner?

4

by user email address

1 Like
5

OK, thanks! I will try, should the database be made in glide or in google sheets?

6

always go with google sheets… the most reliable service in the World… plus you can do real magic with sheets formulas and scripts.

7

Can you please describe to me how to make each restaurant see only its data? Then the restaurant enters the data in the app or in a Google Sheet?

8

assign the owner’s email to each restaurant… but there is a bad side to this method… that’s why I’m not a big fan of the row owner function… it blocks the whole row. So you gonna have to recreate accessible info in some other sheet.

9

Which method do you recommend? And how do I do that?

10

hmm… I have a very unique and complicated method… LOL

11

It looks complicated :slight_smile:

1 Like
12

don’t worry… in a few minutes… (or more) some of the big writers, will write a whole manual on how to make your question work using just Glide… i’m out for today :wink:

13

Thanks!

14

If you need this to be secure, then you would need to make use of the roles feature.
Essentially you would define a role for each restaurant, assign the appropriate role to each user from each restaurant, and then use those roles as row owners.

For example, imagine that you have Restaurant A and Restaurant B. You might define something like role resta for Restaurant A and restb for Restaurant B. All users that belong to Restaurant A would be given the resta role, and all users from Restaurant B would get restb.

Then in the table/s that contain the Restaurant data, you would have a row owner column. Data that belongs to Restaurant A would have resta in the row owner column, and data that belongs to Restaurant B would have restb.

Using this approach, the data for each restaurant would be siloed, and it would not be possible for users from one restaurant to access data from any other restaurant.

It should be noted however, that every user that is assigned a role would be counted as a private user, even if your App allows anyone to sign in.

2 Likes
15

Thank’s!