Information Architecture Detail layer Node page

6.14 Connections / Accounts

Where the trust promise made on the landing either holds or turns out to be marketing.

Node 6.14Type: page plus a dialogMVP Cluster 6 Account and Trustnoindex

Specified with the template fixed on the etalon, node 1.1 Welcome. Source: docs/nodes/6-14-connections.md. Composition from the block bank, type G. Supersedes this node's section of account.md.

Purpose and jobs

Every figure in the product comes from something listed on this screen, and this is where a person can end that. J1 and J5 are both primary, and E3 lives across this cluster: the mechanism table names Connections, Data and Privacy and Settings as three of E3's four homes.

JobsJ1 trust the connection and J5 keep control of my data, both primary.
URL/sources. Breadcrumb: back to Settings, where the You tab lands.
Entry, exitIn from node 6.16, from the sync-failed state 2.6.3, and from the trust line (GC6) on any screen. Out to nodes 1.3 and 1.4 in their in-app variants, and to node 6.15.
ComponentsGC1 detail variant with back, GC2 Global Tab Bar, GC6 Data Source and Trust in its full row form. This screen is where GC6 is at its largest; the compressed one-line version appears on nodes 1.3, 2.6 and 2.7.

Content blocks

#BlockCarriesFrom the bank
1Back, and the title (GC1)GC1TAKE
2One line saying what this screen is for, and the read-only promise repeatedJ1, E3, principle 4TAKE, DIFFERENTLY (Canva): a plain statement first, controls after. A list of controls with no statement reads as a menu of things being done to you
3A card per source: institution, which accounts are included, statusJ1TAKE (Linear, Squarespace)
4The last successful check, on every sourceGC6, J1, principle 4TAKE: exists in none of the sources. A silently stale connection makes the whole calm view quietly wrong, and the person has no way to know. It is the trust line from Home, one level deeper
5Reconnect, when a connection has expiredJ1TAKE: bank connections expire by design. The category treats that as an error; ours treats it as maintenance, in the same calm register
6Disconnect, with the consequence in the same sentenceJ5, E3, principle 4TAKE, DIFFERENTLY: every source offers disconnect and none says what happens to the data already collected. Ours says what stays, what goes, and whether the subscriptions remain visible
7The manual source card: "added by you", private, only what you typeD2, J5TAKE: the manual path is a source with equal standing, not a lesser mode
8Add a source, with no counter and no limit anywhere on the screen, into dialog 6.14.3D-Free, J1TAKE: a count beside a connection list reads as a cap even when there is none. D-Free is a promise this screen can quietly break by design, so it is written down as a block decision
9The provider note: US banks connect through Plaid, more regions soonD5TAKE
10A way into node 6.15 for the full "what we read" answerE3TAKE

Named and not added: a bank search and picker (Plaid Link owns that screen, the same boundary as node 1.3), per-integration permission toggles, and any count of connections used against connections allowed.

States, filters, the one action

NodeStateReads likeTrigger
-defaultThe ten blocks, one card per sourceAt least one source
6.14.1No sources yetBoth doors offered, in the same words used at node 1.2Nothing connected and nothing added
6.14.2Source needs attention"Banks ask for this now and then to keep your connection secure", the last figures still shown and datedA connection expired
6.14.3Add a source (dialog)Two options: connect a bank, or add them yourself"Add a source" tapped
-Loading sourcesSkeleton cardsFetching

On 6.14.2: the copy explains why a bank asks for this because the person's first reading of "reconnect" is that something went wrong with their money. Nothing did, and the screen has to say so before it asks for anything. On 6.14.3: this dialog is the resolution of FLAG 2. It creates no new screen: it reopens nodes 1.3 and 1.4 in their in-app variants and returns here. It was numbered on 2026-08-04, because account.md had it at 6.14.1, a number the sitemap already gave to the empty state. Filters and facets: none, a person has a handful of sources.

The primary is conditional, and that is deliberate. When a source needs attention the primary is "Reconnect", because that is the only thing on the screen costing the person accuracy. Otherwise it is "Add a source". The screen never has two primaries at once.

Responsive. Mobile: one column of cards, one action per card. Desktop: the same single column at a wider measure, and the tab bar becomes a left rail. Not a two-column settings layout with a category sidebar: it does not survive 360px, and that is also why this cluster is three nodes rather than one screen with sections.

Emotional support

JobMechanismWhere exactly on this page
E3 feel safe, control dataRead-only is stated in the same breath as the bank, the source of every figure is shown, and disconnect is reachable in one tap rather than buriedBlock 2 for the promise, block 4 for the source and its freshness, block 6 for the one-tap exit with its consequence stated

SEO, locked, open

SEO. noindex, no schema. Private, behind auth.

Locked: the last successful check on every source, disconnect with its consequence in the same sentence, no counter anywhere, reconnect as maintenance rather than error, the manual source as an equal card, FLAG 2 resolved through one dialog. Open: none.

Done at the wireframe rebuild, 2026-08-05: all four locked blocks are on the screen, node 6.14.3 has a page for the first time, and the Chase count is 11 on both the default and the reconnect state. It was 11 on one and 8 on the other: a stale connection does not reduce the count.

Grey screen: wireframes/connections.html. No coloured screen yet: only Home and Subscription Detail were taken into colour at Concept, and the rest arrive at UI + Visual (design/overview.html).