CapitelistHelp Center

Security guide

Coming soon

Legacy Delivery Protocol

Configure the inactivity-based process that helps trusted people recover essential information if the owner cannot respond.

Current Capitelist screen for Legacy Delivery Protocol.

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 > Delivery Protocol

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

Set inactivity timing, owner check-ins and travel mode behavior

Set this based on the real constraint behind the record: currency, ownership, liquidity, date, access or review cadence. Do not change a setting only to force a nicer dashboard total.

03

Add the required trusted contacts and recovery setup before activation

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.

04

Use QA cadence only in development or admin-approved testing

Use the option named in the step only when it matches your source. If the source is weaker than the label suggests, record the uncertainty instead of making the value look more precise.

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

  • Creates a structured recovery path for critical information.
  • Separates owner check-ins from beneficiary release.
  • Reduces reliance on informal instructions.

What it does not do

  • Legacy Delivery is not a will, trust or probate process.
  • Release depends on correct contact data and recovery configuration.
  • Capitelist cannot bypass missing recovery material.

Common mistakes

What to check

  • Tell trusted people what Capitelist is before they need it.
  • Keep phone and email details current.
  • Test the recovery process after setup changes.

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 Legacy Delivery Protocol 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