Before you hand off the site, run through this checklist. Then reuse the same flow for every new client.
Handover checklist
[ ] Brand: Logo, brand name, and palette applied (Theme Manager + Appearance). Header and sidebar show the client’s identity.
[ ] Login: Custom login page (if used) and session/demo settings configured (Settings → Login). Tested in a private/incognito window.
[ ] Sidebar: Menu shows only relevant items, in a clear order (Menu Builder). No internal or developer-only items for the client.
[ ] Dashboard: Widgets are relevant and arranged (Unified Dashboard). No technical or internal-only widgets.
[ ] Role: Client has a dedicated role with the right permissions (User Management). No access to themes, plugins, or sensitive settings unless intended.
[ ] User: Client user created or updated, with a strong password or password-reset sent. Notifications (Settings → Notifications) tuned so they’re useful, not noisy.
[ ] Quick test: Log in as the client (or use a test user with the same role). Confirm they see only what they should and that branding is consistent.
Reusing this for every client
Template your choices: Note your default theme, palette, and menu structure so you can replicate them.
Reuse roles: If “Client” or “Editor” works for most sites, create it once and assign it per client.
Same checklist: Run this checklist on every handover so nothing is missed.
Docs and training: Point the client to FleekDash docs (e.g. Unified Dashboard, Comment Manager, In-Place Editor) if they need to learn specific features.
Related FleekDash docs
Theme Manager: Themes, palettes, and branding.
Settings Center: Appearance, Login, Notifications.
Menu Builder: Sidebar and menu.
User Management: Roles and permissions.
Unified Dashboard: Widgets and layout.
You’re done. Your client now has a dashboard that looks and feels like their product. And you have a repeatable white-label process for the next site.