Community Launch Checklist and Admin Troubleshooting

Run this checklist with an owner/admin account and a separate member account. Add a signed-out browser when any page is public. Never test production purchases, outreach, or destructive actions with a real member.

Community and access

• About, icon, cover, description, support email, language, URL, privacy, and public metadata are correct.
• Purchase, request-access, single invite, CSV invite, and affiliate/funnel paths grant only the intended access.
• Categories, rules, navigation tabs, dashboard, sounds, and levels are understandable.
• Owner/admin pages reject a member and signed-out account.

Learning and events

• Courses, Course Studio drafts, lessons, resources, quizzes, progress, certificates, and cohort rules work in the member view.
• Draft content is hidden and published content is available to the correct tier.
• Tutor answers are grounded, practice answer keys are reviewed, and Cerebro does not expose another member's personal memory.
• Event date, time zone, recurrence, access, meeting link, reminder, and calendar subscription are correct.

Growth, automation, and safety

• Pricing, billing, payouts, discovery, funnels, affiliates, and attribution match the published offer.
• Retention starts at draft-for-approval with a conservative cap; channels and plugins use test recipients/data.
• API/MCP tokens use least privilege, an expiry, secure storage, and a verified revocation path.
• Check narrow mobile, tablet, and desktop layouts in light and dark mode.
• Complete every task with a keyboard and visible focus; check headings, labels, status messages, images, and screen-reader names.
• Verify reduced motion and that color/sound are not the only status cues.
• Test the Help bubble, search, quick prompts, feedback, and a no-result query.
• Revoke test tokens, remove test payment data, and keep screenshots free of personal or secret information.

Open the Help panel from the separate member view. Confirm its role context and locale, select each quick prompt, follow the cited article, and test an empty/no-result query without submitting sensitive text.

Capture a useful incident

Record the route, community, role, locale, browser, time, correlation/run identifier when visible, expected result, actual result, and a cropped/redacted screenshot. Note whether the failure is a permission denial, 404, loading state, empty real-data state, credit/plan gate, validation error, or server error.

Check the owning settings section, operational report, and recent audit/run history before changing configuration. Do not retry sends, payments, generation, publication, or deletion until you understand whether the first attempt committed.