CapitelistHelp Center

Security guide

Coming soon

Send a Legacy Test Email

Test whether Legacy Delivery contact emails can be reached before activating the protocol.

Current Capitelist screen for Send a Legacy Test Email.

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 contact or review section

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

Choose test email where available

Pick the option that matches the real-world record you are adding or reviewing. If two options look similar, use the one that matches the source document, not the one that makes totals look cleaner.

03

Send the test to the selected contact

Use this step to turn loose information into a clear portfolio record. If you are missing an input, note the gap instead of guessing.

04

Confirm receipt outside Capitelist

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

  • Checks contact reachability before a real continuity event.
  • Reduces risk of stale or wrong contact details.

What it does not do

  • A successful test email does not prove future availability.
  • Email delivery does not confirm identity.

Common mistakes

What to check

  • Warn contacts before testing sensitive workflows.
  • Update bounced or outdated addresses immediately.

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 Send a Legacy Test Email 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