[Feature] Support for managing multiple profiles (Managing family records)

[balajiv113]

Problem

Currently we are managing health records of a single user which looks solid.
In this ticket am thinking of managing family health records usually this will be needed when we are managing family health records as well

Proposed solution

I could think of multiple options,

1. Introduce a concept of profiles where we can switch user altogether
2. Sharing / providing manage access from other profile

But there are other issues like how linked devices will sync across profiles and all. This is where this feature gets complicated

Alternatives considered

No response

Affected surface

Self-hosting / Docker

Additional context

No response

Pre-flight checks

• I confirmed this is not a duplicate of an existing feature request.
• I'm proposing a feature, not asking a usage question (those go to Discussions or the docs).

[MBombeck]

Thank you for this — I sat down with it properly, and it's a genuinely thoughtful request. Reading it closely, there are really two distinct asks bundled together, and I want to be honest about how I'm weighing each.

1. Account-to-account "manage access" (one person granted ongoing write access into someone else's existing account)

I'd like to set this one aside for now, and I want to explain why rather than just say no. The whole app is built on a strict one-account-one-owner model: every record and every query is scoped to a single authenticated user, and that invariant is a big part of what keeps health data safe from cross-account leakage. Introducing a second person who can write into another person's account means retrofitting that boundary across the entire codebase — not something I want to do quickly or half-way with data this sensitive.

For the read side of this — showing your data to a doctor or a family member — the existing share feature already covers a lot of ground today: it's passphrase-protected, time-limited, and revocable. I'd much rather extend that than open a second write path.

2. Family records / managing a profile for someone who isn't a separate user (e.g. a parent tracking a child)

This one I find genuinely interesting — and the nice part is it can be done without the security trade-offs above. The model would be a dependent profile: it lives under your own account, you fully own and manage it, and there's no second login involved. That keeps the security boundary and the data model intact while still solving the real need.

Where I'd love your help — I'm not yet sure this matches your situation, so could you tell me a bit more about the concrete use-case?

• Whose records would you be managing — a child / dependent, or another adult who has (or wants) their own account?
• Do those profiles need to pull in device data (Apple Health / a wearable), or is it mainly manual entry plus lab and medication tracking?
• Are you picturing switching profiles on desktop, on mobile, or both?

I ask about device data specifically because there's a sharp edge on mobile: a phone's sync is bound to exactly one profile, so switching profiles on the phone and then syncing Apple Health could quietly write data into the wrong profile. My current thinking is to keep profile management on desktop and keep each phone locked to a single profile — but your answer will tell me whether that actually fits how you'd use it.

Really appreciate you raising this. It's exactly the kind of thing I'd rather get right than get fast — and your concrete scenario is the missing piece that lets me scope it well. 🙏

[balajiv113]

Thanks a lot for detailed deep dive.

Whose records would you be managing — a child / dependent, or another adult who has (or wants) their own account?
It can be anyone. Child, parents. They may not be having their own account

Do those profiles need to pull in device data (Apple Health / a wearable), or is it mainly manual entry plus lab and medication tracking?
Yes, this would be helpful but can also be optional. Reason being if they don't have their own account may not be using much of smart devices. But again another side to it is they maybe using

Are you picturing switching profiles on desktop, on mobile, or both?
Both, atleast I use android for now so doing in web for first should be good I hope

I understand the security issue in account sharing. That's where even I was in a dialama on which is right fit.

[MBombeck]

Perfect — that clears it up, thank you. This lands us in a really clean place:

• Dependent profiles (people you manage who don't have their own account — a child, a parent) is exactly the model we'd build: each profile lives under your account, you own and manage it, no second login, security boundary untouched.
• Web-first is the right starting point, and it suits you well since you're on Android + web.
• Device sync stays optional / later. Keeping the first version to manual + lab + medication tracking (no Apple Health / wearable pull for dependent profiles) sidesteps the wrong-profile-attribution risk entirely, and we can layer device data in afterwards once the per-profile model has earned its keep.

So the shape we're leaning toward for a first cut: manage dependent profiles on the web, switch the active profile there, full manual / lab / medication tracking per profile — and adult-to-adult account sharing parked for the reasons we both landed on.

No commitment on timing yet, but this is now a well-scoped, safe piece of work rather than an open-ended one — which is a great place to be. I'll keep this issue updated as it moves. Thanks for thinking it through with me. 🙏