Before you start
Start from the current portfolio state and treat the article as an operating checklist. If a required input is missing, record that gap instead of inventing precision.
Detailed steps
Open Support from the workspace controls when available
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.
Describe the issue, expected behavior and affected screen
Use this step to turn loose information into a clear portfolio record. If you are missing an input, note the gap instead of guessing.
Attach screenshots only when they do not reveal secrets
Attach or reference the clearest source available so the value can be checked later. Use the source that shows the date, amount, method and any uncertainty.
Follow up in the same ticket until resolved
Use this step to turn loose information into a clear portfolio record. If you are missing an input, note the gap instead of guessing.
Field guide
The label you and your advisors will recognize.
Match source documents where possible.Current portfolio value.
Use current value, not purchase price, unless cost is the only defensible estimate.Native currency of the asset or liability.
Do not change currency to force a base-currency display.When the value was last reviewed.
Missing dates create stale-data risk.Why the value is credible.
Use imported, market, appraisal, manager mark or internal estimate honestly.Decision rules
What it adds
- Creates a structured support history.
- Helps the team diagnose issues with screen and workflow context.
- Avoids mixing support requests with portfolio edits.
What it does not do
- Support cannot request passwords, seed phrases or full recovery keys.
- A support message does not grant permission to bypass security boundaries.
- Sensitive attachments may be restricted for admin roles.
Common mistakes
What to check
- Redact private account numbers, keys and beneficiary-sensitive details.
- Include exact steps to reproduce the issue.
- Use one ticket per issue when possible.
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 Support Tickets 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 other guide when source evidence changes.