Forum Discussion
Unfortunately, I think that you're stuck with those options. For option 3, I would say that you can limit the risk of exposing other customer's data by limiting the reports and forms that the Customer Role has access to.
I have a many-to-many table set up that drives my user permissions. If I were to make either parent restricted, then the permissions break. So, I just hide the reports and forms from the users for those tables.
Good luck!
John
------------------------------
John Crosland
------------------------------
- MattStephens2 years agoQrew CadetThanks John, I think I will go with your suggestion of limiting report and form views. Especially since the I expect the app to grow on complexity, requiring more and more automatons to keep the withdrawn order up to date. Your suggestion has saved me a few hours today, and possibly days of work in the future.
Matt
Sensitivity: General
- AdamKrzyzanek2 years agoQrew Captain
You wrote: I don't want customers to ever be able to see other customers' orders
In role you can restrict it in a way to show to you customers only data associated with them. It means you need to create separate roles for them, or manage roles via "access table" but it is doable.
I am doing it in my app, used by over 1000 people, and many external partners. Unfortunately because of this I am having 166 separate roles (some with similar settings but "filtered" to show specific customer number).
Also you can hide table from viewing. So user can have access to table but cannot see it (User Interface --> Hide in Table Bar)&
------------------------------
Adam Krzyzanek
------------------------------