A first-visit rule for coins and milestones, and a permission for Export Histories
Coins and milestones can wait for a trader's first visit to the community, and a role permission decides who sees Export Histories.
01 ·Require a first visit before coins and milestones
XP & Currencies settings have a new toggle for each community: Require a visit before users can earn coins or complete milestones. It starts off for new and existing communities, and while it is off, nothing changes. With it on, a trader needs at least one recorded visit to the community before coins reach their balance or a milestone completes. The platform still records progress toward a milestone, and the milestone completes after that visit. The rule applies to coins that arrive through:
- user bulk updates
- Snowflake syncs
- inbound webhooks that map coins
- data workflows that post user fields
It covers every coin change on those routes, deductions and overwrites included. In a bulk update or a sync, the job skips any row that changes coins for a trader with no visit, carries on with the other rows, and gives the reason in the job details: User has not visited the community. The rule does not apply to coin corrections sent directly through the Integration API.
A community can hold imported clients who have not opened it yet. With the rule on, coins and milestone completions start at a trader's first visit, so the earn-and-spend loop begins with someone who has turned up at least once.
02 ·A role permission for Export Histories
Role permissions in Community Settings have a new Logs category, between Moderation and Integration, with one option: Export Histories. Search finds it under Logs or Export Histories, Select All includes it, and each role saves its own value. With it checked, members of the role see the Export Histories tab. With it unchecked, the tab disappears and its page will not open. The permission applies to admin-level roles, the community owner always has access, and it is now separate from the Audit Log permission. Every existing role starts with it checked.
Export Histories holds the record of past data exports. A broker can keep that record with the admins who handle data requests and hide it from other admin roles.
Scheduled user field resets run on their own worker, which moves through members in small, capped batches and resumes after a restart without repeating work.
16 SepThe Streak Log in settings shows the username for every trader.
16 Sep