The Ultimate Member myCRED integration ties myCRED's points system to Ultimate Member profiles: members earn or lose points for actions (registration, login, posting, referrals), with each event recorded in the myCRED log table (commonly wp_mycred_log) carrying user_id, ref, creds, time and ctype columns. Each member's running balance lives in usermeta as a myCRED point-type key. The default surfaces are the myCRED log screen and a per-profile points panel, which is right for one-member-at-a-time audit and unhelpful for understanding the points economy across the community.

SleekView reads wp_mycred_log joined with wp_users and Ultimate Member usermeta and renders the ledger as a sortable audit table. Filter to last-30-days awards for bonus-event review, sort by creds for top-earner shortlists, group by ref to see which actions actually carry the economy. The same dataset the chart view aggregates becomes a row-level surface for community managers, finance and admins.

myCRED keeps owning rules, hooks and balance calculations. The table view owns the audit surface, so the ledger myCRED already writes stops hiding inside a paginated log screen and becomes something operations can actually query.

Ultimate Member myCRED captures genuinely useful data: who earned how many points, for what action and when. The default surface places that data inside a paginated log screen and per-profile panels, which is right for auditing one event and unhelpful for almost everything operators do with a points economy at the community level. A queryable ledger table answers the questions teams actually ask: who is the top earner this month, did the bonus event drive activity, which adjustments need review.

Same log rows, same creds values, completely different decision posture. The table renders the ledger myCRED already maintains as an auditable cohort, which is the difference between knowing the economy exists and knowing how it is performing this quarter.