Yes. Any point type registered with GamiPress is detected automatically and appears as a column option. Credits, gold, XP, or whatever you have defined all flow through the same dropdown. Switching between types reuses your filter and sort settings, so you can move between economies without rebuilding views from scratch.

Yes. Click a point cell, change the value, and SleekView writes the adjustment back through the GamiPress API so logs stay consistent. The change appears as a manual transaction with the editor recorded, which keeps your audit trail complete. Triggers fire normally, so dependent achievements and rank promotions still recalculate after the edit.

Achievements, Ranks, Restrict Content, and most other add-ons are picked up since they all write to the same earnings table. Add-ons that introduce custom meta fields can have those fields surfaced as additional columns. The detection is schema-driven, so installing a new add-on rarely requires you to reconfigure existing views.

Yes. Add the rank column and the user's current rank appears next to their balance. Sort by rank to see who is at each tier, or filter by rank to find members stuck at one level. Combine rank with point balance to spot inconsistencies, like a Master rank with only Novice-tier credits.

Yes. Sort by point total, hide non-leaderboard columns, and embed the table on a public page. Use role-based column visibility to keep moderator-only fields private. The result is a real leaderboard with sorting and filtering rather than the static shortcode the GamiPress core ships with.

Yes. Adjustments fire the standard hooks so dependent achievements and rank promotions still recalculate. If a manual point award pushes a user across a rank threshold, the rank promotion fires automatically and gets logged just like an organic earning would. Your downstream automations stay intact.

Yes if GamiPress is configured per site. SleekView views are site-scoped by default, but you can build a separate view per blog ID and link them from a network admin dashboard. For network-wide point sharing setups, point the view at the central earnings table and the same filters work.

Use role-based filters to scope each staff member's view. A community manager for the German cohort can be locked to users with the de-DE locale meta, while a course instructor only sees enrollees in their course. Combine with role-based column visibility to hide payment-related point fields from non-finance roles.