Buckets & Views Guide
Portfolixir groups your wealth with two tools instead of portfolios: a bucket is a label on your depots and cash accounts, a view is a saved filter over buckets that scopes the analytics pages and can carry its own target plan. This guide walks through four real grouping needs with the exact clicks, so you can map your own setup onto the model instead of reverse-engineering it. The reasoning behind the model is recorded in ADR-0024; the reference description lives in the product documentation.
Which do I need — a bucket or a view?
A bucket answers “what is this account part of?” — it is a label you put on depot and cash-account rows, and nothing more. A view answers “what do I want to look at (and steer)?” — it is a saved include/exclude filter over buckets that you pick in the view switcher, set as your default, and attach a target plan to. Rule of thumb: tag reality with buckets, then create one view per question you keep asking. Buckets alone change nothing on the analytics pages; only a view scopes what you see.
Use case 1: “My wealth” vs. “whole household”
You share some accounts with a partner and want two numbers: your own wealth and the whole household — without a joint account ever counting twice.
- Open Accounts & depots (sidebar, Administration area). Every row shows its bucket memberships as chips.
- On each row that is yours alone, click the + chip (Add bucket),
type
Mineinto the New tag field, and click Create tag. The tag is created and assigned in one step. - Tag your partner’s rows the same way with a new tag
Partner. Tag shared accounts with both — buckets are free overlapping labels, so a joint account may carryMineandPartnerat once. - Open Views (sidebar, Administration area — the same page the view
switcher’s Manage… link opens). Under 2. Views, type
My wealthinto New view and click Add view. - Click Edit view buckets on the new row. In the Buckets for My
wealth dialog, check
Mineunder Include buckets and press Save view. - Repeat for a second view
Householdthat includesMineandPartner(or simply check Include all buckets). - Open Wealth, pick
My wealthin the View: switcher at the top of the page, and click Set as default under Default view. The Wealth page and the Overview page now open on your personal number; the switcher still flips toHouseholdor the built-in Everything at any time.
The counts-once guarantee. In a view’s total, every account is counted
exactly once, no matter how many of the view’s buckets it carries. The joint account
tagged Mine and Partner appears once in Household, not twice. When a
view’s buckets share an account, the Wealth page shows a badge next to the
total — Overlapping buckets — accounts counted once — reminding you that
the per-bucket figures are overlapping facets and must not be summed; the
total itself is already deduplicated.
Use case 2: a strategy view with its own target plan
You run a retirement strategy across depots at several brokers and want its own target allocation and drift tracking — independent of everything else you hold.
- On Accounts & depots, tag every depot that belongs to the strategy
with a new tag
Retirement(the + chip → New tag → Create tag), regardless of which broker it sits at. - On Views, create a view
Retirementthat includes theRetirementbucket (steps 4–5 above). - Open Classifications, select the custom tree you steer by, and find
the Target plan section of its detail pane. In the selector Target
plan for view: pick
Retirement. - Click Create plan (or Copy from another view… to prefill from an
existing plan), enter a Target % per category plus the Cash
target, watch the Σ footer reach 100 % ✓, and press Save plan.
Plans are bound to the view (ADR-0020):
Retirementnow carries its own plan, and your other views keep theirs — or none. - Open Wealth and switch to
Retirement. The Target and Drift columns now measure only the strategy’s holdings against the strategy’s plan; the drift amounts tell you what to trim or add inside the strategy.
Use case 3: coming from Portfolio Performance
In Portfolio Performance you may have used depots or portfolios as categories — one “portfolio” per strategy, employer, or family member. Buckets and views replace that habit without the bookkeeping split.
- What the one-time migration created. When your data was migrated (ADR-0024), every former portfolio became one bucket and one view of the same name, so every number you could see before still has a view that shows it. The Wealth page announced this once with a dismissible notice listing the seeded views. Rename both freely on the Views page (Rename bucket / Rename view) — the names were only carried over, nothing depends on them.
- Migrated an empty database, restored data afterwards? The one-time
migration only converts the portfolios it finds. If you ran the upgrade
against an empty database and restored your data later, run
mix portfolixir.seed_scope_bucketsonce — it seeds the missing scope bucket + view per portfolio and is safe to re-run (already-seeded portfolios are skipped). - What imports do now. The import preview no longer asks for a target
portfolio. Instead it offers an editable bucket tag — The accounts created
by this import get the bucket tag: — pre-filled with a date-stamped
PP Import <date>. Keep it to find the imported accounts later, type the name of an existing bucket to reuse it, or check No tag — leave the new accounts untagged to skip tagging entirely. - Where the portfolio records went. Portfolios still exist as internal compatibility records, but they carry no behavior in the UI. The Accounts & depots page lists them in the collapsed, read-only Portfolio records (compatibility) panel; there is no create or edit UI anymore.
So the PP habit “one depot per category” translates to: keep depots as the bookkeeping reality your broker statements match, and put the categories into bucket tags — an account can carry several, which depot-as-category never allowed.
Use case 4: count it, don’t steer it
You hold Bitcoin as a long-term store of value. It belongs in your total wealth, but it should not distort the target allocation of your strategy — the motivating case of ADR-0018 (see ADR-0018).
- On Accounts & depots, tag the depot (or account) holding the position
with a new tag, e.g.
Store of value. - On Views, click Edit view buckets on your strategy view and check
Store of valueunder Exclude buckets. Exclude always wins: even if the account also carries an included bucket, it stays out. Press Save view. - Check the result on Wealth: under the built-in Everything view the position counts toward your total as before; under the strategy view it disappears from the 100 % basis and the drift table, so every other category’s actual weight is measured against the steered mix only.
Nothing is hidden and nothing is flagged per security — the same position is simply inside one view and outside another.
Honesty note: re-tagging rewrites history
A view resolves its buckets as of today. When you re-tag an account, the view’s whole historical series is recomputed with the new membership — there is no “tagged since” date. That is why view-scoped performance series carry the label Composition as of today: the chart answers “how would this view have developed with its current composition?”, not “what did I see last year?”. Bucket changes are recorded in the audit journal, so you can always reconstruct when a membership changed — but expect historical view figures to move when you reorganize your buckets.