Norva

How Many Household Profiles Do You Actually Need?

Estimate household profile needs from independent progress, favourites, preferences, recurring groups, guests, shared screens, and current plan capacity.

In short: Count persistent viewing contexts, not people or devices. Create a profile when someone or a recurring group needs independent progress, history, favourites, or preferences. Merge contexts that genuinely watch together, and handle rare guests with an agreed temporary routine rather than automatic profile growth. Compare the result with current plan capacity on the pricing page.

A household of several people may need fewer profiles when most viewing is joint. Two people can need separate profiles when they follow the same series independently. The useful unit is persistent state ownership.

Start with recurring viewing contexts

List each pattern that happens often enough to preserve:

Do not create a profile per device. Norva can preserve account state across supported devices.

Mark states that must stay independent

For each context, ask whether it needs separate:

If none of these needs separation, the context may be merged with an existing shared profile.

The separate-versus-shared framework helps resolve mixed answers.

Exclude temporary demand

A one-time visitor, borrowed device, or single film night does not automatically justify a permanent profile. Consider whether the guest can use an agreed shared context without exposing private data or changing important state.

Do not claim a dedicated guest profile unless the product currently verifies one.

Merge genuine shared contexts

Two people who always watch together and accept one history may need one profile. Do not merge solely to fit capacity if it creates repeated progress mistakes.

Write the ownership rule: “This profile belongs to these viewers for these occasions.” A profile without a clear owner or purpose becomes clutter.

Compare with current plan capacity

Review the official pricing page for current profile allowances and conditions. Do not embed a profile count into an evergreen decision unless it is rechecked at publication.

Profile capacity is not a device count or simultaneous-playback permission.

Prioritise if demand exceeds capacity

Rank contexts:

  1. independent overlapping series progress;
  2. distinct personal history and favourites;
  3. persistent language or subtitle needs;
  4. recurring shared groups;
  5. occasional guests or one-time use.

This is a decision order, not a universal value ranking. The household can change it based on actual consequences.

Original evidence: minimum viable worksheet

ContextRecurs?Separate progress?Separate favourites?Separate preferences?Keep as profile?

Then record:

The worksheet produces a transparent estimate rather than a number invented from household size.

Test the structure for one real cycle

Use the proposed profiles during ordinary viewing. Record any wrong-profile starts, duplicate favourites, or unclear names. Do not call this a measured improvement unless a before-and-after method was defined.

When adding a new context, follow the clutter-free profile introduction. The complete household profile guide adds naming, privacy, and shared-screen rules.

Common mistakes and limitations

Avoid one profile per device, permanent profiles for every guest, duplicate contexts with similar names, and using plan capacity as proof of concurrent sessions.

Household patterns change. This worksheet estimates current organisational need and cannot determine account security, parental controls, media rights, or future plan terms.

Schedule a reduction check

After one viewing cycle, identify profiles that were never selected or represent the same recurring context. Merge only with the affected people's agreement and after documenting which progress, favourites, language, and privacy expectations could change.

Frequently asked questions

Should profile count equal the number of people?

No. Count independent persistent viewing contexts. A recurring group may share one; one person usually uses one across supported devices.

Do guests need permanent profiles?

Not necessarily. Consider frequency, privacy, state impact, and current capacity before creating one.

What if the minimum exceeds current capacity?

Review which contexts are genuinely independent, then compare current plan options. Do not merge important state silently.

Your next step

Review current Norva plan details

Sources