Skip to content

Share a project with a client and they follow it from the Hub: their projects, what is open and late, and the next milestone. They never see WordPress, your team’s internal work, or the budget unless you choose to show it.

  1. Open the project’s Team tab and invite the client by email, or add an existing user, with the project role Viewer.
  2. The client gets one email: “{your site} shared “{project}” with you”, with one link. A new account chooses a password first, then lands on the Hub.

A client who already has an account gets the same short email with a link to the project.

Place What the client gets
Hub A greeting, their projects (paged 12 at a time) with status, progress, dates, open and late counts and the next milestone, plus upcoming and late milestones. No task stats, quick actions, My Tasks, activity, team avatars or calendar feeds.
Project page Overview, Tasks, Gantt, Calendar, Milestones and Discussions tabs. Tasks show title, status, due date, priority and milestone. Discussions show only the threads your team shared with clients; a client replies there but cannot start a thread.
Task panel Title, status, dates, priority, milestone, description, checklist and comments. The client can post comments, edit or delete their own, and approve a task or ask for changes when your team asks. No team-only comments, watchers, logged time, custom fields or activity.
Notifications Only about tasks and discussions they can see: comments, replies, @mentions and approval requests included. Nothing about internal tasks, team-only comments or team-only discussions.
Hub A “Waiting for your approval” list of the tasks your team asked them to approve.

What stays with your team: the board, the Activity and Team tabs, team-only discussions, watchers, logged time, and every task marked Internal with its comments and files.

A client can comment on any task they can see. A client cannot move or edit a task. Besides commenting, the only thing a client can do is answer an approval request (see below).

  • A client edits or deletes only their own comments.
  • A client comment emails the task’s assignees and watchers, like any comment.
  • In a comment a client can @mention people on your team, never another client.
  • Your team can @mention a client only on a task that is not Internal. On an Internal task the client is not in the @mention list, and a typed @name sends them nothing.
  • An Internal task, its comments included, answers a client with “Task not found”.

Your team can tick Team only under the comment box to keep one comment away from clients. A team-only comment carries a “Team only” chip for your team. Clients never see it anywhere: the task panel, comment counts, the REST API, notifications, emails or the digest. Clients cannot post one, and a reply to a team-only comment is team-only too.

  1. Open the task and tick Needs client approval. The box appears once the project has at least one client. On an Internal task the switch is off, because clients cannot see the task.
  2. Every client on the project gets an email and a bell notice, “Your approval is needed”, with a button to the task. The task shows a “Waiting for client” chip in your lists and on the Board and a “Your approval is needed” chip and banner for the client.
  3. The client clicks Approve, or Request changes and writes what should change. A change request is posted as a comment on the task.
  4. The person who asked gets an email and a bell notice saying who answered. The task shows “Approved by …” or “Changes requested by …”, and the project activity records it.

Rules:

  • Any client on the project can answer. The first answer counts; a second client sees “Already answered by …”.
  • Approving does not change the task’s status. Move it yourself when you are ready.
  • To ask again after making changes, tick Needs client approval again. Every round stays in the activity history. Untick it to withdraw a request nobody has answered yet.
  • Pending approvals show in wp-admin Approvals, and as “Waiting for your approval” in a client’s daily digest when client digests are on.
  • Each person can switch approval notices off in Hub > Notifications, under “Approvals on tasks”.

A client never sees wp-admin. Opening /wp-admin/ sends them to the Hub. They can still open their profile to change their name, email or password, and that page has a “Back to your projects” link. On the front end they get no WordPress admin bar.

A client who also has an editing role (for example Editor) is treated as a regular WordPress user and keeps wp-admin.

Tasks are visible to clients unless you mark them Internal. To mark one:

  • In the task panel, under Clients, tick “Internal (hidden from clients)”.
  • In wp-admin Tasks, select tasks and use the bulk action “Mark: Internal (hidden from clients)” (or “Mark: Visible to clients”).
  • In a CSV import, map a column to “Internal (hidden from clients)” (yes / no).

Anyone who can edit the task can set the flag; clients cannot. Sub-tasks follow their parent. Your team sees an Internal badge on these tasks everywhere.

An internal task is hidden from clients on every screen: project tabs, Hub counts, late work, search, calendar feeds, blocks, notifications and emails. Existing tasks stay visible after the update.

The budget is hidden from clients by default. Priority is always visible.

To show it on one project, open the project and tick Client can see: Budget:

  • wp-admin: Projects, edit the project, Settings tab.
  • Front end: the project’s edit form (project owner or manager).

Only the project owner or a Kanbanomy manager can change this switch.

  • kanbanomy_portal_roles (filter, string[]): roles treated as portal users. Default: the Kanbanomy Client role.
  • kanbanomy_portal_hide_admin_bar (filter, bool): return false to give portal users the admin bar back.
  • REST: PATCH /kanbanomy/v1/tasks/{id} accepts is_internal (boolean). PATCH /kanbanomy/v1/projects/{id} accepts client_can_see_budget (boolean, owner or manager). Project responses carry a read-only can object (write, manage, see_budget). Task responses carry can.comment, can.approve and an approval object (state, label, by_name, at_label, can_request, can_answer). POST /kanbanomy/v1/tasks/{id}/approval/request, /approval/withdraw (team) and /approval/approve, /approval/request-changes with comment (client) answer 409 when the request was already answered. POST /task-comments accepts team_only (team only). GET /kanbanomy/v1/projects/{id}/members?task_id={task} returns the people who may be @mentioned on that task.
  • Actions: kanbanomy_task_approval_requested( $task_id, $task, $actor_id ), kanbanomy_task_approval_withdrawn( $task_id, $task, $actor_id ), kanbanomy_task_approval_answered( $task_id, $task, $actor_id, $answer, $comment_id ) where $answer is approved or changes. Webhook events task_approval_requested and task_approval_answered.
  • Project meta sent to PATCH /projects/{id} is merged into the stored meta. To delete a key, send it as null.