Yes. Moving a card calls the GamiPress award and revoke functions used by the admin, so point totals, related ranks, and notifications update through the normal hooks. Custom code listening to gamipress_award_achievement keeps firing without any extra plugin glue or workarounds.

SleekView reads the GamiPress user earnings table directly, where each achievement, rank, and points award has its own row. You pick that table as the source, choose the status column to group by, and SleekView renders one card per award with the fields you select.

Yes. SleekView ships with role-based permissions, so program reviewers can have a single page that holds the GamiPress board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role for safer manual review.

Custom achievement types and any extra status values appear automatically because SleekView reads distinct values from the chosen column. You can rename column headers, pick colors, and decide whether reviewers can drag cards between any two columns or only along the official path.

Each board has one source so the award rules stay clear. Most programs run separate boards for achievement earnings and rank promotions, link them from the same dashboard, and let reviewers switch between them. Card counts surface pending work in each lane.

Dragging never deletes data. It changes the status field SleekView is grouping by, which matches what the admin screens do. A revoke calls the GamiPress revoke function, so the badge can be re-awarded later from the same board without any data loss for the member.

Yes. Each card can show the time since the earning row was created or last modified, so a nomination waiting for days looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of each column so old work never silently drifts out of view.

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the earnings table for the status filter. Programs with hundreds of thousands of earnings rows stay responsive because heavy fields are only fetched for the cards currently on screen.