Set up and launch a new community

Owner setup order

Complete installation and sign in as the administrator. Record the edition/build.
In System → Settings set name, tagline, canonical URL, pagination, tag and username policies.
Upload header/light/dark logos in Branding; set the separate footer logo/about on Menus if desired.
Create forum categories/subcategories. Decide public, member-only, read-only and staff-only access before adding sensitive content.
Review every user group’s global capabilities and category levels. Group grants are additive.
Replace the default terms with your own community policy and publish any required help/custom pages.
Configure SMTP and test both immediate mail and ordinary queued delivery through the host scheduler.
Review spam heuristics, word filters, screened-address rules and Turnstile. Test with a genuine ordinary account.
Enrol owner/staff accounts in TOTP or passkeys and keep recovery methods securely.
Enable only the features you intend to offer. Install/enable the required free or licensed addons before configuring their screens.
Create download categories/compatibility presets and submission/review policies if you offer resources.
Configure integrated payment providers in sandbox first if you sell plans/resources; verify purchase and refund outcomes before live mode.
Activate the intended style and compare both guest and signed-in preferences. Test mobile topic menus, editor controls and addon placements.
Configure PWA, feeds, social links and outbound webhooks only where needed; verify the actual endpoint or browser result.
Choose private backup storage, create/verify a full backup and keep an off-host copy.
Test the ordinary member journey: register/login, profile image, topic/reply, mention, message, upload and download. Check what a guest cannot do.
Test staff moderation and a private-category direct link with a non-staff account.
Publish an introductory announcement and help topic; then invite members.

Before every update

Read the target handoff, take a verified full backup, use the exact-baseline updater and inspect the actual final archive version. After updating check both installed and database versions, then repeat the affected member/staff workflows.