Skip to content

Site Owner Handbook

Kanbanomy overviewPremiumGet Kanbanomy →

For the person who installs Kanbanomy, configures it, and keeps it running.

Getting Started covers installation and your first project. This handbook covers everything after that: taking the plugin to production, keeping mail and scheduled jobs healthy, backups, upgrades, privacy requests, and what happens if you ever delete the plugin.

Requirements: WordPress 7.0+, PHP 8.1+.


Work through this before you invite anyone. Each item links to the section that explains it.

# Check Where
1 License activated Kanbanomy to Settings to License
2 Default project visibility is what you intend Kanbanomy to Settings to General
3 Roles map to the right capabilities Kanbanomy to Settings to Access
4 Guest submissions deliberately on or off Kanbanomy to Settings to Access
5 Test email actually arrives Section 3
6 Scheduled jobs are registered and running Section 4
7 Front-end menu links exist Kanbanomy to Dashboard to Get started
8 Sample data removed if you loaded it Kanbanomy to Settings to General
9 Uninstall behaviour chosen consciously Section 7
10 A backup exists and you have tried restoring it Section 5

New projects default to members only. They are not served to anonymous visitors and not indexed by search engines. A members-only or private project returns a 404 to someone without access, deliberately identical to the response for a project that does not exist, so that the 404 does not confirm the project exists.

If you change the default to public in Settings to General, every project created afterwards is readable by anyone with the URL. Existing projects are not changed by flipping this setting.


Kanbanomy has three capabilities:

Capability Grants
manage_kanbanomy Full administration: create, edit, approve, configure
submit_kanbanomy Create and submit projects, work on tasks
view_kanbanomy Read-only access to projects they are a member of

Defaults out of the box:

Role Manage Submit View
Administrator yes yes yes
Editor yes yes yes
Author - yes yes
Subscriber - yes yes
Project Manager (kanbanomy_manager) yes yes yes
Member (kanbanomy_member) - yes yes
Client (kanbanomy_client) - - yes

Edit the matrix at Kanbanomy to Settings to Access. Two things to know:

  • You cannot lock yourself out. Administrator is always forced to all three capabilities, whatever the matrix says.
  • Subscribers can submit by default. If your site has open registration and you do not want every registered user creating projects, clear Submit for Subscriber before you go live.

The Client role can read and comment, never change work, and is how you share a project with a customer. Add them to the project as a viewer member; the front-end Hub becomes their portal. See the Member & Client Quick Start.


Kanbanomy sends mail through WordPress (wp_mail). It does not talk to a mail service directly, so if WordPress cannot send mail, neither can Kanbanomy.

Kanbanomy to Settings to Notifications controls:

  • A master email switch that turns off all outbound Kanbanomy email.
  • Per-event toggles. Each per-event toggle gates both the in-app notification and the email for that event. They are not independent channels: turning an event off silences it everywhere. The master switch is the only email-only control.
  • The from name used on Kanbanomy mail (email_from_name).

Check in this order:

  1. Is the master email switch on? Settings to Notifications.
  2. Is the specific event enabled? A disabled event produces neither an email nor a bell notification, so “no notification at all” points here rather than at mail delivery.
  3. Can WordPress send mail at all? Test with any SMTP or mail-log plugin. A default PHP mail() setup on shared hosting frequently fails silently.
  4. Is the recipient the person you expect? Some notifications deliberately suppress self-notification. You do not get an email for your own action. Someone who is both a task’s assignee and @mentioned in it receives one email, not two.
  5. Milestone reminders are the exception. Every other Kanbanomy email is sent during the request that triggers it, so a stalled job queue does not delay it. Milestone reminders are the one email driven by a scheduled job - if those specifically are missing, check scheduled jobs rather than mail delivery.

Use an SMTP plugin in production. It is the single highest-value reliability fix on a WordPress site.


Kanbanomy runs recurring background work: pruning the activity log, cleaning up read notifications, and sending milestone reminders.

Action Scheduler first, WP-Cron only as a fallback. If Action Scheduler is available, jobs are registered there under the group kanbanomy. WP-Cron is used only when Action Scheduler is absent. There is deliberately never more than one authoritative schedule for a hook.

Find them at Tools to Scheduled Actions, filtered to the kanbanomy group.

Hook Runs Does
kanbanomy_prune_activity_log Daily Deletes activity entries past the retention window
kanbanomy_cleanup_notifications Daily Deletes read notifications past the retention window
kanbanomy_milestone_reminders Daily Sends reminders for milestones coming due
kanbanomy_process_recurring Daily Creates the next occurrence of recurring tasks

If recurring tasks stop appearing, this is why - that feature depends entirely on the job queue running.

What Default Where Disable
Read notifications 30 days Settings to Notifications Set to 0
Activity log 90 days kanbanomy_activity_log_retention_days option -

Setting notification retention to 0 disables cleanup entirely and is a supported value. Unread notifications are never deleted by cleanup, at any retention value.

Activity-log retention has no settings-screen control; it is an option, adjustable in code via the kanbanomy_activity_log_retention_days filter. Milestone reminder lead time is likewise filterable via kanbanomy_milestone_reminder_days.

  1. Check Tools to Scheduled Actions first. If the actions are listed as pending with a past date, the queue is stalled rather than unscheduled.
  2. WP-Cron needs traffic. WordPress fires scheduled work on page loads. A site with no visitors runs no cron. On a low-traffic site, disable WP_CRON and drive it from a real system cron every 5 minutes.
  3. DISABLE_WP_CRON without a replacement is the most common cause of silently frozen jobs. If it is true in wp-config.php, confirm a server cron is actually calling wp-cron.php.
  4. A fatal in one job blocks the queue. Check the site’s error log.

Settings does not currently display when cleanup will next run. Tools to Scheduled Actions is the authoritative view.


Kanbanomy’s Import/Export is not a backup system. It is a data-transfer convenience. Use a real database backup for disaster recovery.

Kanbanomy stores everything in its own database tables (prefixed pflow_), not in posts. A backup plugin that only exports posts and pages will not capture any Kanbanomy data. Verify that your backup covers the full database, not just WordPress core tables.

At Kanbanomy to Import/Export:

Data type Export Import
Projects yes yes
Tasks yes yes
Milestones yes no
Time entries yes no

Export offers four data types. Import accepts two. You can export your milestones and time entries, but you cannot load them back through the plugin. Treat those exports as reporting output, not as a restore path.

Attachments are WordPress media library items. They are covered by your normal uploads backup, not by Kanbanomy’s export.

An untested backup is a hope, not a backup. Once, on a staging copy:

  1. Restore the database and the wp-content/uploads directory.
  2. Confirm project count, task count, and a project’s Board all match production.
  3. Open a task with an attachment and confirm the file loads.
  4. Confirm Tools to Scheduled Actions still lists the kanbanomy group.

Kanbanomy integrates with WordPress core’s privacy tools, so it answers data requests through the screens you already use: Tools to Export Personal Data and Tools to Erase Personal Data.

Both are keyed on email address, and both work for guest submitters as well as registered users.

Group Fields
Projects Title, status
Tasks Title, status
Comments Comment, date
Time entries Minutes, note, date
Submissions Name, email, status, date

Erasure treats personal records and shared records differently, on purpose. A team’s project history belongs to the workspace, not to one member, so cascading a deletion through it would destroy other people’s records.

Deleted outright - rows that exist only to describe that person:

  • Their project memberships
  • Their task assignments
  • Their notifications

Kept, with the personal link removed - shared records that stay readable but no longer identify anyone:

Record What is anonymised
Tasks Assignee and creator
Task comments Author
Activity log Actor
Time entries Member
Change requests Submitter and reviewer
Project templates, webhooks Creator
Projects Submitter, approver, and the stored submitter name and email
Submissions Submitter name, email, and IP address

So a task that member wrote stays in the project with its history intact; it simply no longer names them.

Projects and tasks are never deleted by an erasure request. If a departing member’s work must also go, delete those projects explicitly afterwards.

Guest submitters are covered. Someone who submitted through a public form has no user account, so their rows are matched by the stored email address instead of a user ID.

After erasing, Kanbanomy re-checks every table it touched. If any row still references that person, the request reports how many - so a partial erasure is visible rather than silent.

  • All data stays on your server. Kanbanomy makes no third-party calls with project data. The only outbound request is the license check to wbcomdesigns.com, which sends the license key and site URL, not project data.
  • Webhooks are your responsibility. If you configure outbound webhooks, you are sending project data to that endpoint. Declare it in your privacy policy.

Deactivating hides the interface and stops scheduled jobs. Every table, project, and file stays. Reactivating restores everything.

delete_data_on_uninstall at Settings to General defaults to off.

Setting Deleting the plugin
Off (default) All 25 tables and every project, task, and time entry are kept. Reinstalling picks up where you left off.
On All 25 tables are dropped, including the search index. Custom roles and capabilities are removed. This is irreversible.

The safe default means an accidental delete does not destroy your data, at the cost of leaving tables behind if you genuinely meant to remove everything.

Before you ever turn this on: take a database backup, and confirm you can restore it. There is no undo, and no confirmation step at deletion time - the decision is made here, possibly months earlier.

Attachments are media library items and are never deleted by uninstall, at either setting. Remove them separately if required.