The vaultie side of the V1 vault system, per the 2026-07-18 respec — reworked 2026-07-20 to Donna's review: the vault nav bar appears on every in-vault page (with an "All vaults" item at the start and Profile / Access at the end, Overseers only — Dwellers get a reduced bar); vaults can be pinned exactly like collections (pinned vaults appear in the app sidebar under Vault management, mirroring "Pinned collections" — that sidebar pinning still exists); the profile is full-width sections matching the collection/user profile layout with the standard Save; Access matches the project Access page and adds a permissions matrix; tables carry the standard white list bar; the item view matches the marketplace/launchpad token view; and Inventory uses the minted-token card grid with bulk select. Vault management is its own top-level area, gated per account; access is granted per vault location.
01All Vaults — pick a locationThe area's landing page: one card per vault location. Your role shows per location — access is per vault location, never for all vaults. Each card carries a pin toggle: pinned vaults appear in the app sidebar under Vault management, exactly like Pinned collections.
Vault management
Vault management
All vaults.
Here are all the vaults you have access to. Select one to manage.
02Vault overview — the vault nav bar, Overseer vs DwellerThe vault nav bar appears on every in-vault page, under the header. It starts with ‹ All vaults (back to the landing page) and ends with a pin toggle. Profile and Access sit at the end and only render for Overseers — the second strip below is the Dweller bar with the reduced link set. Shown here on the overview.
03Vault Profile — Overseer (edit)Reworked to match the collection / user-profile layout: full-page-width sections, stacked — no two-column split. The vault nav bar sits at the top (Profile active, Overseer variant). Saving follows the user-profile convention: one Save changes primary with Cancel, at the end.
Shown to a user with a shipment from this vault — where they direct questions about it.
03bVault Profile — Dweller (read-only)The same sections rendered read-only: plain values, no inputs, no Save. Dev note: with Profile removed from the Dweller bar, a Dweller reaches this view from the vault name/logo on the overview — confirm, or keep Profile (read-only) in the Dweller bar and drop only Access.
04Vault Access — team + permissions matrix (Overseers only)Matches the project Access page: the + Add vaultie button sits top-right in the white context bar, exactly where the project page puts "+ Add member" (checked against the access gallery — it is the established placement). The vault nav bar shows the Overseer variant with Access active. Below the team, the permissions matrix spells out Dweller vs Overseer — which lets the add modal drop its explanatory text. The provider's account is the permanent first Overseer.
Added by their existing Toko account — access to this location only, effective immediately.
See "What each role can do" on the Access page.
05Manage Shipments — list with nav + filtersThe vault nav bar (Shipments active) sits on its own row; the filter row (search + status segmented) gets its own row beneath it on the grey — the shell keeps them stacked, so the two bars never collide. The table sits on a white surface and ends with the standard white list bar (count · pager · per-page) per the pagination spec — that's the style-guide table handling. Status: en route → delivered → processed.
06One shipment · en route — view onlyDetail pages keep the vault nav bar (Shipments stays active, so you're never stranded); the status filters belong to the list and don't repeat here — the breadcrumb and the bar carry you back. While en route, items are view-only thumbnails. The one action is Mark as delivered (confirm + sender notified).
Are you certain that shipment from Graded Legends with JD014600003RS has been delivered? Vault One will be notified that you have received the shipment.
07One shipment · delivered — process items one at a timeSame page chrome as 06 — nav bar present, Shipments active. Once delivered, each item unlocks; items are processed strictly one at a time. When every item is accepted or rejected, the shipment flips to processed.
08Process an item — accept or rejectNav bar present. Left: the token exactly as the marketplace / launchpad token view renders it (main asset + thumb rail + title + attribute chips — same components), read-only, with the certificate number to verify. Right: the acceptance form — vault images are rectangular cards using the style-guide upload icon (icons/Icon=Upload); insurance/dispute evidence only, never the token's own assets. Saving vaults the item; rejecting opens the flag modal.
For insurance and dispute records between creator, vault and a future redeemer — these never touch the token's own assets.
Leave blank if covered by the facility-wide policy.
Flag a problem · Kaiju Ember
✕
The collection's admins will see this flag and decide what happens next.
Photo 1 ✓
Add photo
The creator chooses: return it or vault it anyway. Missing items are simply recorded as missing.
09A vaulted item — the marketplace token view + appended vault informationNav bar present (Inventory active). The left column is the same public token view a collector gets on the launchpad or marketplace — the token itself never changes. Right: the vault's appended information — status, rectangular vault images, insured value (vaulties + collection admins), vault id + location (vaulties only).
10Manage Inventory — the minted-token card grid + bulk selectReworked to match viewing minted tokens: nav bar (Inventory active), a filter row (search + status segmented), then the card grid — each card carries a status badge top-left (Vaulted · Redeem requested · Return requested) so flagged items read at a glance. Select mode ticks cards into the bulk bar (outer ring + corner check, the minted pattern); bulk actions: apply one set of shipping details to the selection (returns), or update locations. White list bar closes the grid.
10Redeem Requested — per-item fulfilmentOpening a redeem-requested card starts fulfilment: retrieve → package → label → ship, one item at a time; a hint offers combining a same-redeemer parcel.
Same redeemer, more items: the owner of Kaiju Prime also has 2 other redeem-requested items in this vault — consider combining them into one parcel with one tracking number.
Kaiju Prime · cert 91230011
Retrieve fromZ1·R02·B004·S11
Shipping details
10Return Requested — bulk shipping detailsBulk-selecting return-requested cards lets one set of shipping details apply to all of them.
12 selectedReturn to Graded Legends · Vault One
One set of shipping details · applied to all 12
11Redeemed Items — everything that leftSame chrome: nav bar (Redeemed active) + filter row + white table surface with the list bar. All items shipped from this location, so vaulties can answer enquiries: what went where (country only), when, with which carrier and tracking.