Planual Rules regarding Users and Roles
1.03-01 Only give write access to lists when needed
Unless the end users need to edit the members of the list (for example, add, delete), access doesn't need to be set. Adding roles to lists increases the memory usage, so only use when necessary. A user can edit data in a module without needing to have access to the list.
bestPracticesArticles
1.03-02 Performance and size can be dependent on the Users list
When Users list is heavily used, the number of users added can have a significant impact. Be mindful of this and remove model access from any Workspace users when not required.
1.03-03 Set a landing page by role
Different roles should require a different entry point. Avoid a generic landing page if possible and create a specific page tailored for each role.
