whose money is it?
shared view. individual boundaries.
Most financial platforms are built around one simple assumption: one person logs in and sees their money.
That works nicely until a family starts using the same platform.
Now there might be several people, separate logins, joint accounts, individual portfolios and linked sub-portfolios. Technically, everyone is a separate user.
In practice, one person is often the one who logs in every time.
That person becomes the household’s unofficial financial administrator.
And that is where the UX gets interesting.
the household is bigger than the login
Imagine this structure:
Partner 1
ISA
Pension
Investment portfolio
Partner 2
ISA
Pension
Joint
Investment portfolio
The platform understands five or six separate financial relationships.
The person logging in is probably thinking:
“Show me our finances.”
That gap is important.
A household view needs to bring things together without pretending they are all the same thing.
what should i actually be able to see?
This is where linked accounts become much more than a navigation problem.
Should I be able to see every sub-portfolio?
Can one be hidden?
Can I see its valuation but not its transactions?
Should documents be shared across linked accounts?
What about secure communications?
And if I can see an account, does that automatically mean it belongs in my overall portfolio value?
These are not edge cases. They are fundamental questions about how the product represents a household.
aggregation is useful until it becomes confusing
A big consolidated number looks great:
Total portfolio: £4.8m
But what is actually inside it?
My investments?
My partner’s?
Joint assets?
Pensions?
Linked accounts I can view but do not own?
Suddenly the number needs context.
Compare:
Household total: £4.8m
with:
Andy: £1.7m
Partner: £1.4m
Joint: £1.7m
The second view gives you the convenience of consolidation without losing ownership.
That distinction matters because a single number can be technically accurate while still being conceptually wrong.
visibility needs boundaries
The same issue applies to the rest of the platform.
A consolidated transaction feed might be incredibly useful.
It might also be a privacy disaster.
A household communications area could be convenient.
It could also expose messages that were never intended for everyone.
Documents are even more obvious. Some may relate to the whole household, others to one person or one account.
So the interface needs to distinguish between:
mine
ours
theirs
and simply:
visible to me
Those are not the same thing.
the account structure should remain visible
There is a temptation to solve all this with one beautifully simple dashboard.
Put everything together and let people get on with it.
But the underlying structure still matters.
A useful hierarchy might be:
Household
→ Person
→ Account
→ Sub-portfolio
That gives people two useful abilities.
They can zoom out and understand the bigger picture.
They can also zoom in and understand exactly where a number, transaction or document comes from.
That is much safer than one giant bucket of financial information.
design for the person who actually uses it
There is one final wrinkle.
The person who logs in most often may not be the person who owns most of the assets.
They may simply be the organiser.
They check the numbers.
They download the documents.
They read the messages.
They keep an eye on everything.
Designing only around individual ownership misses that behaviour.
But giving that person unrestricted visibility is not necessarily the answer either.
The better question is:
What does this person need to manage the household confidently while still respecting individual boundaries?
That is where good household UX starts.
a useful checklist
When designing linked household accounts, ask:
Can users understand which people and accounts are linked?
Is ownership clear at every level?
Can individual sub-portfolios be separated or hidden?
Is it obvious what is included in consolidated values?
Can transactions, documents and communications have different visibility rules?
Can users move easily between the household view and individual account detail?
Does the experience reflect how households actually use the platform?
A financial platform may see a collection of separate accounts.
The family sees their finances.
Good UX has to support both views.
The trick is making them feel connected without making them feel indistinguishable.
