When a developer hands off a WordPress site to a non-technical client, the standard admin interface presents features the client should not touch (plugin management, theme switching, code editors, core update controls) alongside nothing to orient them toward what they actually need to do. There is no built-in structure for that transition.

Client Handoff addresses this through two mechanisms: a first-run setup flow that walks the developer through configuring the site for a client, and a runtime enforcement layer that limits what designated client roles can see and do. Configuration is stored as a single option and can be exported as JSON for reuse across multiple sites.

What it does

Replaces the WordPress dashboard for designated client roles with a configurable widget containing a welcome message, quick links, developer contact information, and site status.
Hides admin menus, admin bar entries, and update nags for client roles without modifying their underlying role capabilities in the database.
Blocks deactivation and deletion of plugins the developer marks as protected, intercepting four distinct request shapes (single deactivate, bulk deactivate, single delete, bulk delete).
Filters eleven codebase-altering capabilities at runtime (including install_plugins, activate_plugins, edit_plugins, switch_themes, update_core, and six others) using WordPress’s user_has_cap filter. No changes are written to the role definitions in the database.
Provides a four-step setup flow (Roles, Dashboard, Restrictions, Activate) that guides the developer through full configuration before handoff mode is enabled.
Exports and imports the full configuration as a JSON file for multi-site deployment.

What it does NOT do

Does not modify role capabilities or role definitions in the database. All capability filtering is runtime-only and disappears on deactivation.
Does not phone home, send telemetry, or make external API calls of any kind.
Does not include a premium tier, upsell prompts, or in-admin advertising.
Does not support network-wide activation on multisite in this version. Single-site activation on a multisite network is supported; network-wide activation is detected and no-ops with an admin notice.

Comparison with BrenWP Client Safe Mode

BrenWP Client Safe Mode is the established option in this space and focuses on depth of restriction: granular control over what client roles can access. Client Handoff focuses on the workflow layer above restrictions: the guided setup experience, the client-facing dashboard widget, and the JSON export/import for deploying the same configuration across multiple sites. The two plugins address different problems and can coexist if a developer wants both the workflow structure of Client Handoff and the restriction depth of Client Safe Mode.

Client Handoff is for developers and agencies who hand off WordPress sites to non-technical clients and need a structured, repeatable process for that transition.