Recognize preview accounts and market modes

Read the identity label before interpreting the workspace

A preview or fixture account is an explicitly selected development identity. It allows local work on navigation, saved records and sample interactions without pretending to be a normal production account. The label should remain visible wherever the interface identifies the current context. Treat its account access and billing behavior as development behavior. A preview account cannot establish that a real customer has the same subscription, and it cannot make ordinary billing changes. If you did not deliberately enter a development workspace, record the unexpected label before switching accounts or contacting support.

Understand why market mode is separate

Account fixture mode and market mode are independent settings in the application. A local preview identity can be paired with a real read-only market connection, while another development setup may use explicit fixture market data. This separation supports development without turning synthetic account entitlements into live customer access. It also means that one label cannot answer every question: a Preview account label describes identity context, whereas a source or fixture-data label describes the particular market evidence being displayed. Read both before deciding whether a chart is illustrative or observed.

Identify synthetic and retained evidence

A fixture chart or synthetic replay demonstrates behavior but does not prove that an exchange event occurred. Actual retained replay uses admitted chronological market inputs and reports their coverage. The quality labels distinguish these cases, and a replay panel should not be interpreted from its moving clock alone. A smooth sample sequence can look more complete than a real captured period with gaps. Those gaps are meaningful evidence of what was unavailable. Do not compare a fixture total with a live tool as if they were independent observations of the same session.

Confirm the context you are working in

Use the same short inspection whenever you open a local development workspace, switch accounts or share a screenshot with someone who cannot see your setup.

1. Read the current account identity and note any Preview or fixture designation.
2. Inspect the current market tool's source and quality labels instead of assuming identity mode determines the feed.
3. Check the exact instrument, selected date and latest observation time.
4. Open the relevant plan or availability view on a normal account when you need to confirm real access.
5. For replay or history, read whether the panel uses synthetic fixtures or retained captured evidence.

Keep saved configuration in perspective

A development workspace may let you save layouts, watchlists or template choices so interactions can be tested repeatedly. The existence of a saved record proves that the application accepted that configuration in the current context; it does not verify a production provider, payment flow or email delivery. Similarly, adding a tool to Map proves only that the view is part of the available interface. A normal customer still needs the relevant server-authorized access and available source inputs. Copying a sample arrangement cannot convert missing provider history into real observations.

Recognize account changes and remembered browser state

Some layout conveniences are remembered locally by the browser, while saved account records remain owned by the signed-in account. After changing accounts, verify the displayed workspace and selected Order Flow template rather than relying on a familiar name. The application scopes remembered selections to accounts where required and clears authenticated data at session boundaries. A changed selection or a brief loading state after account switching can be expected while the new account's records are loaded. A previous account's preview access should never be treated as evidence of the new account's entitlements.

Report unexpected preview behavior clearly

If a normal sign-in unexpectedly opens a preview context, include the sign-in method, account label and page in a support ticket. Explain whether you deliberately used the development workspace entry point and whether a reload changed the label. If market data looks synthetic, include the source or quality text from the specific tool, not just the global connection indicator. This helps distinguish an identity-mode issue from a fixture market selection or an unavailable live source. Never use a development sample as proof of verified live provider delivery, real payment processing or complete retained market history.