Gamification 0.9.94 / Core Concepts
Member balances and history
Give members private, paginated access to exact reward records.
Signed-in members can view exact current and lifetime totals plus paginated transaction history. History filters support point type, human-readable source, action/transaction type, start date, and end date. Each history item retains its exact decimal string and includes a display-formatted amount derived without floating-point conversion. Owners and administrators may inspect full permitted provenance and transaction details.
Public source labels describe the member activity rather than its software provider. When a transaction is tied to content, the configured label for that content type takes priority. Administrators can customize content-type and fallback labels under System → Activity sources → Public source labels. Provider and platform identifiers remain immutable audit provenance but are not projected into member history.
Public profile surfaces are disabled by default. When enabled, administrators choose visibility, an explicit point-type allow-list, and which independent profile surfaces exist. Reward history, balances, achievements/badges, ranks, quests, and streaks can be separate profile tabs or an intentionally combined tab. The main SnapWeb and FluentCommunity Rewards destinations independently select one view; Reward history is the default. The combined-overview switches affect only destinations explicitly configured as Combined overview.
History is chronological and paginated, with one immutable point movement per row. The configured point-type allow-list constrains both balances and history. A zero-only member with no earned records or activity follows the configured empty-profile policy. Public visitors never receive internal UUIDs, raw provider IDs, private metadata, or full history. Public activity is private by default and can be limited to a sanitized summary. Members may opt out when that option is enabled.
Achievement earnings and Rank assignments retain their definition-version identity. Member, shortcode, terminal, and administration history surfaces use the label belonging to the version that was earned or assigned rather than silently replacing old history with a later renamed definition.