All updates

Manage members from the user list: fields, balances, and discipline

Manage every member field in one place, read XP, coins, and tags in the user list, take disciplinary action on a member, and review every penalty.

01 ·Manage every member field in one place

A User Fields page under user management collects every field a member record can hold. It separates the thirty default fields that come with the platform from the custom fields a broker creates, each on its own tab, and lists each field with its type, who created it, and when. A broker adds a custom field from here, choosing from nine field types, and edits or deletes the custom fields. The default fields stay in place and cannot be deleted.

Why it matters

A broker that tracks traders by their own attributes, a desk, a tier band, an account reference, needs one place to see and shape what a member record can store. Keeping the default and custom fields together with their type and origin makes the shape of the member record something a broker can read and change directly.

02 ·Read XP, coins, and tags in the user list

The user list gains Total XP, Total Coins, and Tag columns, and its columns are reordered to a set sequence. The Tag column shows a member's first tag and folds the rest into a count that opens to the full set on hover. A broker manages tags from the list itself: adding a tag, creating a new one inline, and removing a tag a member holds without leaving the row.

Why it matters

A broker working the member list wants a trader's standing in the reward program visible alongside their details. Reading total XP and coins per member, and tagging members where they sit, turns the list into a place to group and act on traders by how far they have come in the loyalty program.

03 ·Warn, suspend, or ban a member

Disciplinary actions move into the user list under the manage user control. A broker can warn, suspend, or ban a member from there, each opening its own form. Two fields back this up, a penalty field and a suspend-until date, hidden by default and turned on from the field dropdown when a broker wants them in view.

Why it matters

A broker moderating a community wants to act on a member where they already manage them. Handling a warning, a suspension, or a ban from the member list, with the penalty and the date a suspension lifts on the same record, keeps moderation in one place rather than a separate tool.

04 ·Review every disciplinary action in one log

A Misconduct Log records the penalties handed out across the community. A broker filters it by role, type of penalty, who assigned it, channel or location, and date, and chooses which columns to show, with the member and the penalty always present. Opening a member's history from a row shows their misconduct on its own, and a warning carries no revoke action because there is nothing to lift.

Why it matters

A broker enforcing community rules needs a record of what was done and why. A single log of every penalty, filterable down to a role or a channel and openable per member, gives a broker the history to apply rules consistently and to answer a member who asks.