TradeHarbor treats authentication, brokerage authorization, account isolation and operational fail-safes as separate security boundaries.
No single control is treated as sufficient on its own.
Protected product access uses authenticated sessions rather than a shared dashboard password.
Brokerage connectivity uses the supported authorization flow rather than asking users to paste brokerage passwords into TradeHarbor.
The current runtime intentionally remains single-owner until database-backed multi-user isolation is completed and tested.
Starting live autonomous activity is an explicit operator action.
The operator can halt new autonomous activity without losing visibility.
Sensitive product APIs require authenticated sessions.
Multi-user access is being built around tenant-scoped data, brokerage connections, policy and runtime state.
TradeHarbor is currently operating as a private beta while we continue building secure multi-user infrastructure.