Privacy Philosophy
Household data is sensitive. Clarity and discretion both matter. The right access helps people work without exposing unrelated context.
Role Overview
| Role | Best For | Notes |
|---|---|---|
| Admin | Trusted setup owners. | Every area, plus people and settings. Use sparingly. |
| Member | Family and household team. | An admin chooses which areas each member can use, and whether they can make changes or only view. |
| Driver | Drivers. | Transport only, view only. |
Feature And Record Visibility
Feature controls decide whether a module is available. Roles and permission flags decide whether a user can see or manage it.
- Check feature control.
- Check role.
- Check permission flags.
- Check house context.
- Check the mobile More menu.
Notes Privacy
Notes can be private or shared through categories. Keep sensitive information in private notes or tightly shared categories, and review sharing after staffing changes.
Calendar Privacy
Personal imported calendar events are not the same as shared records. Use shared Omnisant events when others need ownership, notes, status, or shared visibility.
Audit History
Audit history supports accountability and troubleshooting. Use it to understand what changed, not as surveillance theater.
Access Review Checklist
- Remove inactive users.
- Review admin users.
- Check household support permissions.
- Review shared note categories.
- Confirm calendar connections.
- Verify feature controls.