Forum Discussion
MCFNeil
8 years agoQrew Captain
At least at the high level you will have 2 tables.
HQ & Stores.
One way to handle access at the store level is to have a field on the stores table called "Users with access".
This is a multi-select User field. So as long as you don't have more than 20 'store users' per store. Then you can use this field to indicate which users can view that store (and possibly all the child records).
You will then have your 3 roles; HQ User, Store Management, Store Employee.
Then you can apply the 'viewing' rights to the store users where they are listed in the 'users with access' field.
If you are going to have more than 20 users per store, there are a few other ways to do this, but much more tricky to set up.
HQ & Stores.
One way to handle access at the store level is to have a field on the stores table called "Users with access".
This is a multi-select User field. So as long as you don't have more than 20 'store users' per store. Then you can use this field to indicate which users can view that store (and possibly all the child records).
You will then have your 3 roles; HQ User, Store Management, Store Employee.
Then you can apply the 'viewing' rights to the store users where they are listed in the 'users with access' field.
If you are going to have more than 20 users per store, there are a few other ways to do this, but much more tricky to set up.
- ltduranltduran8 years agoQrew CadetThanks for your reply! This sounds like a great solution. Is there a way to do a multi select user field? I can't seem to find it. Thanks!
- ltduranltduran8 years agoQrew CadetNevermind, I figured this out! This is a great solution, thanks!
- ltduranltduran8 years agoQrew CadetIs there a way to have this affect child records?
- MCFNeil8 years agoQrew CaptainPass that "Users with Access" field as a lookup field to all the child records.
Then adjust the roles/permissions to use that field for access. Viewing and/or modifying. - ltduranltduran8 years agoQrew CadetGreat, thank you!