The Complete Guide to Shared Household Media Governance
Create household media governance for account roles, profiles, source responsibility, trusted devices, privacy, changes, troubleshooting, onboarding, and offboarding.
In short: Good household media governance assigns clear responsibility for the account, authorised sources, profiles, and devices; sets privacy and credential boundaries; records major changes; and defines onboarding, offboarding, and incident routines. Keep the agreement short, never store secrets in it, and treat household roles as organisational responsibilities rather than unverified product permissions.
Governance sounds formal, but its purpose is practical: everyone should know who may change what, how to avoid disrupting another person's viewing state, and what to do when a device or source changes.
Separate five governance layers
- Account: subscription, authentication, privacy, and official support contact.
- Source: compatible media access the user owns or is authorised to use.
- Profile: progress, history, favourites, and preferences for a viewing context.
- Device: supported screens, sign-in state, local media, and physical custody.
- Session: current item, version, position, audio, and subtitles.
A change at one layer should not be disguised as another. Removing a profile does not necessarily sign out devices; changing a device does not change source rights.
Assign household roles
Useful roles include:
- account coordinator: keeps official account and plan information current;
- source steward: confirms source authorisation and handles connection changes;
- device custodian: knows which devices retain sign-in;
- profile owner: decides their favourites and preferences;
- incident reporter: collects privacy-safe evidence for support.
These are household roles. They do not establish Norva administrator permissions or require password sharing.
Use the account-management decision guide to select a coordinator.
Write one page of rules
The agreement should cover:
- who approves plan and account changes;
- who may connect or remove a source;
- how profile ownership works;
- which devices are trusted;
- the pre-play profile check;
- how guests are handled;
- what changes require a log;
- what happens when someone moves in or out;
- how incidents reach support.
The one-page household agreement supplies a concise template.
Protect credentials and private history
Never place passwords, recovery codes, source credentials, payment data, or private URLs in the agreement or device inventory. Share the outcome of account management, not the secret itself.
Profiles organise viewing context; they are not passwords. Review Norva's privacy policy and terms for current product conditions.
Approve changes proportionately
Small personal actions, such as adding a favourite to one's own profile, usually need no household vote. Shared changes, such as removing a source or renaming a shared category, affect more people and deserve notice or approval.
Use three levels:
- personal and reversible;
- shared but reversible;
- shared and potentially disruptive.
Record only the latter two when the information will help recovery.
Maintain a trusted-device inventory
A trusted device is a household judgement about custody and access. A supported device is a product-compatibility status. They are different.
The trusted-device inventory records owner, role, sign-in state, local media, and exit plan without secrets.
Use controlled troubleshooting
When a problem appears, preserve the first state and change one condition at a time. Do not let several people reset, reinstall, reconnect sources, and change profiles simultaneously.
Agree who coordinates the incident, what can be tried, and when support is contacted. Keep evidence minimal and redacted.
Plan lifecycle events
Onboarding explains account, profile, source, and device boundaries. Offboarding separates profile state, device access, local media, and credentials. Selling or returning a device adds manufacturer reset and custody steps.
Do not perform irreversible removal until ownership and consequences are understood.
Original evidence: governance charter
| Area | Responsible role | Decision right | Evidence kept | Review trigger |
|---|---|---|---|---|
| Account/plan | ||||
| Authorised sources | ||||
| Profiles | ||||
| Trusted devices | ||||
| Privacy | ||||
| Shared changes | ||||
| Troubleshooting | ||||
| On/offboarding |
Add the agreed escalation path and where the secret-free agreement is stored. This charter documents responsibility; it does not grant technical access.
Review after meaningful changes
Use triggers such as a new household member, device sale, source change, unknown device, plan change, repeated profile mix-up, or privacy concern. Avoid calendar theatre when nothing changed.
Common mistakes and limitations
Avoid sharing credentials to “make everyone an admin,” logging every personal action, treating profiles as security, and making changes without an owner or rollback plan.
This governance framework is not legal advice, a security guarantee, or a substitute for current Norva documentation and support.
Frequently asked questions
Does every household need formal roles?
Names can be informal, but responsibility should be clear for account, source, device, and incident decisions.
Should one person control everything?
Not necessarily. Centralising coordination can help, while profile owners should retain say over their own viewing context.
Where should the agreement be stored?
In an accessible household location that contains no secrets or unnecessary private history.
How often should governance be reviewed?
After material changes or repeated problems, not solely because a fixed date arrives.