SignoffFlow – Client Approval Workflow & Client Portal
SignoffFlow – Client Approval Workflow & Client Portal
Description
SignoffFlow is a client portal and approval workflow plugin for agencies, freelancers, and service teams.
Create a private portal workspace per client account where you can:
* Share project updates (timeline)
* Share files with protected downloads
* Send client requests/tasks and track approval outcomes
Portal access is restricted to WordPress users assigned to a client account, plus staff users with management capability.
This plugin only outputs front-end content on the portal page via the [cliapwo_portal] shortcode.
Use cases
- Collect client confirmations on deliverables and tasks
- Keep client communication out of email threads
- Share files securely with per-client access control
- Provide a branded agency client portal experience
Getting started
- Go to
SignoffFlow > Settings. - Use the
Quick setuppanel to create a sample portal page, or create a page manually and add[cliapwo_portal]. - Confirm that page is selected as the portal page in SignoffFlow settings.
- Create a client account in
SignoffFlow > Clientsand assign one or more WordPress portal users. - Add updates, files, and requests for that client account.
- Log in as an assigned portal user to view the portal and respond to requests.
Installation
- Upload the plugin folder to
/wp-content/plugins/or install it as a zip in WordPress. - Activate SignoffFlow through the WordPress Plugins screen.
- Go to
SignoffFlow > Settings. - Use the optional
Quick setuppanel to create a sample portal page automatically, or create your own page and add the[cliapwo_portal]shortcode. - Confirm the portal page is selected in SignoffFlow settings.
- Create a client account in
SignoffFlow > Clients. - Assign one or more WordPress portal users to that client account.
- Add updates, files, and requests for that client account.
Screenshots
Faq
Only WordPress users assigned to that client account, plus staff users with the cliapwo_manage_portal capability.
Clients receive protected download links that go through an access-checked endpoint. Files are stored in a dedicated cliapwo-private uploads subdirectory instead of standard public Media Library URLs, and the portal UI does not expose raw file paths.
Apache hardening files are created automatically for that directory. Nginx hosts may still need an equivalent deny rule added at the server level.
Yes. SignoffFlow can send request, update, and file notifications with wp_mail() to all WordPress users assigned to the related client account. Notification types can be toggled in SignoffFlow > Settings.
Yes, but local mail delivery depends on your environment. SignoffFlow records Email attempt entries in the Event Log for each notification. If WordPress cannot confirm delivery, SignoffFlow also shows a dismissible admin notice on its own screens so you can check the Event Log and review your mail transport.
The Notifications settings screen also includes an Email delivery help section with a simple test flow and recommendations for Mailpit, MailHog, SMTP, Postmark, and Mailtrap.
Yes. The portal uses a stable root wrapper (.cliapwo-portal), documented CSS variables, and a small set of filters for wrapper classes, section classes, and inline style variables.
For installed sites, see the Portal styling help note in SignoffFlow > Settings. Customizations should be added from a theme or site-specific plugin rather than by editing SignoffFlow directly.
Reviews
Changelog
1.1.0
- Added richer approval outcomes for requests: Approved, Changes requested, Rejected, and Blocked.
- Existing completed requests remain compatible and are shown as Approved for clearer approval workflow language.
- Tested with WordPress 7.0.
1.0.0
Initial release.





