CapitelistHelp Center

Security guide

Coming soon

Trusted Contacts

Manage beneficiaries, continuity guardians and other trusted roles used by Legacy Delivery.

Current Capitelist screen for Trusted Contacts.

Before you start

Decide what should be visible in normal workspace views and what must stay protected. Sensitive access details belong in encrypted/private areas, not ordinary notes or shared exports.

You know whether private data is currently hidden or included.
Sensitive details are ready to be stored only in protected fields.
You know who should and should not see this information.

Detailed steps

01

Open Legacy Plan > Trusted Contacts

Start from the screen named in the step and confirm the portfolio in the top bar before you change anything. If the wrong portfolio is selected, switch portfolios first.

02

Add each contact with role, email, phone and release level

Enter the values exactly as they appear in your source material. Include enough detail that you or an advisor can later understand what the record is and why the value is credible.

03

Confirm who should receive a package versus who should help verify continuity

Compare the screen against your source before relying on the result. Check name, value, currency, date, ownership, liquidity and whether private data should stay hidden.

04

Review contacts after family, advisor or entity changes

Compare the screen against your source before relying on the result. Check name, value, currency, date, ownership, liquidity and whether private data should stay hidden.

Field guide

Visibility

Who can see the record in normal use.

Keep private operational details out of standard fields.
Recovery context

How the information can be understood later.

Document non-secret context clearly.
Protected notes

Sensitive details encrypted behind private controls.

Never store raw secrets in regular notes.
Release level

What a trusted person may receive.

Match the role and relationship deliberately.

Decision rules

What it adds

  • Makes legacy responsibilities explicit.
  • Supports staged release levels instead of all-or-nothing access.
  • Keeps recovery workflows from depending on memory.

What it does not do

  • Contacts do not automatically receive all private data.
  • Contact records are not legal appointments by themselves.
  • Incorrect emails or phone numbers can block recovery.

Common mistakes

What to check

  • Use people who can act responsibly under stress.
  • Avoid naming people who should not know a private asset exists.
  • Review access levels before activating the protocol.

Entering a clean-looking value without recording where it came from.

Ignoring currency, ownership percentage or valuation date because the total appears reasonable.

Using ordinary notes for private access information.

Assuming Trusted Contacts produces advice, verification or execution beyond the workflow described here.

After you save

  • Return to Net Worth and confirm totals changed as expected.
  • Open Capital Review to see whether the record created, resolved or changed any review item.
  • Check whether the record should affect Forecast, Investment Plan, exports or share links.
  • Revisit this security guide when source evidence changes.

Keep reading