Members and Roles Documentation
Household invitations, admin/member/viewer roles, client permissions, least privilege, and offboarding.
Audience: Household administrators and members reviewing access. · 4-page PDF · v6.26.1
How to read this document
Sections move from purpose → concepts → calculation process → worked examples → edge cases. Formula boxes use plain mathematical notation for clarity; they are conceptual summaries, not API contracts.
- Point lists call out operator-visible behaviour.
- Callouts mark warnings, limitations, or important qualifications.
- Worked examples use round numbers so you can reproduce the arithmetic by hand.
Purpose
Membership controls who participates in a household and what each person can do.
- Invite known people
- Assign an appropriate role
- Constrain write and client access
- Review and revoke access
Role concepts
- Administrator — household-wide management.
- Member — operational access within permissions.
- Viewer — read-oriented access.
- Additional per-person permissions can further constrain actions.
Invitations
Verify the recipient and household before sending or accepting an invitation. Expired, mistaken, or unused invites should be withdrawn where supported.
Permissions and clients
Role is a baseline, not always the entire authorization decision. Feature, write, web, and mobile controls can combine.
Effective access concept
Identity + household membership + role + feature/client permission
Least privilege
Add a reviewer
- Invite the intended account.
- Choose viewer access.
- Disable unnecessary write or client access.
- Confirm visible modules.
The reviewer receives only the needed access.
Role changes and offboarding
- Review ownership before demoting an admin.
- Revoke departed members promptly.
- End relevant sessions.
- Review shared exports and downloads.
- Check independent Split groups separately.
Visibility caveats
Copies outlive access
Removing a member cannot retract screenshots, exports, or files they already received.
Privacy, advice limits, and what we do not publish
AccountHouse is a household tracking and organisation tool. It is not a bank, payment processor, tax advisor, or investment advisor. Forecasts, health scores, balances, and alerts are informational.
- Household data is scoped to your household; other families cannot see your ledger.
- Public documentation explains product behaviour and calculation concepts, not proprietary internals.
- Exact scoring weights, anomaly thresholds, cryptography parameters beyond high-level algorithms, and operational detection rules are reserved.
- Household membership does not necessarily grant unrestricted access to independent Split groups or every sensitive detail.
Intellectual property boundary
This document describes what AccountHouse calculates and which inputs matter. It does not disclose source algorithms, secret constants, or implementation details sufficient to reconstruct proprietary systems.