​

Family Sharing

Family sharing allows you to share specific accounts with other members of your family, enabling collaborative financial management while maintaining privacy and control over your data.

​

How Family Sharing Works

Each Sure family can have multiple members with different permission levels. You can selectively share accounts with specific family members, giving them View only, Can annotate, or Full control access.

​

Permission Levels

When sharing an account you assign one of three permission levels to each family member. The account owner always retains full control and cannot be removed through the sharing settings. In bulk edit and the categorize flow, Full control (full_control) allows changes to all supported fields. Can annotate (read_write) allows category, merchant, tags, and notes, while View only (read_only) accounts are skipped. Can annotate does not permit name, date, or amount changes.

​

Sharing an Account

To share an account with family members:

1. Navigate to the account you want to share
2. Click the Share button or access sharing settings
3. Select the family members you want to share with
4. Choose their permission level (View only, Can annotate, or Full control)
5. Click Save

The account will now appear in the selected family members’ account lists with the appropriate access level.

​

What Gets Shared

When you share an account, the following information is accessible to family members:

• Account balance and balance history
• Transactions and transaction details
• Holdings (for investment accounts)
• Trades (for investment accounts)
• Account settings and preferences

​

Privacy and Scoping

Family sharing respects privacy boundaries:

• Scoped views: Each family member only sees accounts shared with them
• Reports: Financial reports are scoped to only include accounts the user has access to
• Budgets: The household budget includes shared accounts. Personal budgets (when enabled) are scoped to each member’s own accounts independently.
• Totals: Net worth and other totals reflect only accessible accounts
• Sparklines: Sidebar group sparklines aggregate only the accounts accessible to the current user, so each member sees balance history for their own accounts rather than the full family
• Providers: Third-party provider connections are scoped per family. When a sync completes, the browser refreshes through its own authenticated request, so account visibility is checked for that member. Automatic refresh can be deferred while a form or dialog is in use; provider-card HTML is not broadcast to the whole family.
• Provider cards: Connection cards on the accounts page show a member only accounts they own or that have been shared with them. If a connection has three accounts and a member has access to only one, that card displays only the one shared account. Admins see all accounts on every connection.
• Provider sync summary: When a member can see only some accounts on a connection, the sync summary shows counts rather than account names and details for the other accounts on that connection.
• Manual accounts after provider setup: When provider setup or linking refreshes the Accounts page, its manual-account list includes only accounts the current user owns or that have been shared with them. This also applies to admins.
• Merchants: Merchant data is shared across the family for consistency
• Personal budgets: When personal budgets are enabled, each member’s actual spending is scoped to their own accounts only
• Insights: The shared insights feed only shows insights about accounts every active family member can access. Access is checked again when the feed is read, so revoking a required share hides the related insight on the next read.
• Sync updates: After an account sync, page refreshes use each browser’s own authenticated request. Automatic refresh can wait while the user is interacting with a form or dialog. Account names and balances are not pushed to family members who do not have access to that account.

​

Managing Shared Accounts

​

Viewing Shared Accounts

Shared accounts appear in your account list with an indicator showing they’re shared. You can filter your account list to show:

• Only your accounts
• Only shared accounts
• All accounts

​

Editing Shared Accounts

If you have Full control permission on a shared account, you can:

• Add, edit, and delete transactions
• Update account settings
• Record trades (for investment accounts)
• Categorize, tag, and add notes to transactions

If you have Can annotate permission, you can categorize, tag, and add notes to transactions but cannot add or delete transactions or change their financial fields. If you have View only permission, you can see the account data but cannot make any changes.

​

Imports and account write access

Publishing or reverting an import writes to (or removes entries from) its target accounts. Sure requires write access — owner or full_control — to every pre-existing account the import targets, including accounts referenced via column mappings and any accounts that already received entries from a previous publish of the same import. Accounts created by the import itself are excluded from this check. Statement imports also require permission to view and manage the associated statement. A family member with read-only access to an account cannot publish or revert an import that targets it, even if they created the import. If a member’s access to an account is downgraded after an import is configured, someone with write access to every pre-existing target account must complete the publish or revert.

​

Removing Access

Account owners can remove sharing access at any time:

1. Open the shared account
2. Go to sharing settings
3. Remove the family member or change their permission level
4. Click Save

The account will immediately disappear from that family member’s view.

​

Family Roles

​

Admin Role

Family admins have additional privileges:

• Manage family members
• Configure family-wide settings
• Manage all third-party provider connections
• Access all family accounts (if shared)

​

Member Role

Members can connect and manage their own Plaid bank connections. This is the only provider integration a non-admin can manage — all other providers require admin access. A member can re-authenticate, sync, and delete the Plaid connections they created, but cannot modify connections created by other members or by an admin. If a member is demoted to guest, an admin must manage their connections.

​

Guest Role

Guests have read-only access to family configuration. They can view categories, tags, merchants, and rules, but cannot create, edit, or delete them. They also cannot create or manage any provider connections. The option to connect a provider is not shown to guests; the server also refuses connection creation for that role. These restrictions are enforced consistently across every access path:

• Web UI: Write controls for categories, tags, merchants, and rules are hidden or disabled. The rule toggle is shown but disabled. The “create a rule?” prompt after categorizing a transaction is not shown.
• API: Guest API credentials receive a 403 Forbidden response on any write endpoint for categories, tags, merchants, and family-configuration import types (category, merchant, rule, and Sure imports). Read endpoints remain available.
• Imports: Guests cannot create, publish, revert, or delete category, merchant, rule, or Sure imports. Guests also cannot publish any import — including transaction, Mint, QIF, or PDF imports — if publishing would create new categories or tags. Mapping an unmapped value to an existing category or tag, or leaving it empty, still works. For guests, reverting or deleting non-family-configuration imports requires write access to all affected accounts, including accounts created by the import; linked-statement permissions also apply.
• Import wizard: Guests can edit pending or failed imports that are not category, merchant, rule, or Sure imports, subject to linked-statement access requirements.
• Assistant and MCP: The create_tag, update_tag, create_category, and update_category tools are not available in a guest’s tool registry for either the chat assistant or MCP.

​

Use Cases

​

Couples Managing Joint Finances

Share checking, savings, and credit card accounts with your partner. Both can track spending, categorize transactions, and monitor budgets together.

​

Parents Teaching Financial Literacy

Share specific accounts with children in view-only mode, allowing them to learn about budgeting and money management without making changes.

​

Household Budget Collaboration

Share household expense accounts with all family members who contribute to bills, enabling transparent tracking of shared expenses.

​

Investment Portfolio Oversight

Share investment accounts with a financial advisor or trusted family member for oversight while maintaining control over trading decisions.

​

Security Considerations

• Encryption: All shared data is encrypted at rest and in transit
• Access control: Permissions are enforced at the database level
• Audit trail: All changes to shared accounts are logged
• Revocable access: Sharing can be revoked instantly by the account owner
• File attachment access: Sure checks access before serving protected financial attachments; public logos and avatars are exempt. Export files require the requester to be an admin of the owning family. Import files (PDF and NDJSON) and family document attachments require membership in the same family; statement-linked imports also require visibility of the linked statement. Direct attachment requests that fail these checks return a 404.

​

Best Practices

1. Start with view-only: Give new family members View only access first, then upgrade to Can annotate or Full control as needed
2. Regular reviews: Periodically review who has access to your accounts
3. Clear communication: Discuss financial goals and boundaries with family members
4. Use categories consistently: Establish category conventions for shared accounts
5. Respect privacy: Only share accounts that genuinely need collaboration

​

Limitations

• Sharing is limited to members within the same family
• Most provider credentials are managed at the family level by admins. Plaid connections can also be created and managed by members for their own bank accounts.
• Some account types may have restrictions on sharing
• Recurring transactions are scoped to the family, not individual users