Getting Started
Portal Setup
Forms & Booking
Sessions & Projects
Quotes & Documents
Communication & Automation
Galleries & Delivery
Billing & Reporting
Troubleshooting
Installing Mankai CRM
Install the plugin, activate it, and get to the Portal Foundation wizard without guessing where anything lives.
Mankai installs like a normal WordPress plugin, but the first-run flow matters because the plugin also creates and manages portal pages for you. If you install it correctly once, the rest of setup is much easier.
Before You Install
- Use WordPress 6.0 or newer.
- Use PHP 7.4 or newer. PHP 8.x is better.
- Make sure you are logged in as an administrator.
- Have your license key ready if your copy requires activation.
Upload and Activate
- Go to Plugins > Add New > Upload Plugin.
- Select the Mankai zip file exactly as downloaded. Do not unzip it first.
- Click Install Now, then Activate.
After activation, you should see the Mankai CRM admin area. On a fresh install, Mankai also marks its managed routes for setup and rewrite syncing, so the first page load after activation may do a little more work than normal.
What Happens on First Activation
Mankai does not just add a menu. It also boots its domain modules, registers its post types, and prepares managed portal pages for routes like dashboard, billing, documents, quotes, and in photographer mode, galleries and deliverables.
If the setup wizard has not been completed yet, Mankai redirects its admin pages back to Portal Foundation until the initial configuration is done. That is expected.
First Screen to Open
Open Mankai CRM > Portal Foundation. This is the real starting point. From there you will:
- Choose your portal mode
- Set your base portal slug
- Review enabled features
- Configure branding, menu items, and shell settings
- Set booking and gift card slugs if you use them
Quick Verification Checklist
- The Mankai CRM menu appears in wp-admin.
- You can open Portal Foundation without a fatal error.
- Your portal routes start generating pages after setup.
- No white screen appears on plugin pages.
If any of those fail, skip ahead to the troubleshooting doc instead of forcing it.
Was this helpful? If something is missing or wrong, I want to know.
Send feedback