The practical details before you centralize the workspace.
Short answers for the parts that matter most: what the product unifies, how data gets in, and how trust boundaries still work.
Check how the connected workspace works before adding records.
The questions move from product centralization to data handling, then into privacy and registration controls.
It centralizes holdings, imported trades, allocation drift, journal notes, and performance patterns so the investment record is not split across tools.
No. Broker sync can be enabled when credentials are configured, but CSV imports and manual records remain first-class ways to build the same ledger.
Imports can be staged and reviewed first. That gives the workspace a chance to surface malformed rows, duplicate records, and source-file context before records join the ledger.
A trade record explains what happened. The journal explains why it happened, how it was managed, and what should be checked before the next review.
No. The public pages are separate from authenticated app routes. Dashboard, reports, import, journal, settings, watchlist, and trade-log routes remain protected.
Yes. Private deployments can use registration controls so the public site can exist without opening the finance workspace to everyone.
Start by centralizing one source.
Import a sample, connect sync later, and keep every new source tied to the same investment workspace.