Product updates as they ship.
Market charts and live activity checks now load a single bounded trade page across all outcomes. Busy markets require less data transfer while keeping the same trade ordering, history coverage, and activity indicators.
When enabled, tournament administrators can queue and inspect settlement reconciliation while a tournament remains archived. Restore remains a separate action. This capability is disabled by default during rollout.
Organization sites now show the name of the organization's configured tournament in the header chip, tournament hub, leaderboard and portfolio scope pickers, and past-season standings instead of a fixed label.
Organization admins can now archive a tournament from the admin panel, hiding it from members and freezing trading while open orders stay as they are, then restore it later or reset its balances. API tournament lists now exclude archived tournaments unless they are explicitly requested.
Organization member and analytics exports now include registration details collected at sign-up: country, date of birth, university, expected graduation, contact opt-in, and rules acknowledgement. The iCIMS export now also reports contact opt-in.
Organization admins can choose whether Tournaments appears in their site navigation. Profile pages link members to the tournament list available on their current site.
Organization leaderboards and profiles now use consistent P&L language. The guide now uses clearer gain, loss, and payout wording.
Organizations can now keep participant notifications in the app instead of sending them by email. Account confirmation, confirmation resend, and password reset emails remain available.
Organizations can now choose the tournament shown by default across markets, portfolios, leaderboards, and API requests. A scheduled tournament can be selected before it opens, keeping trading locked until its start date.
The API guide now explains explicit tournament reads and enrollment requirements, and the Postman collection includes the current tournament signup and currency settings.
The API reference now explains which routes participant keys can use and which require an organization owner or administrator.
