Review market settings and reporting
Edit CSFloat preferences, manage the SalesPanel reporting key and distinguish saved configuration from operational health.
Open Markets in the intended workspace. CSFloat preferences and the SalesPanel reporting connection serve different purposes. Your role determines which settings you can read or change.
Review CSFloat preferences
- Open CSFloat. Wait for the saved preferences to load before making changes.
- Review the offer, buy-order and sale-pricing settings. Monetary fields labelled USD use dollar amounts: enter
5.00for five dollars or0.01for one cent. - Change only the values you intend to change, then choose Save preferences. Use Discard changes to return to the current saved values.
- Read the result. A successful save confirms the preferences were accepted; it does not activate trading.
Workspace setup uses the same preference editor. Returning to setup reads the existing configuration. Saved preferences present in the final review means preferences exist; it does not mean that visit submitted a new save.
If another edit changes a value you are working on, compare the current values with your draft. Keep my changes retains your edits for a new submission; Use current preferences adopts the saved values. Review the result before saving.
Review the SalesPanel connection
Open SalesPanel and check the recorded connection:
| Field | What it establishes |
|---|---|
| Credential | Whether the workspace has a saved reporting key. |
| Saved key | The available suffix of that key, without revealing it. |
| Execution setting | The execution setting returned for the workspace. |
| Reporting health | Credential metadata does not measure current reporting health. |
| Updated / Updated by | The available record of the credential update. |
To set or replace the key, enter it in New API key and choose Save API key. This replaces the workspace reporting key after the required provider access is checked. It does not enable execution.
Authorized managers can reveal and copy the saved key when needed. Hide it afterward and keep it out of screenshots, messages and shared notes. Revealing a saved key is separate from entering a replacement.
Recover an uncertain save
An unknown outcome means the save was not acknowledged. It does not prove the change failed, and the form prevents a blind repeat.
- Preferences: choose Check saved preferences, compare the current values with the retained draft, then make the explicit review choice. Matching values do not establish which request saved them or recover the earlier acknowledgement.
- Reporting key: choose Check saved connection. A suffix or update time cannot prove that the submitted secret was saved. Review the connection before starting another edit; enter a replacement only when you intend another key rotation.
- Save acknowledged, read failed: use the displayed retry for the read. The read failure does not undo the acknowledged save.
Follow recorded activity
Use Marketplace history in Trading activity to inspect retained observations and their source evidence. Purchases and Contract sales show the separate contract records. Links appear when your role includes the corresponding records.
A saved key, an enabled execution setting or retained history does not establish that reporting is currently healthy or that an order will execute. Coordinate the pilot's trading transition with the operator before relying on live buying or selling.
Continue with marketplace history or contract configuration.