Role-based views
Learn how role-based views work: set user roles and permissions so each family member or helper sees only the appointments, questions and handovers meant for them.
Contents
- How a role-based view works
- Enabling a role-based system view
- Roles, permissions and customization
- Questions about role-based views
- Can I enable role-based views in my family organizer?
- What is the difference between a role and roles in a view?
- Do role-based views hide appointments from other family members?
- How does view customization work with user roles?
Role-based views are screens and lists that change according to the user role a person holds in a shared organizer. Each role carries its own permissions, so a view built for one role shows the appointments, questions and handovers that role needs and hides the rest. The pages below explain how to enable a role-based system view, how roles differ from single permissions, and how view customization keeps a family handover clear for everyone.
How a role-based view works
A role-based view ties what a person sees to the user role assigned to them rather than to the device or the day. The role bundles a set of permissions, and the view reads those permissions to decide which records appear on screen. Two people opening the same shared family organizer can therefore see different lists at the same time. Changing a person's role changes their view the next time it loads.
Enabling a role-based system view
Enabling a role-based system view starts with defining each role and the permissions it should carry. Create the roles you need, attach the access rules to each one, and then switch the view setting from a single shared layout to the role-based option. Assign every family member or helper to the role that matches their part in the routine. Test each role by opening the organizer as that person before you rely on the setup.
Roles, permissions and customization
A role is a named container, while permissions are the individual rights inside it, such as reading an appointment or editing a handover note. View customization decides which of those permitted items appear together on a screen and in what order. Keeping roles few and permissions explicit makes role-based access easier to audit when the family routine changes. Review the setup whenever someone joins or leaves the shared organizer.
Questions about role-based views
Can I enable role-based views in my family organizer?
Yes, you enable role-based views through the view settings of a shared family organizer that supports role-based access. You first create the user roles, attach permissions to each, and then select the role-based option instead of one shared layout. If the setting is missing, the organizer does not offer role-based views.
What is the difference between a role and roles in a view?
A role is one named set of permissions, while roles in a view are the full list of those sets available to assign. Each person holds one role or several, and the view combines what those roles permit. Keeping the list short makes it easier to see who can read or change each part of the organizer.
Do role-based views hide appointments from other family members?
Role-based views show each person only the appointments and handovers their permissions allow, so other items stay hidden from them. The data is still held in the shared family organizer and remains visible to roles that carry the right access. Check the permissions of each role before you assume an item is private.
How does view customization work with user roles?
View customization arranges the items a role may see into a screen that fits that person's tasks. It cannot grant access on its own, because the role and its permissions set the limits first. Design each view around the handover and appointment details that role actually needs.