Agency Handoff Guide

Admin UX Cleaner (AUC) can help you prepare a WordPress website for client handoff by simplifying the admin experience while keeping maintenance access available to your team.

This guide provides a practical workflow for agencies, freelancers, and developers preparing a completed WordPress website for everyday client use.

The goal is not to remove as much of WordPress as possible.

The goal is to give the client a clear workspace containing the tools they need while keeping technical and maintenance areas available to the people responsible for the website.

Caption: A simplified WordPress admin experience prepared for everyday client use.

Before You Start

Complete the main website setup before building the final AUC configuration.

Ideally, the website should already have:

Its production theme installed and configured.
Required plugins installed and activated.
Client user accounts created.
Appropriate WordPress roles assigned.
Main content workflows established.
Major development and configuration work completed.

AUC works best as part of the handoff process after the overall WordPress admin environment has become relatively stable.

Installing additional plugins later may introduce new menus, notices, Dashboard widgets, and Admin Bar items that require another AUC review.

1. Identify Who Will Maintain the Website

Start by deciding who should retain full administrative and AUC management access.

For example:

Agency Developer
└── Website and AUC maintenance

Agency Support
└── Ongoing client support

Client Administrator
└── Business administration

Content Editor
└── Content management

The people responsible for maintaining AUC should be clearly separated from users who receive the simplified admin experience.

Configure your Owner and trusted Managers before applying broader restrictions.

Caption: Configure trusted agency accounts before applying the client-facing AUC setup.

See Owner & Manager Access for details.

2. Define the Client Audience

Next, configure Audience.

Identify which roles and individual users should receive the AUC configuration.

For example:

Include
├── Client Administrator
└── Editor

Exclude
└── Agency Support

Keep Audience rules as simple as possible.

Role-based targeting works well when several users have the same responsibilities. Use individual user rules when a specific account needs an exception.

Caption: Define which client roles and users should receive the customized admin experience.

Before continuing, verify that your agency or maintenance accounts are not unintentionally included.

3. Identify the Client's Real Tasks

Before hiding anything, determine what the client actually needs to do.

Common client tasks may include:

Editing pages.
Publishing articles.
Uploading media.
Managing products or orders.
Reviewing form submissions.
Managing comments.
Viewing reports.
Updating specific business information.

Write down the important workflows before cleaning the interface.

For example:

Client needs:
✓ Pages
✓ Posts
✓ Media
✓ Forms
✓ WooCommerce Orders

Client does not normally need:
- Plugins
- Theme configuration
- Developer tools
- Cache configuration
- Backup settings

This gives you a practical basis for deciding what should remain visible.

4. Clean Up the Admin Menu

Use Menu Cleaner to remove navigation that is unnecessary for the client.

Keep the sections required for their normal work and hide technical areas they do not need to navigate regularly.

Caption: Keep the client's everyday tools visible while removing unnecessary admin navigation.

You may also rename menu labels when WordPress or plugin terminology is unnecessarily technical.

For example:

Posts → Articles

Do not hide something simply because the client probably will not use it.

If removing an item makes their workflow harder to understand, keep it.

5. Add Page Locks Selectively

Menu Cleaner simplifies navigation, but hidden menu items may still be reachable through direct URLs when WordPress permissions allow access.

Use Page Locks when the client should not be able to access a specific admin page.

Possible examples include selected:

Plugin management pages.
Theme configuration pages.
Maintenance tools.
Technical plugin settings.

Caption: Add Page Locks only where the client should not be able to access the page directly.

Do not attempt to lock every technical-looking WordPress page.

Add restrictions where there is a clear requirement and test each important workflow afterward.

6. Clean Up Notices

Once the main navigation is ready, review the admin experience for unnecessary notices.

Use Notice Cleaner to reduce messages that do not require client action.

Typical examples may include:

Upgrade promotions.
Review requests.
Optional setup reminders.
Integration suggestions.
Other maintenance-related notices.

Keep important information visible where appropriate.

A client dashboard with fewer notices makes meaningful warnings easier to notice when they appear.

7. Simplify the Dashboard

Review the WordPress Dashboard from the client's perspective.

Use Dashboard Cleaner to hide widgets that do not contribute to their everyday work.

For example, a content-focused client might need:

Keep
├── At a Glance
├── Activity
└── Form Submissions

while technical, promotional, or maintenance widgets can be hidden.

Caption: Keep useful Dashboard information while removing widgets that are irrelevant to the client's work.

The goal is a focused Dashboard, not an empty one.

8. Clean Up the Admin Bar

Use Admin Bar Cleaner to remove unnecessary toolbar shortcuts.

Technical shortcuts for caching, backups, SEO configuration, or maintenance may be useful to your agency but irrelevant to the client.

Keep navigation, account, and content shortcuts that still provide value.

Review the Admin Bar both inside WordPress and on the frontend when applicable.

9. Preview the Client Experience

Once the main configuration is complete, use Preview to inspect the experience for each important client role or user.

Caption: Preview the complete AUC configuration from the client's perspective before handoff.

Check:

Is the admin menu understandable?
Can the client find their everyday tools?
Are unnecessary technical areas removed?
Are important notices still visible?
Is the Dashboard useful?
Is the Admin Bar clear?
Do Page Locks affect only the intended pages?

Do not evaluate the interface from a developer's perspective.

Ask instead:

If I were the client and logged in tomorrow without assistance, could I complete my normal work?

10. Test With a Real Client Account

Preview is useful during configuration, but final testing should be performed using an appropriate WordPress user account.

Test the workflows the client will use regularly.

For example:

Login
  ↓
Edit a page
  ↓
Upload an image
  ↓
Publish an article
  ↓
Review a form submission
  ↓
Return to Dashboard

If the client manages WooCommerce or another application inside WordPress, test those workflows as well.

Pay special attention to workflows involving Page Locks or third-party plugins.

11. Test Direct Access to Locked Pages

For each important Page Lock, test the page using its direct URL.

Confirm that:

The intended client account cannot access the locked page.
Redirect behavior works correctly.
Related client workflows still function.
Your trusted administrative account retains access.

Do this before handing over login credentials or notifying the client that the website is ready.

12. Verify Recovery Access

Before handoff, confirm that your safety mechanisms are ready.

Check that:

The correct Owner is configured.
Required Managers have access.
Recovery information is stored securely.
You know how to enable Safe Mode if necessary.
Your agency retains appropriate hosting or server access when that is part of your maintenance arrangement.

Caption: Verify administrative and recovery access before handing the website over to the client.

Do not store the only copy of your Recovery URL somewhere that depends on access to the WordPress admin area.

13. Create a Final Backup

Once the client configuration has been tested and approved, create an AUC backup.

This becomes your known working handoff configuration.

For example:

AUC Backup
└── Client handoff - final configuration

If future changes create an unexpected problem, this backup provides a useful recovery point.

Also maintain a normal WordPress backup using your existing website backup process.

Remember that an AUC backup contains AUC configuration, not the complete website.

14. Export a Reusable Starting Point

If the configuration represents a setup your agency commonly uses, consider exporting it.

For example, you might maintain internal starting configurations such as:

Content Website
WooCommerce Website
Corporate Website
Simple Client Handoff

The exported configuration can provide a starting point for future projects.

Always review imported configurations for the destination website rather than applying them blindly.

15. Explain the Simplified Experience to the Client

A good handoff should not leave the client wondering why their WordPress dashboard looks different from tutorials they find online.

Briefly explain that their admin interface has been simplified around the tasks they normally perform.

For example:

Your WordPress admin area has been simplified to keep the tools you use regularly easy to find. Some technical and maintenance areas are managed separately by the website administrator.

You do not need to explain every AUC setting.

Focus on what the client can do and where they should go when they need help.

After Handoff

The AUC configuration should be reviewed when the website changes significantly.

Useful times to review it include:

After installing a major new plugin.
After removing or replacing plugins.
After changing the theme.
When the client's responsibilities change.
When new users or roles are introduced.
When a plugin adds new admin menus or Dashboard widgets.
When the client reports difficulty finding or accessing something.

A client handoff configuration is not something you need to constantly maintain, but it should evolve when the website or the client's workflow changes.

Handoff Checklist

Before considering the AUC setup complete, verify:

Owner is correctly configured.
Trusted Managers are correctly configured.
Client Audience is correct.
Required admin menus remain available.
Unnecessary menu items are cleaned up.
Page Locks are used only where needed.
Direct URL access to important locked pages has been tested.
Important notices remain visible.
Dashboard widgets are appropriate for the client.
Admin Bar shortcuts are appropriate.
Client experience has been previewed.
Important workflows have been tested with a real user account.
Recovery information is stored securely.
Safe Mode procedure is understood.
Final AUC configuration has been backed up.

A Practical Handoff Workflow

The complete process can be summarized as:

Configure Owner & Managers
        ↓
Define Client Audience
        ↓
Identify Client Tasks
        ↓
Clean Admin Menu
        ↓
Add Necessary Page Locks
        ↓
Clean Notices
        ↓
Simplify Dashboard
        ↓
Clean Admin Bar
        ↓
Preview
        ↓
Test With Real User
        ↓
Verify Recovery Access
        ↓
Create Final Backup
        ↓
Hand Off to Client

You do not need to use every AUC feature on every website.

A successful handoff is one where the client can comfortably complete their work while the people responsible for maintaining the website retain the access they need.

Next Step

For a shorter reusable setup process, continue with Recommended Setup.

If you encounter unexpected behavior while preparing a client website, see Troubleshooting.