This is an Admin guide for operating ShuffleKit, not for building a game. The Admin area is restricted to authorised accounts; for them, Admin (the shield icon) sits in the sidebar footer beside the help menu, and anyone else who opens an admin page is sent back to Cards. It includes production and user data, so work from a need-to-know mindset, avoid sharing screenshots with personal data, and use destructive controls only after confirming their target.
Its own sidebar lists Overview, Funnel, Onboarding, AI Usage, Demo, Templates, and Support. Back to App at its foot returns to your projects. Templates and icons have their own guide: Admin: Templates & Icons.
Start with Overview
Overview opens with the business: MRR, net paid adds, churn, how many new signups made a card, how many came back, and active users, followed by activation steps, feature reach, support, plans, cancellation reasons and checkouts. Under Everything in the instance are the totals for users, projects, cards, media files, versions and storage, with breakdowns and a People list you can switch between Newest and Most projects. Click one of the instance tiles to put its series in the chart above them. Feature-interest responses appear at the bottom when there are any.
The range picker at the top sets the window: 7, 30 or 90 days, or all time. Each tile compares its window with the one before it. The figures are counted in the database, so large totals are real counts rather than a capped sample.
Use it to notice a change worth investigating; do not treat a single headline metric as the explanation. Pick a window, form a specific question, then use Funnel, Onboarding, AI Usage, or Support to find the evidence behind it.
Investigate the funnel and replays
Funnel links out to three PostHog dashboards: Conversion (signup, onboarding and subscription funnels by channel and device), Activation & product usage, and Tours & announcements. The funnel charts are no longer drawn inside the Admin area.
The Session replays button on the same page opens the replay drawer. It loads recent PostHog recordings on demand and shows the start URL, duration, active time, clicks, keypresses, console errors, start time, and a Live badge for a recording still in progress. Watch replay opens the recording in PostHog.
Use a replay to answer one bounded product question, for example why people abandon a template-selection step, then record the finding. Delete recording removes that evidence for good, so verify the exact session and use it only for a genuine removal need.
Monitor onboarding, AI, and the demo
- Onboarding reports the guided first-game flow: completion, what people said about their pain points and tools, recent completions, and people who have not finished. Tour numbers are in the PostHog Tours & announcements dashboard linked from the same page. Use it to locate a drop-off, then confirm the cause with the funnel dashboards or a replay.
- AI Usage has the same range picker. It breaks down total, text and image spend, tokens, requests and images; click a tile to chart it, and switch the chart between Daily and Cumulative. Below are the token mix, image output, the tools the agent called, image requests, spend per model, the heaviest users, and recent activity. Compare trends before changing limits or prompts; an isolated spike is not automatically a defect.
- Demo manages the landing page demo. The current demo shows its project, counts, publish date and whether a table is saved. Select the project to snapshot, use Show Preview to check it, and confirm before Publish to Demo or Update Demo; removing the demo also asks you to confirm. Set Up Playtable opens a live table on the demo project so you can arrange it, Center View frames it, and Save Playtable State stores that table and camera for the demo. Import to My Account makes an editable copy of the current demo for you. Demo changes are visible beyond the Admin screen.
Work the support inbox
Support is the inbound operational inbox. Search by email, name or message; filter by reply state, ticket state, topic (Bug, Feature, Account, Billing, or Other) or plan (paying now, canceled or lapsed, payment failed, Free, Hobby, Indie); and choose an ordering such as Needs reply first. The list supports keyboard navigation with j/k or arrow keys, and Escape closes an open conversation.
Open a conversation, read the thread, and check the account panel beside it: plan and billing state, account, onboarding, usage, earlier tickets, and the Dodo customer and subscription IDs to copy. Write a concise reply. Drafts are kept per conversation, even across a refresh. Attach files only when they are necessary and safe to share, then choose Send reply and set the ticket with Mark resolved or Reopen. Do not paste secrets, reset links, payment details, or other customers' information into a response.
Close the loop
Route each operational observation back to a decision: a product issue becomes a scoped fix, a repeated support question becomes clearer documentation, and validated interest may guide the roadmap. The user-facing tutorials cover the tools customers can use; this guide explains the internal controls that keep those tools reliable.
