This message was deleted.

Thanks for the response @clever-art-10420. Unfortunately, I don't think that the separate app route will work for me, practically speaking, as it would mean setting up and maintaining way too many separate apps. Alternatively, I could set up hundreds of different roles, but that would leave me with the same problem. I think the best I may be able to do is to make the roles apply to the navigation items only, so that each user is able to access the navigation with their broadest applicable role, and then use record based permissions to show and hide fields.

@stale-judge-11647 yeah I hear that on the too many apps or roles. There are several things in Stacker that you wish were just a bit more programable. This is one of them. Using roles with navigation and creating different protected routes is my chosen first approach. This works fine with List views, but you can only have 1 Detail/Update & Create view per domain (unless Stacker changed this 🤞), when this happens you’ll need to use it on field groups and text sections. One last idea - what if you just relate a user profile to corporation and then restrict the data they can access based on that relationship. Then use roles to differentiate between Director and Shareholder. So it will only 2 roles and won’t make the rendering rules crazy. AND you have probably already defined the relationship between these user profile to the company. edit: this is a much better idea then the other two, if it were me I’d do it something like this.

Thanks for the feedback and suggestions. I appreciate you taking the time.