# מעטפת מוצר אחידה

> תיעוד מקור. מקור: docs/unified-product.md · 6a466bf.

Personal, Family, Business and Enterprise are plan variants inside `PlatformPortal`. Driving destinations and management destinations share the same account identity, navigation, theme, sound controls and mobile drawer. The former `EV1App` standalone shell is no longer mounted by any route.

## Canonical destinations

Connected accounts use `/platform/{tenantId}/{section}`. Explicit demo accounts use `/fleet-demo/{tenantId}/{section}`. Both include dashboard, map, favorites, station details, vehicles, providers, sessions, account profile, device preferences, support and notifications. Management destinations retain the existing plan and role checks, while API authorization remains authoritative.

Station links use `/station?station=mot-{id}` within the chosen account. QR results and map detail links use that same base path. Provider selections come directly from the account displayed in the shell; demo choices use the demo store and connected choices use the authenticated API. Previewing all networks remains an explicit map action.

The map and favorites keep the fixed viewport layout, a single results scroll surface, and map/list switching on mobile. Secondary navigation lives in expandable account-management and profile/help groups. The company website link is always available in the sidebar and on the account-selection and public authentication pages.

## Entry and compatibility

The product root opens the selected account, resolves an authenticated membership, or sends a new visitor to account selection/onboarding. It does not expose an additional driver dashboard. A browser remembers its current selection for navigation convenience; this is not an authorization mechanism. Connected memberships are checked through the context API, and direct account requests still require server authorization.

Legacy vehicle, history, billing, provider, preference and profile URLs resolve into the selected account. Station deep links retain their destination through account selection. Existing registration and legal URLs use a small public page frame. Company and internal-admin surfaces retain their existing separation.

Legacy browser-only charging simulations are not imported into account billing or session records. Their stored data is not deleted. The live charging-provider and payment integration status has not changed.

## Verification

Navigation unit tests cover aliases, account-specific URLs and malformed destinations. Browser tests cover all four plans, deep-link onboarding, provider isolation across account switches, company navigation, viewport fit and the absence of a second application shell. Existing location, QR, profile, theme and sound checks run against the new account destinations.
