← Back to blog

Why (Not) Build Yet Another Finance App — Part 5: Family and Shared Accounts

Part 5 of 8Series: Why (Not) Build Yet Another Finance App
A thoughtful purple bird, hand on its chin, next to a stack of books, a laptop and large question marks
Family, or "just share it".

Sharing finances with someone looks like a permissions problem. You invite the person, they join, and both of you see the same thing.

In our heads, it was an invite button.

218
shared spaces created in Snabber
14
of them have more than one person
69
commits with "workspace" in the message

This is Part 5 of the diary we started in Part 0. Part 4 ended with a couple who want to know who spent what on the same card. Now the question gets bigger: what happens when two people use the same app for the same money?

Quick context: in Snabber, each person has a personal space and can create others, either shared (household, family) or business. Each space has its own accounts, categories and members. A member can be an admin, a regular member or read-only.

What we thought it was

The original plan
  1. A members table
  2. An email invite
  3. Everyone in the space sees its transactions

What it really was

The account belonged to whoever created it, not to the household

On October 9, someone tried to comment on a transaction in their family's shared space. The response was: "This account does not exist in this workspace."

The account existed. It was right there on the screen. It had just been created by another member. And in the code, an account belonged to whoever created it. Every path a transaction can take into the app (the form, spreadsheet import, Telegram, the AI, integrations) looked for the account "of the person making the change". When it did not find one, it created another with the same name. The household ended up with two "Nubank" accounts, one per person.

Along the way, we found a detail that made the error show up even for the owner: the space ID came back from the database as text and was compared to a number. The comparison never matched, so the app thought every edit was trying to move the transaction to a different space.

Before
The account belongs to its creator
another member adds a transaction, the app cannot find it and creates a copy
Now
The account belongs to the space
the creator only breaks ties when two people have accounts with the same name

The new rule fits in one sentence: a transaction belongs to an account, and an account belongs to a space. Applying that sentence took nine releases in a row, because it touches everything that renames, moves or deletes an account. And each of those paths has to be careful not to hit a same-named account that belongs only to someone else.

The read-only member who could delete

While testing the new rule with two real users, a test member with the read-only role deleted two transactions. They were transactions that member had added. The code first checked "did you add this?" and, if so, let it through. The role was never consulted.

Now, inside a space, the role applies to everyone, including whoever added the transaction or created the account.

One household's transfer, suggested in another

When an instant transfer (a PIX, Brazil's instant payment) arrives from the bank, Snabber looks for a planned entry that matches it (the neighborhood security fee, the rent) and suggests marking it as paid. The search looked at all of the person's unpaid entries, across every space. A transfer from the household space could become a suggestion for an account in the business space.

And the screen showing the suggestion filtered by whoever was looking. The transfer had been synced through the other member's bank connection, so the suggestion showed a warning and the dialog opened empty. Now suggestions only match transactions in the same space, and permission comes from the space, not from whoever connected the bank.

Sharing is not granting permission. It is deciding who owns each thing.

One plan, four people

In Part 2, we told the story of the family plan where four members together had four times the AI agents the plan included. That bug gave people more. The others gave them less:

  • Connecting a bank. The screen counted the group's connections and allowed it. The server counted the member's own connections, on the free plan, and refused with "account limit reached".
  • AI agents. A member turned on an alert successfully, but the job that fires alerts looked at their own plan, free, and never sent anything.

And leaving the group has an order that matters. When the plan holder loses their plan, the members leave first, while the plan is still active. That way, each member gets three days of grace and an email. In the opposite order, they would leave with no warning, no plan and no time. And a member's bank connection is never deleted because of a downgrade they did not ask for.

Deleting your own account, in a space that belongs to more people

Deleting an account looks simple until the person is in a space that other people share. Their entries are part of the household's history. And if they are the only admin, the household is left with nobody who can manage it.

Since October 15, deletion works space by space. The personal space goes entirely. In a shared space with other active members, the app asks whether the entries stay with the household. And the last admin of a space in use cannot leave without first promoting someone, right there in the dialog.

Personal and business accounts at the same bank

Someone with a personal account and a business account at the same bank uses two spaces: personal and business. In October, when connecting the business account, the new connection found an account named "BANCO INTER", the same name as the personal account, and adopted it. Result: 28 duplicated transactions, one copy in each space.

The rule that reuses an account by name exists for people who reconnect their bank and want to keep their history. It just never asked whether that account still belonged to a live connection.

snabber-fin
$ git log --oneline -i --grep=workspace
9889059b contas: ignora resposta atrasada ao trocar de workspace
43ba3170 Conta do workspace em todo lugar: escopo por membro, contas sem duplicar e reconciliação
37ae5725 Edição de transação resolve a conta pelo workspace, não por quem edita
4ce8fb2b travas de move workspace para sync em andamento
d8b6ebca workspace e initial sync dangerous changes
78fbbd07 fix: corrigir deleção de transação em workspace compartilhado

Some of the 69 commits with "workspace" in the message, June to November 2026. The highlighted one reads "Workspace account everywhere: per-member scope, no duplicate accounts, and reconciliation". The fifth is one of the five "dangerous" commits from Part 0.

What we did

  • ✓The account belongs to the space. The creator only breaks ties.
  • ✓Every entry path (form, spreadsheet, Telegram, AI, integrations) looks for the space's account before creating another.
  • ✓The role in the space applies to everyone, including whoever added the entry.
  • ✓Payment suggestions only within the same space.
  • ✓A shared plan with group-wide limits, and members leaving with a grace period and a warning.
  • ✓Account deletion space by space, without wiping out anyone else's household.

What we still haven't solved

The number at the top. Of 218 shared spaces, 14 have more than one person. Most people create a "shared" space to separate something (a renovation, a trip, a small business) and never invite anyone. We did a lot to make invites work. We have not yet made people send them.

Inside a space, every member sees all of its accounts. There is no "only I can see this account" within a household. Anyone who wants privacy for part of their finances needs two spaces.

And a bank connection brings every account from that login. You can move an account to another space, but you cannot stop syncing one specific account. The guardrail that stops one connection from adopting another's account is also still to come. The personal/business case was cleaned up by hand.

If you are going to let two people use the same account

Decide who owns each piece of data before deciding who can see it. Does the account belong to the household or to its creator? That answer changes every query in the system.

And test every write path with a second user, with a different role. That is where everything breaks, and it is the test nobody runs alone.

Want to organize your household finances? Create your Snabber account and invite whoever shares the bills with you.

In the next part: a bank statement says more about someone's life than any diary. How we keep it.