Changelog

Stay up to date with the latest improvements and updates to Client Cove. We release updates regularly to improve your experience.

October 2026

v4.218.0 — October 26, 2026

New: a Today card for your dashboard

• Your Today list, on the dashboard: a new Today card shows how much is due today and overdue, the top things to do first with the reason for each (such as an amount and how many days overdue), a line to Actions when drafts or requests are waiting for you, and how much is due tomorrow. Open Today takes you to the full page. It uses the same list as the Today page, so the two always agree.
• Choose how many items it shows: from 3 to 8, five by default. Add it from the dashboard builder by picking Today.
• New sites: the admin and staff dashboards made by the setup wizard now start with the Today card where the "Go to" card used to be. Use the menu or Cmd+K to jump to a page.
• Existing sites: if your admin or staff dashboard still has the "Go to" card exactly as the setup wizard made it, it is replaced by the Today card once, in the same place and size. If you changed that card in any way, such as its title, buttons, links, order or style, it is left as it is.
• Unchanged: client dashboards keep their "Go to" card, cards you built yourself are never touched, and the Quick Actions card is still available in the dashboard builder.
• For your team only: clients never see the Today card.

v4.217.0 — October 26, 2026

New: ask the assistant what needs you today

• The same answer as the Today page: ask the assistant "What needs my attention today?", "What should I do now?" or "What are my priorities today?" and it reads your Today list: what is overdue, what is due today and the tickets waiting for your reply, leading with the suggested things to do first. It no longer answers from your upcoming tasks alone, so tickets, invoices, routines, contracts and file transfers are included, and chat and the Today page agree.
• Read only: the assistant tells you what is on the list; to pin, remind or dismiss an item, use the buttons on the Today page. Its answer ends with an Open Today suggestion.
• "What's due this week?" is unchanged: questions about the coming days or weeks, or about one client's deadlines, still list upcoming deadlines as before.
• The "What needs my attention today?" starter in the assistant now uses your Today list.
• For your team only: clients never get this answer or the Open Today suggestion. Connected AI assistants (such as Claude Desktop) can read your own Today list too, once the connector update rolls out; a connected agent cannot.

Improved

• Today page layout: the tabs and list now sit in a card, like the Calendar page, so they have room on wide screens.

v4.216.0 — October 26, 2026

New: Today, one place for what to do now

• A Today page for your team (staff only): Today (at /today/) lists what is overdue, what is due today and the tickets waiting for your reply, across tasks, routines, tickets, projects, invoices, estimates, contracts and file transfers, with 3–5 suggested things to focus on first. It only shows work you can already see elsewhere in the portal. It works with no setup: nobody has to turn anything on, and it updates when you come back to the browser tab.
• A button on every item: open it, pin it or set its priority, dismiss it (it comes back if its date changes), or send a reminder. A reminder that would reach a client is a draft in Actions that you publish yourself; nothing is sent to a client from Today.
• Briefs is now part of Today: Weekly Breakdown and Upcoming Due are tabs on the same page and work exactly as before, including their schedules and emails. Old Briefs links keep working and open the same page.
• Also on Today: a link to Actions when drafts or requests are waiting there; your meetings for the day from your connected calendar (read only: just the time, title, location and join link); and how many things are due tomorrow. Meetings are never counted as work to do.
• File transfers you sent or requested now show on Today, Weekly Breakdown and Upcoming Due on the day they expire, while they are still active. Once a transfer has expired it drops off the list. Only transfers you created are listed.
• Getting there: Today is the first item in the account menu for everyone on your team, so it is in the quick search too. On new installs, and on menus switched to the recommended layout in Settings → Menus, it is also the first page under Work. Existing menus are not changed; add Today in Settings → Menus if you want it there.
• Linked from the places that answered "what now?" before: Actions ("Everything due today"), the Today tab in My Tasks, the Calendar ("Today list") and the Your Week dashboard card ("Open Today"). Those pages keep their own jobs: Actions is still where drafts and approvals wait, My Tasks is still your task list, and the Calendar is still for planning across days.
• Clients never see Today, its links or its menu item.

v4.215.0 — October 26, 2026

New: track time and hour budgets

• Log time on tasks: in My Tasks (the expanded task and the side panel), Log time records the hours, the day the work happened (today by default, never a future date) and an optional note, credited to the person logging it. Each task lists its entries; you can change or remove your own, and task managers can change anyone's. A task's total is always the sum of its entries. Time already on your tasks is carried over automatically when you update, as one entry per task dated on the task's completion date (or its last change), so no totals change. Only staff log time; clients cannot add hours.
• An Hours tab on each client (staff only): see Budget, Used, Remaining and % used for the current period, any of the previous 11, or a custom date range, then the hours by team member and by task, with every entry and its note. All time on the client's tasks counts, billable or not; billable tasks are marked. Clients never see this tab or any budget.
• Budgets come from your included hours: the budget is the client's "Hours per Month" included hours, set on the client's Billing tab or on their retainer product. If you already use included hours there is nothing to set up. Clients without included hours still get the tab, just without a budget.
• Periods: a client with a retainer subscription follows its billing cycle; everyone else runs on calendar months. On the Hours tab, Change period gives a client its own period: every so many days, monthly, quarterly or yearly, starting from a date you choose (for example the 15th to the 14th). The monthly budget scales to the period's length, so a quarter gets three months' worth; a retainer's budget stays as its product sets it, per billing cycle. Only people who can edit the client's billing settings can change the period. Nothing changes on upgrade until someone sets one.
• Hours left, where you log time: staff see a "hours left this period" chip for the task's client in My Tasks.
• One number everywhere: the included-hours usage shown on tickets and used by the assistant now comes from these time entries, so it matches the Hours tab.

New: invoice tracked time

• From the Hours tab: Create invoice lists the period's uninvoiced tasks with their hours and amount; billable tasks start ticked. It makes a draft invoice with one line per task (a task worked at different rates gets one line per rate) that you can edit before sending. Nothing is sent.
• From New Invoice: when you pick a client who has uninvoiced time, it asks "Create this invoice from tracked tasks?" Choose tasks fills in the line items, from all uninvoiced time or from one period, and saving marks that time as invoiced. If you remove any of a task's lines before saving, that task's time stays uninvoiced. An invoice built from tracked tasks cannot be recurring.
• Rates: hours are priced at the client's rate card (its hourly "Standard" rate, otherwise its first hourly rate), then the team member's billable rate, then the client's default rate, then your account's default rate card. Tasks with no rate show "No rate" and go on the invoice at $0 only if you tick them. The assistant's "invoice from billable tasks" now uses the same rates.
• Never billed twice: invoiced time is locked and cannot be edited or deleted. Permanently deleting the invoice makes that time uninvoiced again; moving the invoice to the trash, or restoring it, does not. Time invoiced from the Hours tab, from New Invoice or by the assistant is never offered again.

Fixes

• Tagging a task with a client: a task can only be tagged with a real client that the person works with: staff who manage clients or tasks, or people assigned to that client. Technicians and contractors who are not assigned to a client can no longer tag a task with it, including when creating a task from a ticket, a routine or the calendar. Clients can only use their own client.
• Only staff set a task's time: clients can no longer change the time recorded on a task.

v4.214.0 — October 25, 2026

New

• See which planning pages your team uses: the portal now counts how often staff open Actions, Briefs, My Tasks and the Calendar, and how they got there: from another of those pages, from the Your Week card, from elsewhere in the portal, or directly. It also counts how often the Your Week card is shown on a dashboard. Only staff visits are counted, never clients and never while you are viewing the portal as someone else. The counts cover the last 90 days and stay on your own site; nothing is sent to ClientCove. Site administrators with command-line access can read them with wp cove-surface-visits, or start a fresh count with wp cove-surface-visits reset.

v4.213.1 — October 25, 2026

Fixes

• On the Tickets page, the "Unclosed" tab is now called "Open".
• The number beside each Tickets tab now matches the tickets that tab lists. Before, Unanswered could show 0 while listing open tickets, and Open and Unassigned counted closed tickets too. The tab counts at the top of a ticket's page now match as well, and count only the tickets that person can see.
• On the Revenue page, Overdue now appears inside the Outstanding card, so the two no longer show the same total side by side. The Collected chart now shows each month's total above its bar, so a small month next to a big one is still readable.
• On tablets, and on laptops with the sidebar open, dashboard widgets now fill the full width instead of leaving an empty column on the right.

v4.213.0 — October 25, 2026

Easier to find your way around

• A menu organised into hubs: the staff menu can now be grouped into Dashboard plus five hubs: Work (tickets, tasks, projects, calendar, crew dashboard), Clients (clients, locations, assets, dashboards), Financial (estimates, invoices, orders, products, revenue, agreements, contracts), Files & forms (resources, transfers, intake forms, knowledge base) and Automate (actions, agents, automations). New portals start with this layout. Your current menu does not change on upgrade: to switch, go to Settings → Menus, review the preview under "Recommended layout" and choose Use this layout. Your current menu is saved, and Restore my previous menu puts it back.
• Financial pages follow each person's access: the menu now hides estimates, invoices, orders and revenue from team members who cannot use them, and marks pages they can only view with an eye icon. The Users and Agents links and the Actions page also show only for people who can open them.
• Hubs in the chat view: while the sidebar shows the chat, a row of hub icons sits under the page name. Each one opens that hub's pages, so the menu stays one click away.
• Cmd+K (Ctrl+K) goes to pages and creates things: as you type, matching pages from your menu appear right away, along with actions such as "New invoice", "New ticket" or "New task", above the search results. Choosing a "New …" action opens that page with its create form already open. Clients see "New ticket" only. Search needs AI features turned on, as before.
• One assistant at a time: when the sidebar is showing the chat, the dashboard's own assistant card is hidden, so you no longer see two copies of the same assistant. It comes back when you switch the sidebar to the menu or minimise it.

v4.212.2 — October 25, 2026

Fixes

• The Clients page now counts open tickets for each client and labels the count "Open Tickets", so it matches the Tickets count on that client's company card. It used to count closed tickets too.
• On a project page, a client who can't see the project's activity no longer gets a background error every few seconds. The page stops asking for the activity log once it has been refused.

v4.212.1 — October 25, 2026

Fixes

• The Projects count on a client's company card and on the Clients page no longer includes archived projects, so it matches the Projects page.
• The Resources count on a client's company card now counts only files that person can open. Files in your team's private Workbench folder were being counted for clients.
• Assets and Locations counts on the company card and the Clients page now include every asset and location assigned to the client. Some were being left out.
• The agent summary on the Actions page now shows what is still open, not the counts from when the agent last ran, and adds how many items were finished since, for example "8 overdue · 3 done since". The line is now a link to the full list, and the section counts on the Briefs page match it.

v4.212.0 — October 24, 2026

Your clients get their own views

• Tickets: clients now see a page made for them instead of your team's ticket table. Requests that need their reply are listed first under "Waiting on you", then "Open requests" your team is working on, with a New request button at the top and resolved requests one click away. Your team's Tickets page is unchanged.
• Projects: a client's project page now shows a progress tracker above the tabs: the current stage, the next milestone, and the one thing needed from them. When a stage is waiting on their sign-off, they can approve it or request changes right there. Their projects list shows each project's progress and next step instead of a table. Projects without stages, or that don't share Process or Status with clients, look the same as before.
• Client home: the To-Do Center lists everything a client needs to do in one place, and now also includes tickets waiting on their reply and project sign-offs waiting on them. This changes on upgrade: wherever a client's dashboard has an Action Center, clients now see the To-Do Center list in that same spot, with the same title and the same filters. Your team still sees the Action Center. Nothing else on your dashboards moves unless you choose "Lead with To-Do Center" in Manage Dashboards, which puts the list right after the welcome banner.
• Recent Items now shows each record's name (for example "T-1000") instead of its number.

Faster

• Project pages appear about a second and a half sooner. The loading screen no longer waits for every image on the page.

Fixes

• A non-staff user with no client assigned, such as a contractor not yet given any clients, could see every ticket on the Tickets page and in the Action Center. They now see none until a client is assigned. Users with clients assigned see the same tickets as before.
• Ticket filters that matched nothing showed every ticket instead of an empty list.

v4.211.1 — October 24, 2026

Fixes

• The Tickets count on a client's dashboard now includes every open ticket for that client. Tickets opened through the assistant, an embedded support form, the calendar or a PIN page were left out, so some clients saw 0 while their Tickets page listed open tickets.
• Ticket counts on the Clients page now match each client's Tickets page.
• Agent lists (Upcoming Due, Weekly Breakdown) now say "awaiting your reply" for tickets that need a response from your team. They used to say "waiting on you", which on the Actions page means drafts and approvals waiting for you to publish.

v4.211.0 — October 22, 2026

Clients hear about tickets opened for them

• When your team, the assistant, a board card or a staff email opens a ticket for a client, that client's active portal users are now added to the ticket's subscribers. They get the new-ticket email and every later reply and status email. Staff can remove anyone from the subscriber list. This does not happen for tickets a client opens themselves, for tickets an autonomous agent opens, or for your own internal client.
• Turning a board card into a ticket now sends the same emails and Slack post as any other new ticket.
• Slack now posts status changes and replies however they happen: the ticket page, the assistant, agent drafts, connected AI tools and email replies. A reply that also changes the status posts both.
• Tickets from the public support page now get a ticket number, Open status and Medium priority, appear in the tickets list, and notify staff and Slack. The requester gets a confirmation with the ticket number only, never the text they submitted, because anyone can type any address into that form. Staff replies are not emailed to public requesters, who have no account.
• The "Request received" confirmation now goes only to clients who open their own ticket, not to staff opening one on a client's behalf. Its subject now starts with the ticket number so replies stay in the same thread.
• Emailed tickets get a confirmation with a proper From, Reply-To and ticket-number subject. Before this, some mail providers rejected it.
• Custom ticket statuses, and Reopened, can now be picked from the ticket sidebar, the reply box and the mobile status menu.
• The Reopen Window column now shows your real setting. A setting of 0 stays 0 and shows "Staff only"; before, it always showed 7 days.

Invoices: quick date filters

• The invoices list Date filter now offers All dates, This month and Last month, then Date range for anything else. Choosing Date range after a month starts the From and To fields on that month so you can adjust it. All dates is the default.

Email footers

• Email footers now show the copyright year instead of today's full date. Existing templates are fixed when the email is sent, so nothing needs re-saving, and a date placed anywhere else in a template still prints in full.

v4.210.0 — October 19, 2026

The assistant builds automations and forms on every AI setup

• Automations and intake forms can now be built and changed through the assistant whichever AI setup your portal uses, including WordPress AI connectors and managed AI. Before this, some setups could not send the assistant the detail an automation's steps or a form's questions need, and the request failed.
• On those setups the assistant can now look something up and act on it in one reply. "Move the Monday digest to 7am" finds the automation by its name and then prepares the change for your YES, instead of asking you which one you meant.
• Your YES is still required for every change, and the assistant still makes at most one change per reply. Text written by other people (ticket messages, emails, form answers) is treated as information only; it can never make the assistant prepare an action on its own.
• Nothing changes on upgrade, and nothing changes for portals already using their own AI keys beyond small accuracy improvements.

v4.209.0 — October 19, 2026

The assistant can read and change your intake forms

• Ask "which intake forms do we have?" or "what does the onboarding form ask?" and the assistant lists your forms and the questions on one: type, whether it is required, its options and its show/hide rules.
• Ask for changes in plain words: "add a phone question to the onboarding form", "make Budget required", "only show Budget when they pick Website", "remove the fax question", "add a Files step". You see each change listed and confirm with YES before anything is saved.
• Everything you did not ask to change stays exactly as it was, including settings the assistant does not edit. Forms keep their version history, so submissions already made still show the questions they answered, and the YES prompt tells you when a form already has submissions.
• Show/hide rules and calculated fields stay pointed at the right questions when a question is removed. If something else depends on that question (the form's automations, alerts, after-submit options, a dashboard widget or a step jump), the assistant does not remove it and links you to the form builder instead, which updates those connections for you.
• When the assistant creates a new form it can now use the builder's other question types too: email, phone, number, currency, web address, checkboxes, dropdown, rating, scale, NPS, consent, date, time and signature, with their settings saved.
• If someone edits the same form in the builder between the assistant's question and your YES, nothing is saved and the assistant asks you to look again.
• What has not changed: only administrators and editors can have the assistant change forms, the same people who can use the form builder. Moving questions and removing a whole step are still done in the builder. A new form title still changes the form's link, and the YES prompt warns you. Nothing changes on upgrade.

v4.208.0 — October 19, 2026

The assistant builds automations without guessing

• Ask the assistant "what can trigger an automation?" or "what does the invoice paid event carry?" and it answers from the live list: the triggers and schedules you can use, which events are switched on (and which are not available yet), the fields each one carries, the conditions it understands, and the steps it can add.
• Before it drafts or saves an automation, the assistant now checks the whole thing and fixes every problem it finds in one go — an event that does not exist, a schedule written wrong, a step that does not take that input. Before this, some of those mistakes saved fine and the automation simply never ran.
• Small changes are now small. "Move the Monday digest to 8am", "change the wording of the second step" or "only do this for urgent tickets" changes just that part; the rest of the automation is left exactly as it was. You still see each change listed before you confirm with YES.
• If someone edits the same automation in the Automations screen between the assistant's question and your YES, nothing is saved and the assistant asks you to look again, so a stale change can never land on the wrong step.
• Changing an automation that is on applies straight away (the YES prompt says so); if you moved its schedule, the next run moves with it.
• What has not changed: the assistant still never turns an automation on or off — you do that in Automations. Automations the assistant drafts still need a person to publish them, and they are created switched off. Editing in the Automations screen works exactly as before.

v4.207.1 — October 19, 2026

Intakes menu fix

Fixed

• The Intakes item under the portal's wp-admin menu now appears when Intake Forms is turned on in Core Features. Before this, it never showed, even with the feature on. Intake forms themselves and the Intake Manager in the portal were not affected.

v4.207.0 — October 19, 2026

New assistant suggestions from ClientCove

Fresh suggestions as features ship

• The rotating suggestions under the assistant's greeting can now include new ones that ClientCove publishes, often for features that just shipped. A newly published suggestion shows ahead of the others for its first couple of weeks.
• These suggestions only ask the assistant a question or start a draft. They never send, delete or change anything on their own, and anything the assistant would change still asks for confirmation first.
• They follow the same rules as the built-in set: a suggestion only appears if its feature is turned on and the person can use it, and clients only ever see client suggestions.

How it works

• Your site checks for new suggestions in the background, at most every 30 minutes, after a page has finished sending. Pages never wait on it.
• The check sends only your theme version. No user, client or portal data leaves your site.
• If the check fails, the assistant keeps using the last suggestions it received and the built-in set.

Defaults

• Include suggestions from ClientCove is on by default. Turn it off under Settings → Assistant Widget, next to Starter chips. With it off, your site never checks for them.
• The setting only applies when Starter chips is set to Rotate suggestions. Your pinned prompts still show first.

v4.206.0 — October 19, 2026

The assistant's suggested prompts now rotate

Fresh suggestions every time you open the assistant

• The prompts under the assistant's greeting now change from visit to visit instead of showing the same three or four every time.
• They come from a larger built-in set for each role (admins, staff, clients, and signed-out visitors), and the order changes daily for each person.
• The assistant only suggests features you have turned on and tools the person can use. If Invoices is off, nobody is offered an invoice question.
• Agent reminders, such as "things waiting from my agents", still show first.

Your own prompts stay put

• Prompts you wrote under Settings → AI → Assistant Widget are now called Pinned prompts. They always show first, and the rotating suggestions fill the rest.
• If you never changed the prompts that shipped with ClientCove, nothing is pinned and everything rotates.
• To go back to a fixed list, set Starter chips to "Show only my prompts". With no prompts of your own, each role then gets the original standard set.

Defaults

• Starter chips is set to "Rotate suggestions" on every site after this update. Nothing else changes.
• Suggestions are built into the theme. This update does not fetch anything from outside your site.

v4.205.1 — October 19, 2026

Fixes for agents and the summary email

• The summary email now goes to each person at most once a day. In 4.205.0 a late-running hourly check could send a client the same summary twice in one day.
• When someone who manages users opens another person's Briefs, they now see only items they could see themselves. Before, they could see invoice and estimate amounts and contract signers that their own role doesn't allow.
• Run now shows the list on screen and no longer emails it. Also email me applies only to scheduled runs.
• Scheduled Briefs emails now include your routines. Before, routines were counted but missing from the email's list.
• Updating from a version before 4.205.0 now converts every team member's summary email setting into an agent, not just the first 1,000 people's.
• The one-time notice on Briefs now says your agent runs at the time you picked with Also email me on, and where to turn the email off.
• Assistant: links in "What's due?" now open the task in the side panel instead of a "page not found" error.

v4.205.0 — October 19, 2026

Agents now run on a schedule and hand you a short list, with a button on each item

• Turn on Weekly Breakdown and every Monday around 7 am it lines up your week: what's overdue, what's due each day, tickets waiting on you, and 3–5 things to focus on. Pick a different day or time if you like.
• Turn on Upcoming Due to see everything due in the next 7, 14 or 30 days, grouped by type. Managers can also group it by person. Open it whenever you want, or put it on a schedule.
• Results live on the new Briefs page. Each item has Open, Mark priority, Send reminder and Dismiss. A dismissed item stays hidden until its due date changes, and only for you.
• Agents only show what you can already see. Clients never see agents or Briefs.
• Agents run on the hour, so a 7 am agent arrives between 7 and 8. Tick Also email me to get the same list by email.

Send reminder never sends to a client on its own

• A reminder to yourself is a notification. A reminder to a teammate is a notification, after you confirm, and at most once a day.
• A reminder to a client or contract signer becomes a prefilled draft in Actions, and nothing goes out until a person publishes it. Drafts made from an agent's list are never auto-sent, whatever your auto-send settings.
• For an overdue invoice, you can send the existing overdue reminder email after you see exactly what will go out. Invoice and estimate reminders need permission to edit invoices.

The Agents tab is rebuilt around your agents

• Your agents shows what each agent does, when it runs, what you get, and when it last ran and will run next, with Run now, Pause and Edit.
• New agent takes two steps: pick what it should do, then when and how.
• Suggest agents for me looks at your own work and recommends one or two agents, each with a reason drawn from your real counts, for example how many items are overdue. Turning one on is always your click. The assistant can show suggestions but never turns an agent on.
• Agents connected from outside, such as Claude Desktop, are listed unchanged under Connected assistants. "Autonomous" now reads Can only draft, which is what it always meant.

Actions says where things came from, and old drafts stop piling up

• Every item shows where it came from (an agent's list, your assistant, or a connected assistant), and Waiting is grouped that way.
• Drafts nobody has touched for 14 days are marked Stale, and after 30 days they move to Done › Expired. A draft whose own date has passed is marked stale straight away and expires 14 days later. A reminder drafted from an agent's list expires once what it was about is settled, such as the invoice being paid, or after 7 days.
• Expiring never sends and never deletes anything. Open the draft under Done › Expired and click Restore to bring it back.
• The client filter on Waiting now works for drafts too.

What changes when you update

• If you're on the team and had the daily summary email turned on, it becomes an agent at the same time of day with Also email me on, and you'll see a one-time notice on Briefs. Clients keep the summary email as before.
• The summary email for clients now arrives in the hour you picked. Before, it often didn't arrive at all. Its project section now lists real project due dates.
• On the first hourly check after updating, drafts that are already past these limits move to Done › Expired, where you can restore them.

v4.204.1 — October 18, 2026

New portals show the photo slider on the login page from the start

• A brand-new portal now gets the ClientCove photo library on its login page (and file transfer pages) as soon as setup begins, so the very first sign-in shows the rotating photos. Before, it only appeared once the setup wizard was finished.
• This applies only to a portal that has never finished setup. Existing portals keep their login background, including after re-running the wizard, and a background you have chosen is never changed. You can switch to a static image or another feed any time in Login Designer.
• On phones the photo credit line is no longer shown on the login page, so it doesn't cover your logo. It still shows on larger screens.

Security fix: "What's due?" only lists work you can see

• The assistant's "What's due?" now lists only work you can see. Client users get tasks for their own company (and tasks they created), never other clients' or your team's internal tasks. Team members get the same view as the work calendar. The same applies to MCP and agent callers.

v4.204.0 — October 18, 2026

The Resources page loads faster for everyone

• Opening Resources, switching folders and scrolling to load more are quicker for every kind of user. The biggest gains are for clients and contractors, whose resource lists used to take several seconds on larger sites.
• Everyone still sees exactly the same resources and folders as before. Only the speed changed.
• The page also asks the server for less: only the details the page shows, the Trash count only for people who have a Trash button, and the client list only for staff.

Quick View takes the whole screen on phones

• On a phone, Quick View now opens full screen instead of as a side panel with a sliver of the page showing behind it. It respects the notch and home bar, and scrolling inside it no longer scrolls the page underneath.

Security fix: workbench folders

• Fixed a way a client could get resources from workbench folders listed through a specially crafted request. They still only saw resources shared with their own client, but the workbench should stay hidden from clients entirely, and now it does.

v4.203.2 — October 18, 2026

Security fix: resource access, everywhere a resource opens

• Opening, downloading or zipping a resource now follows exactly the same rules as the Resources list. Before this update, a signed-in client who knew a resource's number could open its page, download its files, download it as a zip, load its gallery images and read its notes, even when the resource belonged to another client. Update promptly.
• The rules: resources assigned to one of the person's clients, public resources with no client, unassigned resources for contractors who can see shared resources, and nothing in the Workbench unless the person can see the Workbench.
• The same rules now apply to the assistant's resource search and to the resource lookup used by connected AI tools. A contractor with several clients now finds resources for all of them there, not just the first.
• A valid share link still opens the resource it was made for, PIN and expiry included, and someone who bought a resource through a product can still open it. An old link format that skipped the client check on the resource page no longer does.
• These checks now apply even when the Resources feature is switched off.
• Staff see nothing different, and there's nothing to configure.

v4.203.1 — October 17, 2026

Security fix: resource access

• A signed-in client can no longer open another client's resource by its address in WordPress's built-in data feed. Before this update, any signed-in client who knew or guessed a resource's number could read its title, which clients it belongs to and its file list, even though the resource never appeared in their Resources page. Update promptly.
• Opening a resource through the data feed now follows exactly the same rules as the Resources list: resources assigned to one of the person's clients, public resources with no client, unassigned resources for contractors who can see shared resources, and nothing in the Workbench unless the person can see the Workbench.
• The resource list in the data feed can no longer be widened by adding a share code to the request. Share links themselves work exactly as before.
• Staff see nothing different, clients see nothing different in the portal, and there's nothing to configure.

v4.203.0 — October 17, 2026

Deleting a resource now also cleans up its older files

• Since version 4.192, deleting a resource permanently also removes the files it uploaded from your storage. Files uploaded before that version were left behind and kept using space.
• After this update, a one-time background check matches those older files to the resource they were uploaded with. Once matched, deleting the resource removes them too, like newer uploads.
• A file is only matched when it's clearly that resource's own upload. Anything also used somewhere else stays put, for example a file picked from the media library, your logo, a location photo, or a file linked in an article, message or ticket.
• Matched files can also be included when you use Send as transfer on their resource.

v4.202.0 — October 17, 2026

Ad and web previews are no longer at guessable addresses

• Ad groups and web previews are served from a public address so the preview can load them. Until now that address was built from the resource's ID, so anyone who could guess an ID could open the files and the original zip.
• New uploads and replacements now go into a folder with a long random name that can't be guessed. Previews, downloads and sharing work as before.
• Ad groups and web previews you already have are moved to random folders automatically in the background after the update. The old addresses then stop working. Nothing else changes for you or your clients.
• If you store files in your own cloud bucket, make sure file listing is switched off in the bucket's settings, so the folder names can't be listed.

Fixed

• Copying files in S3 or DigitalOcean Spaces storage no longer fails for names containing characters such as ?, #, + or %. This also affects moving a resource's files when you change its client.

v4.201.0 — October 17, 2026

A redesigned email designer, with a templates gallery and ten new blocks

The email designer has a new layout

• The email designer now works like the form builder: a toolbar across the top, blocks on the left, your email in the middle, and the options for whatever you've selected on the right.
• Click a block in the email to edit it on the right. Changes show in the email as you type; there is no separate edit window or "Save changes" step for each block.
• Add a block by clicking it (it goes right after the block you have selected) or by dragging it to the exact spot you want. Drag blocks in the email to reorder them, or use the move, duplicate and delete buttons that appear when you hover.
• With nothing selected, the right side shows an overview of the email and its design: layout, width, corners, colors, header bar and border.
• A Variables tab on the left lists every merge field. Click one to drop it into the field you're editing.
• Keyboard shortcuts: Ctrl/Cmd+S saves, Ctrl/Cmd+Z undoes, Esc deselects, Delete removes the selected block (a notice offers Undo).

Templates gallery

• The designer now opens on a Templates tab that shows every email template as a small live preview, with its type, block count and which notification it's used for.
• Search templates, filter by Transactional, Digest, Marketing or Defaults, and open, duplicate or delete any of them from the gallery.
• Templates comes first in the toolbar: Templates, Build, Settings, Preview.

Ten new blocks

• Subheading, List (bulleted or numbered), Quote (with an optional attribution), Callout (an info, success, warning or neutral note box), Columns (two text columns), Details (label and value rows, handy for invoice totals and due dates), Video, Social, Spacer and HTML.
• The Video block shows a thumbnail and a "Watch the video" link that opens the video. Email apps can't play video inside an email, so it does not play in place.
• The Social block shows text links to the profiles you fill in. It uses text rather than icons because many email apps block icon images.
• All new blocks appear in the emails that are actually sent, not only in the designer.

Settings and Preview

• Settings holds the template type, which notifications the template is used for, whether it's the default, and the logo.
• Preview fills the email with sample data from your most recent matching record, at desktop or mobile width.
• Send test now saves unsaved changes first, because the test always uses the saved version of the template.

Fixes

• Saving the onboarding, form auto-reply and form "finish later" templates in the designer no longer removes which notification they're used for. Those notifications now have their own checkboxes.
• The Message block in the designer now matches the sent email.

Nothing changes in your existing emails until you edit and save a template.

v4.200.0 — October 17, 2026

Tickets: new Filters panel and a working date filter

• The Tickets list now filters the same way Resources does: a search box, a Filters button that opens a small Client · Tech · Created panel, and a Clear button. The Filters button shows how many filters are on.
• While the panel is closed, each filter you've applied shows as a chip under the search box; click its × to remove just that one.
• Created offers Any time, Today, Last 7 days, Last 30 days, This year, or a custom range. A custom range includes both dates, and you can leave either end empty (for example "Since Aug 1").
• Fixed: changing the client, tech or search used to drop the date range without saying so. The range now stays put through filter changes, sorting, paging and the status and category links.
• Fixed: "Today" and the other quick ranges now follow your site's timezone. Before, they used the viewer's UTC date, so in the evening in the Americas "Today" found nothing, and the date shown was a day early.
• Fixed: Export to CSV now includes only the tickets in the selected date range.
• Fixed: going to page 2 or later of a ticket category no longer drops the category.
• Nothing changes until someone uses the filters, and links that already carry a date range still work.

v4.199.0 — October 17, 2026

A cleaner Filters panel on the Resources page

• Type, Client and date added now sit on one compact row, taking about a third of the space they used to.
• Dates are a single "Added" choice: Any time, Last 7 days, Last 30 days, This year, or Custom range. The two date pickers appear only when you choose Custom range, starting from whatever range you had picked.
• When the panel is closed, each filter you've applied shows as a small chip under the search bar, for example "Type Gallery" or "Added Jul 1 – Jul 31, 2026". Click the × on a chip to remove just that filter.
• The separate "Filtering by tag" banner and the extra results bar are gone. Their information is in the chips and the "Showing N" line. Inside a folder, a slim "Search in: This folder / Everywhere" switch remains.
• The Client filter only appears for people who have a client list to choose from.
• On phones, the Filters and Clear buttons show just their icons, so the search box has room to type.

Galleries download as a zip on local storage

• On sites that store files on their own server rather than in cloud storage, Download All on a gallery now works. Galleries are also included when you select several resources and download them as a zip. Before, both failed for galleries.

Fixed: saving in the resource editor

• One click on Save now saves once. It used to send the save twice, which could leave a gallery with every image listed twice.
• After Save, the page stays where you are and refreshes the preview instead of reloading.
• Save & View no longer triggers the browser's "leave site?" warning after a successful save.

v4.198.4 — October 17, 2026

Security fix: share-link QR codes

• The QR code for a resource's share link is now drawn in your browser. Before, it was fetched from an outside service (quickchart.io), which meant sending that service the share link, including its access key.
• Earlier versions also saved each QR image in your uploads folder at a public address based on the resource's ID. Anyone who guessed the address could scan the image and get the share link. Those saved images are deleted automatically the next time an administrator opens the dashboard, and QR codes are no longer stored anywhere.
• Download PNG and Download SVG still work. The PNG is now 1024 pixels.

Resources page

• Searching by file type ("pdf", "jpg", "tiff" and so on) is much faster on large libraries, and it now also finds images inside galleries.
• Thumbnails load as they scroll into view instead of all at once, so long lists open faster.
• Dates, counts and column headings on the Resources page are easier to read. Their grey text now meets accessibility contrast guidelines in both light and dark mode.

v4.198.3 — October 17, 2026

Resources page fixes

• The Resources list now loads more resources as you scroll, and keeps loading when the first page doesn't fill the screen. Before, more only loaded when you clicked Load More.
• In quick view, Next on the last loaded resource now loads the next page and carries on. The counter shows the full total, for example "31 of 80".
• If loading more resources fails, the ones already shown stay on screen, with a Retry link at the bottom.
• If a folder fails to load, the page now says so with a Retry button. Before, it could keep showing the previous folder's resources as if they were this folder's.
• Folder search now finds folders inside other folders. It opens the folders leading to each match and shows the match in bold. Clearing the search puts the tree back as it was.
• On a resource page and in its editor, confirmations and error messages now use the portal's own dialogs instead of the browser's pop-ups. This covers moving to Trash, deleting a file, removing a section, changing type, restoring a version and removing a video.

Fixed: recurring invoices skipping a short month

• A monthly, quarterly, semiannual or annual invoice series that last ran, started or was recalculated on the 29th, 30th or 31st could skip the following month entirely, for example jumping from January 31 straight to March. The next date now lands in the following month, moving to that month's last day when it is shorter.
• Next dates already scheduled are left as they are and correct themselves the next time each series generates or is recalculated.

v4.198.2 — October 17, 2026

Security fix: resource videos

• Uploading, replacing and removing a resource's cloud video now checks that the person can manage that specific resource. Before, a signed-in client could attach a video to another resource, and a crafted request could expose or delete stored files that weren't that resource's video.
• A resource can now only point at a video that was uploaded to it, by the person saving it.
• Replacing or removing a video deletes the stored file only when it is that resource's own upload and nothing else uses it. Otherwise the video just leaves the resource and the file stays in storage.
• Nothing changes for staff uploading videos, and there's nothing to configure.

v4.198.1 — October 17, 2026

Security fix: resource galleries

• Adding, saving and removing gallery images now checks that the person can manage that specific resource. Before, a signed-in client could change another resource's gallery, and a crafted request could delete or expose stored files that weren't part of any gallery.
• A gallery can now only list images that belong to that resource: its own gallery uploads and its own files.
• Removing an image deletes the stored file only when nothing else uses it. An image shared with a cloned resource, or one that came in through an intake form, stays in storage.
• Nothing changes for staff editing galleries, and there's nothing to configure.

v4.198.0 — October 17, 2026

Filter resources by the date they were added

• The Filters panel on the Resources page has a new Date added row. Pick a start date, an end date or both, or use Last 7 days, Last 30 days or This year.
• Both dates are included, so a range ending today shows everything added today.
• Leave one date empty for an open range. A start date on its own shows everything added since then.
• Click an active quick range again, or the ×, to clear the dates. Clear also resets them along with the other filters.
• Works with the other filters, search and Search everywhere, and is remembered between visits like the other filters.
• Items in Trash aren't included, as with the rest of the list.

v4.197.0 — October 17, 2026

Intake forms take files up to 5 GB, straight to your cloud storage

Large uploads on intake forms

• With cloud storage (DigitalOcean Spaces, Amazon S3 or Google Cloud Storage), files attached to portal forms now go straight from the browser to your storage, with a progress bar. They no longer pass through your web server, so your host's upload limit doesn't apply.
• The default limit is now 5 GB per file. Leave a field's Max file size blank to use the default, or set a lower limit for that field. The limit is checked before the upload starts and again on the stored file, and a file over the limit is removed.
• Upload fields that were still at the old automatic sizes (100 MB for files, 10 MB for images) now use the new default. Fields you set to any other size keep it.
• File fields now accept any type of file except programs, scripts and web pages, so video, archives and design files work. Image fields still take images only.
• Without cloud storage, uploads still go through your server, are checked against the field's limit, and are capped at what your host allows.
• Public forms have a new Max upload size setting under Settings → Authentication → Public forms. It defaults to 100 MB (before this update the limit was fixed at 10 MB). Visitors' files still pass through your server, so your host's upload limit also applies.
• Uploads that were started but never finished are cleaned up after a day. Each person can have up to 50 unfinished uploads at once.

v4.196.0 — October 17, 2026

Send a resource's files as a file transfer

• Staff can now send a resource's files to someone as a download link. Open the resource, choose Send as transfer from the ⋮ menu, untick any files you don't want to send, and create the transfer. You get a link to copy.
• The transfer is linked to the resource and its client, and shows up under Transfers like any other.
• Nothing is emailed when you create it. If you entered a recipient, a Send email button sends them the link only when you click it.
• The files stay in the resource. The transfer points at the same files, and deleting the transfer or letting it expire never removes them.
• Set when the link expires (from 1 day to never) and, optionally, a password the recipient must enter before downloading.
• The option appears for admins and editors who can create file transfers, when file transfers are switched on.
• Only files uploaded to the resource itself are offered. Files picked from the media library still show on the resource but can't be sent this way. Files kept on your own web server instead of cloud storage can't be sent as transfers either.

v4.195.0 — October 17, 2026

New dashboard widget: Balance Due

• Balance Due shows what is still owed on open invoices as one number, with how much of it is overdue and how many invoices that is. Click it to go to Invoices (you can change the link).
• Client users see only their own company's balance, and only if they are allowed to see invoice amounts. By default that is Client Admin and Client Billing; Client Standard and Client Basic don't get the card at all.
• Staff who manage invoices see the total for every client, or for one client chosen in the widget's Client setting. Previewing the dashboard as a client shows that client's balance.
• Sales roles don't see other clients' balances, even though they can see every client elsewhere.
• Open invoices are Sent, Viewed, Overdue or partly paid. Drafts, Paid, Cancelled and Refunded invoices never count. An invoice counts as overdue when it is marked Overdue or its due date has passed.
• Invoices in different currencies get separate totals and are never added together.
• Add it from the dashboard builder, or ask the assistant to add a Balance Due card to a dashboard.

v4.194.3 — October 17, 2026

Fixed: dashboard drafts stay drafts in the builder, and the Ticket Form and Intake Form widgets use their settings

• Opening a draft dashboard in the dashboard builder no longer publishes it. Before, the builder's automatic save published any dashboard left open for about a minute, even if nothing was changed and Save was never pressed. It could also bring back a dashboard that had been moved to the trash.
• The builder still saves your work in the background every minute, but that save keeps the dashboard's status. Pressing Save publishes the dashboard, as before.
• A dashboard in the trash can no longer be saved from a builder that was left open on it. Restore it first.
• The Ticket Form widget now uses its heading, intro text, button label and success message. Before, it always showed the defaults.
• The Intake Form widget now shows the intake you chose. Before, it always said "No intake selected".
• If a dashboard was published earlier only because the builder was left open on it, it is still published. Set it back to a draft from the builder if needed.

v4.194.2 — October 17, 2026

Fixed: field settings inside multi-step intake forms

• Fields placed inside the steps of a multi-step form now keep their settings when you save. Before, these settings were lost on every save: Toggle labels and default, Address "International addresses", User field options (mode, multiple, max users, auto-assign, invite approval), and upload label, description, required and max file size.
• Edits to an upload field's label or required setting inside a step now stick.
• Renaming an Info or HTML block after its first save now sticks, inside steps and on single-page forms.
• The form shows each upload field's own size limit instead of a fixed 10 MB or 100 MB.
• Settings that were dropped before this update were never stored. Set them again and save the form once.
• The size limit is a guide shown on the form. It is not yet enforced when the file arrives.

v4.194.1 — October 17, 2026

Cleaner resource pages

• Resource titles are more compact: long titles wrap evenly with tighter line spacing, and every resource type uses the same title style.
• Documentation resources (articles and FAQs) have a cleaner layout. The title lines up with the content, the text has more breathing room, and the "On this page" list has a clear marker for the section you're reading.
• The "On this page" list and the side column now appear only when there is room for them. With the sidebar or a pinned panel open, they step aside instead of squeezing the text into a narrow column.
• The side column no longer opens empty when a resource's attached files have since been removed.
• Pinned resources in the side panel no longer repeat the title or show the "On this page" list, since the panel has its own header.
• Resource pages load a little faster.
• Nothing to configure. The Expand button still widens a resource to the full page.

v4.194.0 — October 17, 2026

The assistant builds dashboards, and you can add new dashboard pages

Dashboards from the assistant

• Ask the assistant (or Claude, through the ClientCove connector) to build a dashboard, for example "build a billing dashboard for client admins with their outstanding invoices and recent tickets". It picks real dashboard widgets, sets their options, and chooses the roles, clients and page the dashboard is for.
• A dashboard the assistant creates is always a draft. Nobody sees it until you publish it, either by asking the assistant or by pressing Save in the dashboard builder. When you publish from chat, the confirmation names the page and the roles and clients who will see it.
• The assistant can also rename, retarget, publish or unpublish a dashboard, and add, change, move or remove its widgets. Every change shows what will happen and waits for you to reply YES.
• Only administrators, editors and system admins get these abilities. Client users and portal agents never do.
• Custom HTML widgets can only be added in the dashboard builder, not by the assistant.
• If the dashboard builder is open on a dashboard while the assistant changes its widgets, pressing Save in the builder replaces the assistant's changes with what the builder shows.

New dashboard pages

• Dashboards appear on pages. You can now create a new top-level page for them from Dashboards → New page, from the new Show on page picker when adding a dashboard, or from a dashboard's Settings → Page Assignment → New page for this dashboard.
• As you type the address, the portal checks it is free. It tells you when another page already uses it, or when the portal itself uses it, and suggests one that is free.
• After the page is created you are asked which menus should link to it. Menus that match the dashboard's roles are already ticked. Clients that have their own custom menu don't get the link automatically.
• Only administrators can add the page to menus. Editors can create the page and are asked to have an administrator add the link.
• Show on page starts at "Not on a page yet". A new dashboard goes live as soon as it is created, so choosing a page that already shows a dashboard can change what those users see.

v4.193.6 — October 17, 2026

Intake forms: the Repeater field now keeps its settings, enforces Required, and shows its rows

• A Repeater field's label, description and Required setting are now saved. Before this update they were lost every time the form was saved, so the field came back as "Repeater" and not required. Its columns were always kept.
• Forms that already have a Repeater keep their columns. Set its label and Required again, then save the form once.
• A required Repeater now needs at least one row with something in it. The blank row a form starts with no longer counts as an answer, in the portal and on public forms.
• Blank rows are dropped when a form is submitted.
• Submissions show a Repeater's answers as a table with the column headings, with links you can click. Before this update they showed as "Array, Array". Emails and exports list one row per line.
• File requests: upload notices left behind by file requests deleted before 4.193.4 are now cleared away automatically. There's nothing to see or do.
• No setting changes and nothing to turn on.

v4.193.5 — October 16, 2026

Security fix: downloading several files as a zip

• On sites that store files locally (not in cloud storage), choosing several files and using Download as zip used to save the zip at a public web address, where anyone with the link could open it for as long as the file stayed there. The zip is now kept in a private folder that can't be reached from the web.
• The download link only works for the signed-in person who asked for it, and only for 10 minutes. Each time it is used, it checks again that the person can still see every file in it and that none of the files have changed. If something has changed, it asks them to download again.
• Zips nobody has downloaded in a day are deleted automatically. Zips left in the old public location are removed once after this update.
• If the "some files were left out" message stays open for a long time, the page fetches a fresh link, so you don't land on an expired download.
• Also fixed for every storage type: if a file in a selection was replaced by another one, the same number of files could make the download serve the old zip. It now builds a new one.
• Nothing to configure. Sites using cloud storage download the same way as before.

v4.193.4 — October 16, 2026

Deleting a file request cleans up after itself

Fixed

• Since 4.193.1, each file request that received uploads keeps a small record of which files have already been announced by email, so none is announced twice. Deleting the request, or letting it expire and be removed, left that record behind. It is now removed along with the request, together with any pending upload email for it.
• This changes nothing you see in the portal and nothing to configure.

v4.193.3 — October 16, 2026

Intake forms: the submissions form filter stays put, a tidier form builder, and a preview that scrolls

• On Intake Manager → Submissions, choosing a form in the form filter now shows that form's submissions. Before this update it jumped back to "All Forms". Links that already point at one form's submissions keep working.
• The form builder's Add to form panel is more compact, with smaller field tiles, and no longer scrolls sideways.
• On narrower screens the builder's top bar shows its buttons as icons, so Save is always visible. Hover a button to see its name.
• The builder's Preview now scrolls for long forms. Before this update the form was cut off at the bottom of the screen. This applies to the desktop, tablet and phone widths.
• No setting changes and nothing to turn on.

v4.193.2 — October 16, 2026

Security fix: file request uploads

• A file request link now accepts only the files actually uploaded through that request's upload page. Previously, someone holding the link could make the request list a file stored elsewhere in your portal, including another client's file, or register the same upload more than once.
• Each upload is accepted once, for the request it was started on. An upload started on one file request can't be added to another.
• Nothing changes for the people uploading: the upload page works exactly as before, and no settings are involved.

v4.193.1 — October 16, 2026

One email per file request upload, with the uploader's name

Fixed

• When someone uploaded several files to a file request, you got one email per file. A 10-file upload now sends one email that lists the files: the first ten by name, then "and N more".
• The email now names the person who uploaded, using the name they typed on the upload page. Before, a request sent by link with no recipient said "A client uploaded a file".
• The email goes out when the upload page finishes. If the person closes the page partway through, the email for the files that made it still arrives about ten minutes later.
• A file is never announced twice. Files already announced before this update are not announced again.
• If you customized the "upload complete" email template, your wording is kept. Its file name field now lists every file in the upload rather than only the last one. Nothing to configure.

v4.193.0 — October 16, 2026

Intake forms: public and embeddable forms, form settings, versions, new field types, and reports

Public and embeddable forms

• A form's Who can see & fill setting has a new option, Public / Embeddable. A public form has its own page, an iframe embed and a script embed for your website, all from the new Embed tab. Existing forms stay exactly as they were until you choose it.
• Public forms always use bot protection. Set up Turnstile, hCaptcha or reCAPTCHA under Settings → Authentication → Public forms (your login Turnstile keys are used until you add separate ones). A public form accepts nothing until a provider is set up.
• Spam protection is built in: a hidden trap field, a minimum fill time, rate limits, and an optional list of the sites allowed to embed the form. Blocked attempts are logged on the form.
• Public submissions wait for approval before any automation runs, unless you turn on Run automations without approval. A visitor whose email matches a portal user is suggested for that user's client but is only attached when you approve; everyone else shows as a new lead.
• A new automation, Create client from submission, makes a client from the answers.
• Each submission records where it came from: your portal, the hosted page or an embed, plus the referring site and UTM tags.
• Public uploads are held separately and kept only when the form is actually submitted. They need private cloud storage.

Form settings

• After submit: show a message (with answers merged in) or send people to a page, optionally carrying chosen answers in the address.
• Notifications: pick who's alerted, optionally only when answers match conditions, and send submitters an auto-reply styled in the Email designer. Auto-replies to public visitors never repeat what they typed.
• Availability: open and close dates, a response limit and a closed message. Staff, including administrators, can still fill a closed form.
• Save & resume: portal users can email themselves a link back to a draft; public multistep forms can offer Save and finish later. Unfinished visitor drafts are deleted after 30 days by default. Portal drafts are never deleted automatically.
• Preview at desktop, tablet and phone widths, or as the real embed.

Versions and safer editing

• Every save that changes a form's questions keeps a read-only version. Each submission remembers the version it answered and always shows those questions, so renaming, reordering or deleting a field no longer breaks older submissions or sends their answers to the wrong field.
• Switching a form between Form and Steps keeps every field and mapping. Going back to a single page asks first if step logic would be lost.
• Automations warn when a required field on the record isn't mapped, or when an answer type doesn't fit the field (for example text into an image).
• Before you approve, the submission page shows Approving will…: each automation that will run, the record an update will change, and its values now and after. Nothing changes until you press Approve.
• New starting templates: Project, Support Ticket and Client Contact.

New field types

• Email, Phone, Number, Currency and URL, each format-checked in the browser and again by the server.
• Star rating, 1–10 scale and NPS (0–10).
• Hidden fields filled from a link parameter, a UTM tag, the referring page or a fixed value.
• Consent: a required checkbox with a policy link, saved with the time it was agreed.
• Calculated fields that do arithmetic on other answers, recalculated by the server so they can't be tampered with.
• Product picker: public forms list only public products; portal forms list the products the person can see.
• An Email field's answer is used as the submitter's email for client matching and the auto-reply.

Default create forms

• A form can be the New client, New resource, New asset, New location, New project or New ticket form (Settings → Default create form). The portal's New buttons then open that form, and after submitting people go straight to the record it created.
• It only takes over a button when the form has an automation that creates that kind of record on submit. Otherwise the button keeps its usual form. New client and New project forms are for staff only.
• Nothing changes until you choose a form.

Reports

• Every form has a new Summary tab: submissions, how many drafts get finished, median time to complete and to approve, approval rate, submissions over time, drop-off by step, and where submissions come from.
• Each question gets a chart that fits its type: choices, ratings with average and NPS score, number ranges with min, average, max and total, dates and yes/no splits. Long text answers can be summarised into common themes with AI, only when you click.
• The submissions page is now a table you can filter by status, date, source and any answer, with saved filters, your choice of answer columns, bulk approve and reject, and CSV or Excel downloads of what's showing.
• Download a summary as a PDF, or share it with a read-only link. The link shows totals and charts only, never individual answers, names or emails, and you can replace it or turn it off at any time. Links are off until you create one.
• Send a weekly or monthly email digest of a form to chosen staff. Digests are off until you turn them on.
• A new Intake form report dashboard widget shows a form's numbers, trend, sources or one question's answers. Only staff see it, whoever the dashboard is shared with.
• Drop-off by step counts people from when they start a form. Visits that never start it aren't counted. Furthest-step tracking starts with this update, so older drafts count only the step they're on now.

Fixes and changes

• Submission counts now agree everywhere and count finished submissions, with drafts shown separately. Opening a form in the builder no longer creates a draft for you. Drafts it created before this update are still there.
• Status names are now Draft, Awaiting review (Submitted on forms without approvals), Approved and Rejected. "In progress" submissions are now Drafts. Autosave no longer changes a submission's status.
• New fields and steps get a name from the start, and a form with an unnamed field can't be saved.
• A form that still has submissions can't be permanently deleted; it stays in the trash. Submissions whose form was deleted show the form's name.
• Uploaded images and files on submissions show reliably instead of breaking after a week.
• Two form uploads with the same file name no longer overwrite each other.
• The forms list has filters for form type and the record a form creates.

v4.192.4 — October 16, 2026

Security fix: client folder permissions in Resources

• Clients and contractors can now only add, move, restore or file resources into their own client's folders, whatever the folder's name. Before this update, a folder whose web address was a number could be checked against the wrong folder, which could let a client put resources into another client's folder.
• Creating a subfolder now checks the same parent folder the subfolder is created in.
• Uploaded and edited resources are assigned to the client who owns the folder they are filed in, as intended.
• Staff are unaffected. No setting changes and nothing to turn on. Update promptly.

v4.192.3 — October 16, 2026

Security fix: gallery images, shared files and Download All on local storage

• Gallery images now load only for people who are allowed to see them. On a share link, they stop loading as soon as the share is turned off or expires, or while its PIN hasn't been entered. Before this update, images in a gallery that wasn't in a client's folder could be loaded without any share at all.
• Signed-in clients and staff now see gallery images that are in a client's folder. Before this update these images could fail to load for people who were allowed to see them.
• Files, videos and previews opened from a share link now use links that last an hour, or less if the share ends sooner. Before this update these links lasted 7 days.
• If your site stores files on the web server rather than in cloud storage, Download All now checks who is downloading, just as it does with cloud storage, and gives a link that lasts 10 minutes. Before this update the zip was saved at a fixed public address that anyone with the address could open, even after a share ended. Those old files are removed when you update.
• No setting changes and nothing to turn on. Update promptly.

v4.192.2 — October 16, 2026

Security fix: share links and Download All

• File links on a shared resource now only open the file and share they were made for. If a share needs a PIN, its files can only be opened after the PIN has been entered on the share page.
• Files on share links with an expiry date work again. Before this update they were refused even before the link expired. Links set to never expire are unaffected.
• Links to files in cloud storage from a share now stop working after an hour, or sooner if the share ends first. Before this update they kept working for 7 days, even after a share expired or was turned off.
• Download All can only be used by someone who can see the resource, or by a visitor with a live share link (with the PIN entered, if the share needs one). It is rebuilt whenever the resource's files change, so removed or replaced files are no longer included. It respects each resource's setting for allowing zip downloads, and permanently deleting a resource also removes its download.
• Copying a resource with Clone no longer copies its share link or PIN, and clients can no longer clone a resource they don't manage.
• File names and links for a resource are only shown to people who can see that resource.
• Shared files that a browser could run, such as HTML or SVG, now download instead of opening.
• Visitors who unlock more than one PIN-protected share in the same browser stay unlocked on each.
• No setting changes and nothing to turn on. Update promptly.

v4.192.1 — October 16, 2026

More uploads keep files with the same name separate

Fixed

• 4.191.2 stopped same-name uploads from replacing earlier files in most places. This release covers the rest: images and files added in the resource editor, images pasted into messages and tickets, contract PDFs, client logos set from an intake form, and files added to a file transfer or file request.
• Contract PDFs were the most visible case. With cloud storage on, a new contract whose PDF had the same file name as an earlier contract for the same client could replace the earlier contract's PDF.
• Two files with the same name in one file transfer, or in one file request upload, are now stored as two files. Before, the second could replace the first.
• When two names clash, the later file is stored with a number added, such as contract-1.pdf. The name you see in transfers, messages and the editor stays the name of the file you uploaded.
• Files that were replaced before this update can't be recovered by the update. New uploads are protected from now on. Nothing to configure.

v4.192.0 — October 16, 2026

Resources: permanently deleting a resource now removes its files, and shared files are protected

• When you permanently delete a resource from the Trash, the files uploaded to it are now removed from your storage too, including its attached files, earlier versions, gallery images and video, and ad or web-preview bundles. Before this update they stayed in storage after the resource was gone.
• Only files that belong to that resource are removed. Files it shares with something else are kept, such as a file sent to it from a message, a file transfer or an intake form, a copy made with Clone, or another resource or ticket.
• This applies to files uploaded from this update on. Files uploaded to resources before this update stay in your storage when the resource is deleted, as before.
• Shared files are now protected everywhere in the portal. Deleting a file no longer removes the stored file while a message, file transfer, project card or cloned resource still uses it, and moving a resource to a different client copies a shared file instead of moving it away from the others.
• Clearing or replacing the ad or web-preview bundle on a cloned resource no longer removes the original resource's bundle.
• No setting changes and nothing to turn on.

v4.191.2 — October 16, 2026

Uploading a file with the same name as an earlier one no longer replaces it

Fixed

• When cloud storage is on, uploading a file with the same name as an earlier file in the same storage folder could silently replace the earlier file. This affected ticket attachments, client logos, intake uploads, and files added through the resource and attachment uploaders. Some of those folders are shared by every client, so one client's upload could replace another client's file. Each upload is now stored as its own file.
• Two people uploading files with the same name at the same moment now always get separate files.
• When two names clash, the later file is stored with a number added, such as report-1.pdf. Ticket attachments and uploaded files keep the name you gave them. Pages that show the stored file name show the numbered name.
• Files that were replaced before this update can't be recovered by the update. New uploads are protected from now on. Nothing to configure.

v4.191.1 — October 16, 2026

Fix: File transfers to several people, emoji and quotes in saved data, and orders from closed checkouts

• A file transfer sent to more than one email address now reaches everyone. Before this update, a list such as "ana@example.com, ben@example.com" was merged into one address that does not exist, so nobody received the email and no error was shown. Separate addresses with commas or semicolons; each person gets their own copy and does not see the other addresses.
• The recipient field on the Transfers page now accepts a list of addresses. Before this update the browser refused a list before it was sent.
• Transfer emails with no recipient name now greet "Hi there," instead of "Hi ,".
• Details laid out as a table in email templates (for example Transfer, Files and Expires) now keep their layout. Before this update the labels and values ran together on one line. This affects estimate and ticket emails that use a table too.
• Emoji, quotes and backslashes are now saved correctly in message participants, intake forms, product groups and pages, project scope history, decisions, file summaries, notifications and other places that store lists. Before this update an emoji could be saved as text like "u270fufe0f", and a quote could make the whole saved list unreadable. Values already saved incorrectly are not repaired; they are fixed the next time they are saved.
• When a buyer pays on your site and closes the page before checkout finishes, the order now starts onboarding and runs your order automations, the same as any other order. Before this update those orders were recorded but nothing that follows a completed order happened. An order is never announced twice.
• No setting changes and nothing to turn on.

v4.191.0 — October 16, 2026

Resources: Undo, quicker card actions, and a better fit on phones

• After you move resources to the Trash, the confirmation now has an Undo button. Undo puts each resource back in the folders it came from and keeps the clients that could see it. Resources that weren't in a folder go back to not being in one.
• Each resource's menu now has Move to…, Download and Copy link. Cmd-click or Ctrl-click (or middle-click) a resource to open it in a new tab.
• When a list is empty, the page now says why, for example an empty folder, a search with no matches, or an empty Trash, and offers the next step, such as Add resource, Clear search and filters, or Search everywhere. A search inside a folder says it only searched that folder.
• On phones and tablets, the select box and action buttons on each resource are now always visible, since there is no hover. When the page is narrow, resources show in two compact columns instead of one tall card per row.
• The Add Resource, folder and tag windows now open with the cursor in the first field, close with Escape, and keep keyboard focus inside them while open. Close buttons are labelled for screen readers. The Filters button now counts a tag filter.
• Renaming or editing a folder that doesn't belong to a client no longer rechecks every resource inside it, and routine entries are no longer written to the server error log on every upload, move and shared-file view.
• No setting changes and nothing to turn on.

v4.190.3 — October 16, 2026

Fix: Fewer database errors on every page, and clearer messages when creating a product

• Every page load ran two failing database checks while making sure the e-signature and payment-webhook tables existed. This produced errors in your database log and wasted time on every request. The checks now look for each table first and only create the ones that are missing. Your existing tables and their data are not changed.
• When you create a product or service and something is missing or invalid (no name, no description, a price that isn't a number, or an image that isn't a picture or is over 5MB), the message now appears in the portal's own notification instead of a browser pop-up.
• No setting changes and nothing to turn on.

v4.190.2 — October 16, 2026

Fix: Resources page trash, folders and lists

• Resources that have no files no longer show a loading bar labelled "Indexing…" forever. They now say "No files".
• The Trash now shows everything in it. Before this update it stopped at 100 items, and "Empty trash" only deleted those. Emptying a large trash now happens in batches; if some items can't be deleted, you are told how many were deleted and why.
• Clicking a resource in the Trash now opens a preview. Before this update it opened a page that didn't exist.
• The Resources page no longer reopens into an empty, hidden Temp folder that made the page look empty. The Temp folder also stays in the folder list while it has files in it.
• After a new search, filter or sort, only the selected resources you can still see stay selected, so bulk actions can't affect resources that are out of view.
• Folder counts now update after you move resources to the Trash, delete them permanently or restore them.
• Changing a search or filter quickly no longer shows the previous results as if they matched.
• Only one resource's menu can be open at a time, and pressing Escape or clicking elsewhere closes it.
• No setting changes and nothing to turn on.

v4.190.1 — October 16, 2026

Security fix: Resources permissions

• Client and contractor users can no longer change which clients can see a resource, change which client a folder belongs to, or make a client folder visible to everyone. Only your team can. Client users who are allowed to add resources can still rename their own folders and file resources into them as before.
• Only your team can now create, rename or delete tags. Client users who can manage a resource can still add and remove tags on it, but can no longer tag anything else in the portal.
• "Delete permanently" now only works on resources that are in the Trash. Before this update, resources still selected in a folder could stay selected after you opened the Trash and be deleted permanently along with the trashed ones.
• When you change which client a folder belongs to, or move a folder into another client's folder, the previous client now loses access to the resources in it and in its subfolders. Before this update the previous client kept access alongside the new one. Clients you added to a resource by hand are kept.
• Several folder actions now check that the request came from the portal itself, upload links are only given to people who can add resources, and the names of a resource's folders are only shown to people who can see that resource.
• Permanently deleting a resource still leaves its files in your storage, as before.
• No setting changes and nothing to turn on. Update promptly.

v4.190.0 — October 16, 2026

Messages: @mentions in replies, a working Mentions folder, links that open the conversation, and one reaction per person

• @mentions now work in replies, not just in new messages. The person you mention gets a notification and the conversation shows in their Mentions folder.
• The Mentions folder now lists every conversation you were mentioned in, older ones included. Before this update it could stay empty.
• Mentioning someone who isn't in the conversation adds them to it, so the notification they get opens a conversation they can read. They also get the usual new-message email. Staff can mention anyone. Clients can mention people they're already allowed to message, or anyone already in the conversation. A mention of anyone else isn't sent and doesn't add them, but the message itself still sends.
• The Read Full Message button in new-message emails, mention notifications, and the message links in the daily digest now open the conversation in Messages, where you can reply. Before this update some of them opened a read-only page.
• In the reply box, Cmd+Enter on a Mac sends your reply, like Ctrl+Enter on Windows. Both now work while you're typing in the reply box.
• Reactions are now one per person. Your thumbs-up or smile no longer replaces someone else's, and tapping it again removes only yours. Each message shows how many people reacted, including on your own messages. A reaction made before this update still counts as one.
• No setting changes and nothing to turn on.

v4.189.1 — October 16, 2026

Email replies to tickets are checked against the sender, and folder uploads report the right folder count

• Security: an emailed reply is now added to a ticket only when it comes from a registered portal user who can see that ticket: staff, the ticket's author, a user of the ticket's client, the assignee, or a subscriber. This applies whatever the "Only accept emails from registered portal users" setting says. Before this update, an email that looked like a reply could be added to a ticket by anyone.
• When an inbound email's From address belongs to a registered user, the sender's domain must now back it up with SPF or DKIM. Otherwise the email is not accepted. This stops someone posing as a user by faking the From address. Google Workspace, Microsoft 365 and Gmail already do this. If a user on their own domain finds their emailed replies no longer arrive, their domain needs SPF or DKIM set up.
• After you drop a folder of folders onto Resources, the summary now counts only the folders that received files. Before this update it also counted the parent folders on the way. For example, it said "into 4 folders" when the files went into 3.
• No setting changes and nothing to turn on.

v4.189.0 — October 16, 2026

Resources: a heads-up before duplicate uploads, keyboard access, and clearer progress for folder uploads

• When you drag files onto Resources and one would sit next to a resource with the same name in that folder, you're asked first. Choose Skip duplicates, Upload all, or Cancel. Two files with the same name in one drop are caught the same way. Bundling files into one resource isn't affected. If the check can't run, the upload goes ahead as before.
• Clients and contractors only see matches among the resources they can already open.
• Dropping a folder of folders now shows one progress bar for the whole upload, with the file being sent ("File 3 of 12: brand-guide.pdf"). Before this update the bar went back to 0 for each folder and briefly disappeared between them.
• Folders, resource cards and list rows can be used from the keyboard. Tab to them, press Enter to open, and press Space to select a card. On a folder, the Right and Left arrows expand and collapse it. A card's buttons appear when it has keyboard focus.
• Client and contractor users no longer see a "Client list couldn't load" warning each time they open Resources.
• If tags fail to load, or a new client folder's Workbench can't be created, you're now told. If the "Also in this folder" list can't load, it says so and offers Try again. Before this update it said the folder was empty.
• Uploads no longer write each file's details to the server's error log.
• No setting changes and nothing to turn on.

v4.188.0 — October 16, 2026

New: Quick tagging and date changes on My Tasks

• Each task on My Tasks now has a tag button just before its due date. Click it to pick tags from a short list; each tag you click is added or removed and saved straight away. A "New tag" link at the bottom creates a tag without leaving the list.
• Until a task has a tag, the button is a faint tag icon. Once tagged, it shows only the tags' colour dots, which replace the dots that used to sit in front of the task title.
• Click a task's due date to change it with a date picker. Picking a date saves it; clearing the date removes it. Tasks with no due date still get their date from the task's edit view.
• When you filter by a tag from the side panel, the "Clear Filter" bar above the list now fits on small screens instead of running off the edge.
• The details under each task now wrap onto a new line on narrow screens instead of squeezing the date and labels.
• No setting changes and nothing to turn on.

v4.187.3 — October 16, 2026

Fix: Resources dialogs, error messages, and sites in a subfolder

• Restoring files from the trash now lets you choose the folder to restore them to. Before this update the folder list did not appear.
• When you move files or folders between clients, or into or out of a client's folders, the warning now says which client they are moving from and to. Before this update these warnings showed a title with no explanation.
• If a folder you move has the same name as one already in the destination, you are now offered a new name ("Name (2)") to accept or change. A blank name or one already in use is refused, and you are asked again.
• If the folder list, the client list or the trash can't be loaded, the page now says so instead of looking empty. If a folder can't be created while you drop a folder of files, the message now gives the reason.
• Error messages on the Resources page now stay on screen for 6 seconds instead of 3, and the remaining browser pop-ups there now use the portal's own dialogs.
• The Resources page now works on sites where WordPress is installed in a subfolder (for example example.com/portal) or uses plain permalinks. Before this update the file list, the trash and uploads could fail on those sites.
• No setting changes and nothing to turn on.

v4.187.2 — October 16, 2026

Project status changes now reach your automations, Slack and notifications

Fixed

• Changing a project's status (from the status badge on the project page, or from Edit Project) now triggers everything that listens for it. Before this release those changes went unnoticed: "Project completed" automations never started, the Slack "Project status changed" post never sent, and project members were not notified.
• Marking a project Completed now starts automations built on "Project completed", including the recipes "Project completed: wait, then request feedback" and "Projects completed 3 days ago: send survey".
• Each real change is reported once. Picking the status a project already has does nothing, and no longer shows "Failed to update status".
• Edit Project now opens with the project's current status selected. Before, saving the form without touching the status reset the project to Open.
• Slack and in-portal notifications show the status name (for example "In Review") rather than an internal code.
• Dashboard widgets, the crew dashboard, a client's Projects tab and project counts now show each project's real status.

Changed

• Edit Project offers the same eight statuses as the status badge: Open, In Progress, In Review, Needs Client Action, Submitted, On Hold, Completed, Cancelled.
• The On Hold help text now describes what On Hold does: it shows an On Hold badge in project lists. It does not hide the project anywhere.

Good to know

• Nothing needs to be turned on. Automations and Slack posts you already set up for project status changes start working after the update.
• Status changes made before this update are not replayed, so no automation runs for projects that were completed earlier.
• Projects saved with an older status keep it and display correctly. No data is rewritten on upgrade.

v4.187.1 — October 16, 2026

Resources: Edit Title and Edit Client Access work from the card menu, and the upload limit shown is your real one

• Edit Title in a resource's ⋯ menu now lets you rename the resource right on the card. Press Enter to save or Escape to cancel. Before this update the menu item did nothing. Double-clicking a title to rename it now puts the cursor in the box straight away.
• Edit Permissions is now called Edit Client Access and opens the folder picker for that resource. A resource's client access follows its folder: move it into a client's folder to share it with that client, or into a general folder to remove client access. The picker explains this. Before this update the menu item did nothing.
• The Add Resource drop area now shows your real limits, for example "Up to 100 files · 5 GB max each". The file count is the "Maximum files per upload" setting in the Resources section of Settings, or your server's limit if you do not use cloud storage. Before this update it always said "Up to 20 files".
• Size limits read the same everywhere. A 5 GB limit now shows as "5 GB" in the drag-in upload warnings too, where it showed as "4.9 GB".
• No setting changes and nothing to turn on.

v4.187.0 — October 16, 2026

Resources: file limits checked up front, and a Cancel button for drag-in uploads

• Files you drag onto the Resources page are now checked against the same per-file size limit and files-per-upload limit as the Upload button, before anything is sent. You no longer find out a file was too large after waiting for it to upload.
• Files over the size limit are named and skipped, and you are asked whether to upload the rest. If every file is too large, nothing is sent.
• If you drop more files than one upload allows, you are asked whether to upload the first ones up to the limit. Choosing Cancel uploads nothing. The limit is the "Maximum files per upload" setting in the Resources section of Settings (100 unless you changed it), or your server's limit if you do not use cloud storage.
• The files-per-upload limit now applies to dropped folders too. Before this update a dropped folder could bring in up to 500 files regardless of that setting.
• The upload progress card now has a Cancel upload button, which asks you to confirm. With cloud storage, files that have finished uploading are still added and the rest stop, and you are told how many were added. Without cloud storage, cancelling adds nothing from that upload. Cancelling a folder upload stops before the next folder starts.
• Once the upload reaches "Finishing up…" it can no longer be cancelled, because the files are already being added.
• No setting changes and nothing to turn on.

v4.186.3 — October 16, 2026

Fix: uploading by dragging files onto Resources

• While files you dropped onto the Resources page are uploading, the page now shows its progress where you can see it, even in a long folder, and says to keep the tab open until the upload finishes. Leaving or reloading the page mid-upload now asks you to confirm first. The Upload dialog and the CSV import show the same reminder.
• If some files in a drop fail, the rest are still added, and you are told which files failed and why, for example "2 of 3 files uploaded". Before this update, one failed file could stop the whole drop and the files that had already uploaded were not added to Resources.
• Dropping several files now keeps you on the Resources list and tells you how many were added. Dropping a single file still opens the new resource, as before.
• Dropping a folder now says how many files actually uploaded and lists any that failed. Before this update it could report "Folder upload complete" even when some files had failed.
• On sites that store files on the web server rather than in cloud storage, dragging files onto the Resources page did not add them and showed "No files were uploaded". It now works. Uploading through the Upload button was not affected.
• After the file list fails to load, Retry now brings the list back without reloading the page.
• No setting changes and nothing to turn on.

v4.186.2 — October 16, 2026

Fix: repeating dates at the end of the month

• Monthly, quarterly, every-6-months and yearly routines and recurring tasks that start on the 29th, 30th or 31st now land on the last day of shorter months and return to the original day in longer ones. A series that starts January 31 now runs Feb 28, Mar 31, Apr 30, and so on. Before this update it jumped from January 31 to March 3, skipping February and putting two dates in March, and it could drift further from there.
• A yearly series that starts on February 29 now falls on February 28 in other years, not March 1.
• If you move one date of a recurring task yourself, later dates follow the date you picked, even if it is the last day of a month. Changing how often a routine repeats keeps it on its original day.
• Daily, weekly and every-2-weeks schedules are unchanged. Due dates you already have, on tasks and routines, stay where they are. Future dates the calendar shows for a series follow the new rule, so a date that showed as March 3 now shows as February 28. Recurring invoices are not affected.
• No setting changes and nothing to turn on.

v4.186.1 — October 16, 2026

Security fix

• Completes the fix in 4.185.1. Intake form templates, agreements, dashboards, connected apps, product groups, project templates and knowledge-base articles are no longer readable through WordPress's built-in data feed by anyone outside your team. Before this update, a visitor who wasn't logged in could list them, and could read the text of agreements and of knowledge-base articles, including drafts and articles meant only for your team.
• Public intake forms, agreements you share, product embeds on other sites and the knowledge base in the portal all work exactly as before. Clients see nothing different.
• No setting changes and nothing to turn on.

v4.186.0 — October 16, 2026

The calendar now has on/off toggles for each type (tasks, tickets, projects, routines, cards, meetings) and remembers your choices. Routines on the calendar show when they're overdue, open a quick card to create the task, mark it done or edit the routine, and you can drag a routine's due date to reschedule that visit without changing its schedule.

v4.185.1 — October 16, 2026

Security fix

• Portal records are no longer readable through WordPress's built-in data feed by anyone outside your team. Before this update, a visitor who wasn't logged in could list invoices, tickets, messages, notifications, intake submissions, contracts, orders, assets, locations, email campaigns and client names, and could find files uploaded to them. These records are now available there only to staff. Update promptly.
• Clients see nothing different in the portal. Invoices, tickets, messages and everything else clients open in the portal work exactly as before.
• Files in the media library can now be looked up through that feed only by staff and by the person who uploaded them. Uploading attachments, for example in a message, still works for everyone who could upload before.
• No setting changes and nothing to turn on. If you run another plugin that reads your media library or portal records through the WordPress data feed without signing in, it will now be refused.

v4.185.0 — October 15, 2026

Draft invoices are now private: clients can't see, open or pay an invoice until you send it, and payment links to drafts stop working until it's sent. Cancelled and refunded invoices can no longer be paid online. Recurring invoices have a new option: Hold as a draft for my review. Each new invoice waits as a private draft, you're notified, and if the series auto-charges, the saved card is charged when you send it.

v4.184.0 — October 15, 2026

A clearer routine form

A clearer routine form

• The Add routine and Edit routine form on asset, location and client pages has been redesigned to match the calendar's add form: short uppercase labels, compact fields, and red markers on the required ones.
• Next date counts from now explains both choices. The schedule keeps fixed dates (monthly from the 15th stays on the 15th, whenever the work gets done). When it's done counts one interval from the day the work is finished.
• Each task setting says what it does. Reminder only makes no tasks. Create tasks on demand adds a Create task button each time the routine comes due. Create tasks automatically makes the assignee's task ahead of each due date, and only then asks how many days ahead.
• The reminder reads as a sentence, "Remind the assignee 1 days before it's due", and explains that it sends a notification and an email, and that 0 reminds on the due day.
• Visible to the client now says what clients see: the name, schedule, notes and due date, read-only, never the assignee or tasks.
• Nothing about how routines work has changed, and existing routines keep their settings.

v4.183.0 — October 15, 2026

Routines on the client page

Routines on the client page

• Each client page has a new Routines tab. It lists the client's own routines and every routine on the client's assets and locations, soonest due first, with a badge counting the ones that are overdue or due this week.
• A routine can now belong to a client as well as to an asset or location. Use it for work that isn't about one asset or location, like a quarterly review or an annual renewal. Add routine on the client's Routines tab adds one to the client. Routines for a specific asset or location are still added on that asset or location's page.
• Rows for asset and location routines name where each routine lives and link to it. You can mark them done, create their task, or edit them from the client page if you can edit that asset or location. Editing the client's own routines takes permission to edit clients.
• Client routines remind their assignee, appear on the calendar, and can create tasks like any other routine. Their tasks are linked to the client. They do not set a next or last service date, because clients don't have one.
• Client users still only see routines marked Visible to the client, and only read-only.
• The assistant can list and add client routines too: list routines for a client now includes the client's own routines.
• Nothing changes for existing routines.

v4.182.0 — October 15, 2026

Recurring invoices can now charge the client's saved card automatically, with their consent. Turn on Auto-charge saved card for a recurring invoice; the client agrees the next time they pay, and later invoices are charged when they're created. Failed charges email the client the payment link, and every automatic receipt includes a link to stop automatic payments.

v4.181.0 — October 15, 2026

Routines on the edit screens

Routines while you edit

• A location's edit screen now shows its routines on the Management tab, below Service Notes. You can add, edit, mark done, create a task, pause or delete a routine there, without leaving the edit screen.
• An asset's edit screen shows the same live list on its Management tab, where it used to show a link to the Routines tab.
• Changes to routines save straight away. You don't need to press Save on the edit screen for them, and pressing Cancel & Exit doesn't undo them.
• Nothing else changes: the Routines tab on the asset or location page works as before, and the same people can see and change routines.

v4.180.0 — October 15, 2026

Automations no longer skip events for the same client

Automations that run on an event

• Each event-triggered automation now runs once per record. Before, two events for the same client within a minute (two tasks completed, two invoices paid) often ran the automation only once, and the rest were logged as "deduplicated".
• This affected: a task is completed, a project is completed, an intake form is submitted, a message is received, an invoice is paid, an estimate is accepted, declined or viewed, and an order is completed. Inbound emails were also affected: every email received within the same minute collapsed into one run. Each email now runs on its own.
• A true repeat of the same event on the same record within a minute is still run only once, as before.
• Billable hours are logged is unchanged on purpose: it still runs once per client per minute, so a burst of time logged across one client's tasks sends one threshold alert, not one per task.
• Nothing to change in your automations. Ones that seemed to fire less often than expected will now fire every time.

v4.179.0 — October 15, 2026

The assistant can work with routines

Routines in the assistant, MCP and automations

• Ask the assistant about routines: "what maintenance is due this week", "which routines are overdue for Acme", "when is the SSL renewal next due". It can also add a routine, reschedule, reassign, pause or resume one, mark it done, create the task for its next occurrence, or delete it.
• Every change is shown to you first and only happens after you reply YES.
• The same tools are available to MCP clients and as steps in automations.
• Client users can ask about routines that are shared with them. They see the name, schedule, notes and due date, never who it is assigned to or its tasks, and they can't change anything.
• Agents can work routines only on assets and locations they are allowed to edit, within their keyring. When listing routines they must name a client or an asset or location.

Assigning routines

• Choosing someone other than yourself as a routine's assignee now needs the same permission as assigning a task to someone else. Without it, you can assign routines to yourself, and edit any routine you can edit as long as you leave its assignee as it is.
• A routine's tasks always go to its assignee, whoever presses Create task.

v4.178.0 — October 15, 2026

Routines for assets and locations

Routines

• Assets and locations have a new Routines tab for anything that repeats: filter changes, inspections, certificate renewals, backup checks. Each routine has a name, how often it repeats (daily to annually), its next due date, an assignee and notes.
• Choose whether the next date follows the schedule (the 15th of every month, whenever the work gets done) or counts from when the work is finished (90 days after the last filter change).
• Each routine either just reminds, gives you a Create task button per occurrence, or creates the task automatically a set number of days ahead (7 by default). There is only ever one task per occurrence, and completing that task moves the routine on to its next date.
• Mark done moves a routine on without a task. Every routine event is written to the asset's or location's activity log.
• The assignee gets an in-portal notification and an email before each occurrence (1 day ahead by default), once per occurrence. The email follows their "task due soon" email setting and quiet hours.
• Routines appear on the calendar in teal, with the next occurrence and the dates after it, and a Routines filter. When an occurrence already has a task, the calendar shows the task only.
• New automation trigger: A routine comes due, once per occurrence, with the routine, the asset or location, the due date, the assignee and the client.
• Routines are internal by default. Turn on Visible to the client to let the client's users see a routine, read-only. Clients never see who it is assigned to or its tasks.
• An asset's Next Service Date now follows its routines (the soonest due date). Assets without routines keep their dates exactly as you set them.

Service schedules became routines

• On upgrade, each open service schedule from the asset edit screen becomes a routine automatically: same name, interval and due date, same assignee, creating its tasks a week ahead. Its open tasks carry on as the tasks for those dates. Nothing is emailed for occurrences that were already overdue at the switch.
• The asset edit screen now links to the Routines tab instead of listing schedules.

Also in this release

• On an asset's page, the Report a problem form now sits in the right-hand sidebar instead of below the whole page. Public share links are unchanged.

v4.177.0 — October 15, 2026

Ticket task updates show on the ticket right away

Live updates on the ticket page

• If you have a ticket open and post an update from one of its tasks (using the My Tasks side panel), the update now appears in that ticket's conversation and history right away. Before, it only showed up after you reloaded the page.
• If you changed the ticket's status in the same step, the new status shows right away too.
• Nothing else changes: you're still asked first, internal notes are still the default for staff, and time tracked on the task is never added to the ticket.

v4.176.0 — October 15, 2026

Bulk complete can update tickets too

Update tickets when you complete tasks in bulk

• When you mark several tasks complete at once with Bulk Edit, My Tasks now asks whether to post an update to each ticket those tasks are linked to.
• It asks once per ticket, not once per task. Each prompt lists that ticket's newly completed tasks as "Completed: " lines, which you can edit before posting.
• Tasks that were already complete don't trigger a prompt, and tasks not linked to a ticket are skipped.
• The same choices apply as when you check off a single task: staff can post an internal note (the default) or a reply the client sees, and can change the ticket's status. Time tracked on the task is never added to the ticket.
• Nothing is posted unless you click Update ticket. "Don't ask again" on any prompt skips the rest for your browser session.
• Works on the My Tasks page and in the My Tasks side panel.

v4.175.0 — October 15, 2026

Ticket tasks can now update their ticket

Update the ticket from My Tasks

• When you check off a task that's linked to a ticket, My Tasks asks whether to post an update to that ticket. The suggested text is "Completed: " followed by the task name, and you can edit it before posting.
• When you save new notes on a ticket task, it offers to post the text you added. If the notes didn't change, it doesn't ask.
• Staff can post the update as an internal note, which is the default and is never shown to the client, or as a reply the client sees. Staff can also change the ticket's status in the same step. Clients can post a reply but can't make internal notes or change the status.
• The update shows up on the ticket just like a typed reply, and the people on the ticket are notified the same way.
• Time tracked on the task is never added to the ticket.
• Nothing is posted unless you click Update ticket. "Not now" skips it once, and "Don't ask again" stops the question for the rest of your browser session.
• Works on the My Tasks page and in the My Tasks side panel. Bulk "mark complete" does not ask.
• Project tasks are unchanged: checking one off still marks it complete on the project.

v4.174.3 — October 15, 2026

Contracts on mobile, and three fixes

Contracts list on phones

• The contracts list now fits a phone or a pinned side panel without sideways scrolling. Empty status tabs are hidden on narrow screens, column headings line up with their columns, rows are one line shorter, and the Submissions filters each get their own line.
• Desktop is unchanged.

Fixes

• Contracts: the Sign button now appears only for people who can actually sign that contract. Staff who are not signers, and recipients who have already signed, now see Open instead.
• Intake forms: sharing a form or a submission with someone now also sends them an in-app notification, as well as the email. Before, only the email went out.
• Automations: automations that run on a subscription, such as pre-renewal reminders, could be attached to the wrong client when the subscription was linked to more than one. They now always use the subscription's first linked client.

v4.174.2 — October 14, 2026

Payment receipts reach whoever paid

Who gets the paid invoice

• When an invoice is paid by card, the paid invoice (PDF attached) is now emailed to the person who paid — the address entered in the payment form — and to the client's billing contact. Anyone at the client's company can pay from the link; they get their proof of payment, and the billing contact still gets the paid invoice for their records.
• If the person paying is the billing contact, one email is sent, not two. Each person receives their own email; neither sees the other's address.
• Correction to v4.174.1: its note said the receipt goes to whatever address is entered. Until this release it went only to the billing contact; it now goes to both.

Payment-link email field

• The email field is now filled in only with company-level addresses: the client's billing contact, or the client's own email if no contact is set. It is never filled with an individual team member's email. If neither is on file, the field is left empty for the person paying to fill in.
• The field can still be changed before paying. Signed-in clients still see their own email.

v4.174.1 — October 14, 2026

Faster checkout from a payment link

Payment-link invoices

• The email field in the payment form is now filled in for you. Opened from a payment link, it shows the address the link was sent to — the client's billing contact, or the client's own email if no contact is set. It can still be changed before paying, and the receipt goes to whatever address is entered.
• Signed-in clients are unchanged: the field shows their own email.
• If the client has no email on file at all, the field stays empty, as before.

v4.174.0 — October 14, 2026

Clients get their paid invoice by email

Invoice copy on payment

• When a client pays an invoice by card — from the emailed payment link or inside the portal — they now receive a payment confirmation with the paid invoice attached as a PDF. This happens automatically; there is nothing to turn on.
• It goes to the client's billing email. If none is on file, it goes to the email entered with the card.
• The "Auto-send payment confirmation" setting is unchanged: it still controls only invoices your team marks as paid by hand. Those confirmations now include the PDF too.

Payment-link invoice page

• The "Log in to download a copy" button is gone — the emailed copy replaces it. Downloading the PDF from the page still requires signing in.
• A new Pay Invoice Now button sits next to Login at the top of the page, on unpaid invoices only.
• The invoice card is now white, and it no longer slides under the header on wide screens.

Fixes

• Signed-in clients now see the Pay Invoice button at the top of an unpaid invoice. It was missing; the button inside the invoice card was unaffected.

v4.173.3 — October 14, 2026

Fixes

• Placeholders like and in a contract message are now filled in on every kind of send. They already worked when sending a template; a one-off contract's signing email and the in-app "new contract" message showed them exactly as typed. When one in-app message goes to several signers, the signer-specific placeholders are left blank and the rest are filled.
• On a contract template's page, someone who confirmed their emailed code before this update now shows as "Verified by" rather than "Signed by". The record was correct; the page wasn't finding it.

v4.173.2 — October 14, 2026

Fixes

• The emailed signing code is now required by default on every contract. Signers already entered a code before signing, but most contracts didn't have the setting saved, so the code wasn't checked when the signature was submitted. It now is, and those signatures read "Verified by" on the signed PDF instead of "Signed by".
• Nothing changes for signers — they see the same code step as before. A contract where you've explicitly switched the code off still skips the check.

v4.173.1 — October 14, 2026

Fixes

• The message you type when sending a contract template (Send from Template) now reaches each recipient's email. Before, it was saved but the email carried the contract's default message instead. With no message typed, the default message is still used.
• On template sends, the "Sent by" and "Date sent" contract variables now name the person who sent it and when, rather than the template's author.

v4.173.0 — October 14, 2026

Verified signer line under every signature

• Each signature on a signed contract PDF now carries a line such as "Verified by jo@acme.com, Jo Smith on October 14, 2026 11:38 am", and when the signer signs for a client company, a second line: "Acting as an agent of Acme Co".
• "Verified by" appears only when the signer entered the emailed (or texted) verification code. Contracts that don't ask for a code say "Signed by" instead — turn on the verification code on a contract if you want every signature to read "Verified".
• The same lines show under the signature on the signature certificate and on each signed copy of a template. PDFs signed before this update are not changed, but their certificate pages show the line too, built from the signing's audit trail.
• Nothing about who can sign or how signing works changes; this only records and shows more about each signature.

Variables in contracts

• When placing fields on a contract PDF, a new Variable menu adds values the portal fills in for you: signer name, email and phone; client company name and billing address; contract title and number; date sent; who sent it (name and email); and your company name.
• Values are filled in at signing from the portal's own records — the signer sees them but cannot change them. A variable with no value on file is simply left blank.
• The same names work as placeholders in the message sent with a contract: wrap a variable name in double curly braces (the Variable menu shows each one), and each recipient gets their own values.

v4.172.6 — October 14, 2026

Fixes

• A contract template you've sent no longer shows "Awaiting Signature" to your team after people have signed it. Its status now reads "Template" with how many people have signed, are still waiting, or declined — the same counts the Contracts list shows. Each person who signs still sees their own status, and one-off contracts are unchanged.

v4.172.5 — October 14, 2026

Fixes

• Signed contracts now display on phones. The signed document used to show only its first page on iPhone and nothing at all on Android; every page now shows, sized to fit the screen.
• On a phone or narrow window, a signed contract now shows its status and details first, then the signed document and its download buttons, then the signing certificate and audit trail. The document used to sit at the very bottom of the page.
• The "contract signed" email sent to your team now uses your portal's name instead of "ClientCove", links to the contract in your portal instead of the WordPress admin, shows the client the contract was sent to instead of "N/A", and shows the signing time in your site's time zone.

v4.172.4 — October 14, 2026

Fixes

• Buttons and panels meant to fill the width of their card no longer come out a fixed 400 pixels wide. On phones they stuck out past the edge of their card on a number of portal pages; they now fill the space they're in, as intended. This also fixes some elements that should fill the full height of their container.

v4.172.3 — October 14, 2026

Contracts: signing works properly on phones

Fixes

• The signing window now covers the whole screen. In 4.172.0 to 4.172.2 the portal's header and side menu stayed on top of it and could still be clicked while signing.
• On phones, signing now opens full screen, and the contract page fits the screen instead of being drawn wider than it. Fields stay where they were placed.
• Small fields such as checkboxes are easier to tap on a phone, and field labels and filled-in dates no longer get cut off.
• On phones and narrow screens, the contract's status and the Sign Contract Now or Download button now appear at the top of the page, above the document and the signing certificate.
• The signing certificate fits narrow screens: its header wraps, and the audit trail lists each event on its own line instead of a table you had to scroll sideways.
• The Download Signed Contract and Reject buttons no longer stick out past the edge of their card on phones.

v4.172.2 — October 14, 2026

Contracts: a decline on a template closes only that person's copy

Fixes

• When you send a template to several people and one of them declines, only their copy is closed. Everyone else can still sign, and the template stays open so you can keep sending it. Before, one decline voided the template for everyone who hadn't signed yet.
• The sender is notified with the reason they gave, and the template's recipient list marks them Declined.
• A one-to-one contract works as before: if its signer declines, the contract becomes Void.
• Template rows in the contracts list show how many people declined, next to the signed and awaiting counts.
• After you void a contract, the Sent and Void tab counts update straight away, without reloading the page.

v4.172.1 — October 14, 2026

Contracts: void a sent contract, and status tabs that fit on phones

New

• Staff can now void a contract that is out for signature, from the row's "⋯" menu or the contract page. Voiding withdraws it but keeps the record: it can no longer be signed, it stays in your list as Void, and the contract page shows who voided it, when, and the reason if you gave one.
• When voiding, you can choose to email the people who haven't signed yet. Nobody is emailed unless you tick that box.
• Voiding a template closes every invitation that hasn't been signed. Copies that were already signed are not changed.
• Only a sent contract can be voided. A draft can simply be deleted, and a signed contract cannot be voided. A voided contract can't be sent or resent again; duplicate it to send a corrected version.

Fixes

• The status tabs on the Contracts and Submissions pages (Draft, Sent, Signed, Void, All, Templates) now wrap onto extra rows on phones and beside a pinned side panel, instead of running off the side of the screen.

v4.172.0 — October 14, 2026

Contracts: safer signing, reusable templates, and new field types

This release rebuilds how contracts are secured, sent and signed. Nothing needs to be switched on; the changes below take effect when you update.

Security

• Client users can no longer reach staff contract actions such as delete, edit, export, send or the audit trail. Clients still see and sign the contracts sent to them.
• Signed contracts are now rebuilt on the server from your original PDF, so the wording a signer sees cannot be changed in their browser before they sign. Each signing is sealed, so a later change to the signed file or its record can be detected.
• Signed PDFs are now private and download only through the portal for people allowed to see them. On update, existing signed copies are moved out of public storage automatically the first time a staff member opens the portal. Old direct links to signed files stop working.
• One-time signing codes now go only to the signer's own email or phone on file. Requests are rate-limited, and verification locks for an hour after five wrong codes.
• The old "mark as signed" shortcuts left over from earlier e-signature integrations are removed. A contract is signed only by signing it.
• CSV exports now download straight to your computer and are no longer kept on the server. Export files left from earlier versions are deleted on update.

Fixes

• Send on a draft contract now works. It used to fail and still leave the contract marked Sent.
• Reminder emails from Resend now contain a working one-time sign-in link. Staff signers get a normal link instead.
• Signing or rejecting a contract now notifies the sender by email and in the portal, and in Slack if you have it connected. Access a contract grants is now unlocked when it is signed in the portal.
• A contract's status no longer disagrees between screens. Existing contracts are reconciled once on update.
• Date Sent on the client page, and the Resent and Signed By columns in the CSV export, now show real values.
• The sample contract created during setup now appears in your contracts list.

Reusable templates for NDAs and other repeat agreements

• A new Templates tab lists your templates. Save any contract as a template, then send it to as many people as you need. Each person signs their own copy.
• Each template shows how many copies are signed and how many are still waiting, with a link to every signed copy.
• Send from a template to people already in the portal, or invite people by email. Someone without an account gets one that only shows what is sent to them, plus a one-time sign-in link. Existing accounts are never changed by an invite.
• Choose "Individual" instead of a client for freelancers and contractors who do not belong to a company.
• New contract from template creates a draft with the same PDF and placed fields, ready for you to pick the client and signers. Duplicate now keeps the placed fields and settings too.
• Each signed copy records which client it belongs to. The client page's Contracts tab now shows that client's templates and signed copies.

New field types

• Date: filled in automatically with the signing date. The signer cannot change it.
• Text: the signer types an answer, for example a job title. You choose the label.
• Checkbox: an acknowledgment the signer ticks, for example "I have read the confidentiality terms".
• Text and checkbox fields are required unless you mark them optional (double-click the field when placing it). A contract cannot be signed until every required field is filled in.
• What the signer entered appears on the signing certificate.

Contracts list

• The contracts pages now fit on phones and beside a pinned side panel. Less important columns fold into a summary under each title instead of scrolling sideways.
• New sorting and date-range filters, with removable chips showing which filters are active.
• Each row has one main action, with everything else in a "⋯" menu. Signed contracts have a Download PDF button.
• Archive, restore, delete and category changes update the list without reloading the page, and confirmations use the portal's own dialogs.
• Pinned contracts now open in the side panel with their details and signed PDF. Signing still happens on the full contract page.
• On phones, page titles and buttons no longer touch the edge of the screen. This applies to every page.

Audit trail

• Every change to a contract is now recorded with who made it, when, and from where: created, sent, resent, status changes, archived, restored, deleted, plus signing-code requests and failed attempts.

v4.171.2 — October 10, 2026

Fixes

• My Tasks calendar: dragging a task to a different day now saves the new date. Before, the task moved on screen but went back to its old day after you changed weeks or reloaded.

v4.171.1 — October 10, 2026

Change

• In My Tasks, the buttons in the Archived and Trash views (Restore, Delete, Unarchive All and Delete All Archived) are now smaller and line up with the task rows. Unarchive All is now blue like the other restore buttons instead of yellow. What each button does is unchanged.

v4.171.0 — October 10, 2026

Setup wizard logo upload, and File Transfers on by default

Setup wizard

• The logo step in the setup wizard now uploads your logo the same way Settings → Design does. Click the upload box or drag a PNG, JPG or SVG onto it. It no longer opens the WordPress media library.
• Your logo is saved as soon as it uploads, just like in Settings → Design.
• If your dark-mode logo was a copy of your old logo, uploading a new one updates it too.
• Replacing or removing a logo in Settings → Design no longer deletes an image that another logo slot is still using.

File Transfers

• File Transfers is now on by default for every portal.
• If you never changed the File Transfers setting, it is now on. If you turned it off in Core Features, it stays off. Nothing changes for portals that already have it on.
• The setup wizard no longer asks about large file delivery, because Transfers is included for everyone.
• File Transfers still needs cloud storage to work. Without it, Transfers stays hidden, as before.

v4.170.16 — October 9, 2026

Hosted portals now update their theme automatically

• If ClientCove hosts your portal, new ClientCove versions are now installed for you automatically once they are rolled out. You no longer need to click Update in WordPress.
• Self-hosted portals are unchanged: WordPress's own auto-update setting for the theme still decides.
• If a self-hosted update can't confirm the download with our servers (for example during a brief network problem), WordPress now stops the update cleanly and you can simply try again.

Clearer menu names

• Menu items now use the same names as the pages they open. For professional services portals, "Engagement letters" is now Agreements (admin menu) and Contracts (client menu), and the "Engagements" group is now Contracts & agreements. For consultant portals, the client menu item "Proposals & agreements" is now Estimates (or Contracts if estimates are turned off).
• Portals that already have the old names are updated once automatically. If you renamed one of these menu items yourself, your name is kept.

v4.170.15 — October 8, 2026

New: a clean "being set up" page before setup

• Until a new portal has been set up, its front end now shows a simple card instead of a half-built portal with the sample post: your logo, your site name and "This portal is being set up."
• Visitors who aren't signed in see a Log in to set up button, which signs you in and opens the setup wizard, plus a "Lost your password?" link. Hosted portals also remind you to use the Start setup button in your welcome email the first time.
• Admins who are signed in go straight to the setup wizard. Other signed-in users see "Your portal is being set up. Check back soon."
• Once setup is finished, your portal works exactly as before.

Good to know

• Portals already in use aren't affected. A portal that already has its sign-in page, a dashboard page or a static front page is treated as set up, and once it has been seen that way the setup page never comes back.
• If your portal is already set up but shows the setup page anyway, click "This portal is already set up — don't show the setup page". It's in the setup wizard and in a notice in your WordPress admin, and it turns the page off for good.
• Sign-in, password reset, public share links, intake forms, file transfers and other public links keep working as before. The setup page asks search engines not to index it.

v4.170.14 — October 8, 2026

New: set up your account first (hosted portals)

• When you open your new hosted portal for the first time, the setup wizard now starts with a "Your account" step: choose a password, confirm your first and last name, and optionally add a profile photo.
• The step tells you how you'll sign in from now on: your email address and the password you just chose. The "Start setup" link in your welcome email only works once, to get you started.
• You stay signed in after choosing your password and carry straight on with the rest of setup. The other setup steps unlock once this one is done.
• If you already chose a password using the link in your welcome email, or set one on your profile, you aren't asked to choose another. Your name and photo can still be changed here.
• This step only appears on hosted portals. Self-hosted portals are unchanged.

Fix

• Password reset and new-account emails now link to a sign-in page that always exists. Before setup created your branded sign-in page, these links could show "page not found".

v4.170.13 — October 8, 2026

Transfers for your whole team

• Transfers now appears in the account menu for System Admin, Tech Admin, Tech Lead, Technician, Representative, Sales Representative and Contractor, as well as Administrator and Editor. Clients still never see it.
• Technical staff (System Admin, Tech Admin, Tech Lead, Technician) see every transfer. Representatives, Sales Representatives and Contractors see only transfers for their own clients, plus client-less transfers they created themselves.
• Deleting a transfer is allowed by default for Administrator, Editor, System Admin, Tech Admin, Tech Lead and Representative. Technicians and Contractors can create and edit transfers but cannot delete them unless you grant "Delete transfers" on the Permissions tab. Sales Representatives can create and edit transfers but cannot delete them.
• Buttons a person is not allowed to use (Send, Edit, Delete and similar) are now hidden on the Transfers page instead of failing when clicked.
• Your existing Permissions choices are kept. Any Transfers permission you already changed on the Permissions tab stays as you set it; everything else picks up the new defaults automatically after the update.
• On the Permissions tab, Senior Contractor, Sales Representative and Tech Admin follow the Transfers settings you choose for Contractor, Representative and System Admin. Turning off "View transfers" for Contractor also turns it off for Senior Contractor.
• Turning off "View transfers" for a role now blocks that role everywhere, including the portal's API, not just the Transfers page.
• Files on a project page are unchanged: Contractors still see the transfer files on projects they already have access to.

v4.170.12 — October 8, 2026

Change

• On a file transfer, Message and Delete are now compact icon buttons at the top right, matching the resource page. Hover for their labels; on touch screens they stay large enough to tap.

v4.170.11 — October 8, 2026

File transfers: representatives see their own clients

• Representatives and sales reps now see, open and manage only file transfers for their own clients: clients assigned to them on their profile (Assigned or Managed Clients), or clients that list them as account manager or primary contact. Administrators, editors, system admins and technical staff still see every transfer.
• The transfers list, its tabs and counts, search, the create forms, Message about this transfer, a project's Transfers In and global search all follow the same rule. A transfer for another client looks the same as one that doesn't exist.
• Transfers with no client are visible to the person who created them and to full-access staff. Transfers created from a project, ticket or resource now record that item's client, and existing transfers are updated automatically in the background.

Security

• File transfers are no longer listed through WordPress's built-in public pages, API or search.
• Uploads to a transfer and files attached to it must come from the person's own upload or from files they can already open.

v4.170.10 — October 8, 2026

Fix

• On a file transfer, the title now stays on one line whenever it fits, on phones, tablets and laptops with the sidebar open. The type and status badges and Edit sit beside it when there's room, or together on the line below.

v4.170.9 — October 8, 2026

Message about this transfer

• On a file transfer, your team can now click "Message about this transfer" to send a portal message about it. The subject is filled in for you.
• Choose what the message is about: the whole transfer, specific files in it, or the file request. The message shows a card with the transfer's title and the files you picked, linking back to the transfer for people who can open it.
• You can send it to your team and that transfer's client's portal users. People outside the portal, such as a transfer's email recipient, keep getting the transfer's own emails.
• The transfer page lists the latest message threads about that transfer that you are part of.
• Replies work as usual: clients reply in the thread from their inbox.
• On phones, the message form opens full width with larger buttons.

v4.170.8 — October 8, 2026

File transfers on phones and tablets

• The single transfer page now fits a phone: the title is a full-width line with its status badges and Edit below, the shareable link has its own full-width row with Copy and Open underneath, and the actions are a tidy grid of larger buttons. There is now one Delete transfer button.
• Buttons, icons, tabs and filters across File Transfers are at least 44 pixels on touch screens, and text fields no longer make iPhones zoom in when tapped, including on your clients' upload and download pages.
• On phones and tablets, upload pages say "Tap to choose files".
• File requests with no named recipient now show "Anyone with the link".

Fixes

• Remove file on a transfer now works, with a confirmation, and the remove button is visible on touch screens.
• Removing a file or deleting a transfer no longer deletes stored files that a ticket, project or resource still uses.
• A transfer's file count now matches its files everywhere. Counts that were already wrong are corrected automatically.
• Allowed file types can be written as "pdf", ".pdf" or "PDF".

v4.170.7 — October 8, 2026

Project lead in Create and Edit

• On the Projects page, Create project and Edit project now use the same people panel as a project's Project users pop-up. Add people, search, remove them, and click a star to make someone the project lead. The first person you add becomes the lead.
• Only your team and the chosen client's own users can be added. If you change a project's client, people from the previous client are removed with a warning.
• The Edit form now preselects the project's current client, shows save errors on screen, and no longer has the single "User" dropdown that replaced the whole team when saved.
• Changes made in the Edit form appear straight away for anyone else viewing the project.

User management

• Administrators can now delete any user except other administrators and themselves. Everyone else can delete, activate, deactivate or move only users with a lower role than their own.
• Bulk actions now tell you how many users were changed and how many were skipped because you don't have permission.

Housekeeping

• Removed old, unused screens and actions from the theme.

v4.170.6 — October 8, 2026

Security

• Tightened permissions across the portal. Actions that change users, settings, orders, tickets, invoices, locations, products and uploaded files now check that the person is allowed to make that change, and only for records they can reach. Your team keeps every action its screens offer.
• Exporting tickets now requires signing in, and people outside your team get only their own clients' tickets.
• Editing, pinning, restoring, resending and copying ticket replies are now available to your team only, matching the ticket screen.
• In user management, the Delete link only appears for users you're allowed to delete: you can delete people with a lower role than yours, never yourself.

Changes

• When a client adds files to the resource library, they choose one of their folders first. If they have only one, it is selected for them.
• Tickets created from a project card are filed under that project's client.
• Items restricted to a client now open correctly for that client's users.
• If an upload was started just before this update, finishing it may ask the person to upload the file again.

v4.170.5 — October 8, 2026

Security

• Project actions are now limited to people who manage projects. Creating, editing, archiving, deleting and re-categorising projects and project templates require the project permissions your team already uses, so client users can no longer change projects they can see. Your staff keep everything they could do on the Projects page.
• The AI assistant's create and update project tools are now available to your team only, matching what clients and contractors can do in the portal. When the assistant assigns people to a project, it can only choose your team or that client's own users.
• The new-message box now lists only the people each user is allowed to message, and shows email addresses only to your team. On a project page, clients see their usual contacts plus the project's team. Drafts follow the same rules as sending.

Fixes

• Client users linked to more than one client company can now open their own clients' projects.

v4.170.4 — October 7, 2026

Fixes

• Managed portals now get the sample "Getting started" intake form once Intake forms is switched on during setup, as long as the sample data is still in place. Remove sample data removes it with everything else. If you switch the sample intake off in setup, it is not added.
• On professional-services and IT services portals, the client dashboard no longer shows a Projects shortcut that the client menu does not have. Existing dashboards are not changed.
• The sidebar no longer shows pages a person is not allowed to open. For example, "My assets" is hidden from client users who are not client admins, instead of sending them back to the home page.
• Core Features now finds the Locations and Assets pages when checking whether a feature is in a menu.
• New installs now create the database indexes that speed up messages on MySQL as well as MariaDB. Existing sites are not changed.
• Fixed a PHP warning in setup when looking up an existing dashboard page.

v4.170.3 — October 7, 2026

Security

• While an administrator is viewing the portal as another user (View as User), the screen that connects an AI app such as Claude to the portal no longer offers Allow. It asks you to return to your own account first, so a connection can never be approved on a client's behalf. Connecting from your own account works as before.

v4.170.2 — October 7, 2026

Connect your own domain

• On managed portals, the Get started card's Connect your own domain step now opens your portal's Domains page on account.clientcove.io directly, where a short guided setup walks you through using a subdomain (like portal.yourcompany.com) or your own domain.

v4.170.1 — October 7, 2026

Fix

• WordPress's weekly background tasks no longer stop with a critical error from the bundled field system's Site Health check, and wp-admin → Tools → Site Health → Info opens normally again. The field system's own Site Health section no longer appears there; nothing else changes.

v4.170.0 — October 7, 2026

ClientCove photo library

• New portals now show a slideshow of six Unsplash photos on the login page and on file-transfer pages, fading every 6 seconds. Each photo credits its photographer ("Photo by Name on Unsplash").
• Photos are chosen for your kind of business: agencies get beach, ocean and sailing; consultants mountains, weather and nature; IT services minimal workspace, office and technology; professional services architecture and landscape; everyone else animals, wildlife and adventure. Change the search terms any time in the login designer or in Settings → File Transfer.
• It is the new first option, "ClientCove photo library (default)", in both places. You do not need an Unsplash account or key.
• Only portals set up from now on get it. Existing portals keep exactly the background they show today until you choose the photo library yourself; re-running setup does not switch it on.
• If photos can't be loaded, the login page shows its colour or image and transfer pages show the previous stock photo, as before.
• Using your own Unsplash key still works. It now credits photographers too, and the saved key is masked: only its last four characters are shown, leaving the field blank keeps it, and a checkbox removes it.

Fixes

• The Sign In button on a brand-new portal's login page was invisible (white on white) until a button colour was saved. It now uses your brand colour, or ClientCove blue when none is set.
• Login page colours that were blank or invalid now fall back to sensible defaults instead of breaking the page.

v4.169.0 — October 7, 2026

A faster, friendlier first run

• The setup wizard is shorter. Managed portals have three steps: About your business, Look & feel and Your modules, and never ask for a license. Self-hosted portals start with the license step, then the same three.
• Use these defaults and finish, on every step, saves what you have chosen, fills in the rest for your kind of business and finishes setup in seconds. Nothing is locked in; change any of it later in Settings.
• The wizard saves as you go and says so. Save and finish later takes you back to your portal, and a Finish setting up your portal card on the dashboard shows where you left off with a Continue setup button. Coming back, the wizard opens on the step you stopped at.
• About your business asks three short questions. Look & feel shows a live preview of your portal in your logo and brand colour, and keeps colours you have already set. Your modules shows each module as an on or off card and lists the sample content already in your portal.
• Finishing shows a "Your portal is ready" screen in your logo and colours. If your device is set to reduce motion, it appears without animation or confetti.
• Show me around starts a short tour of your portal. Skip it at any step or press Esc. Take or replay it any time from Help in your account menu.
• After setup, a Get started card on the dashboard lists optional next steps: invite your first real client, connect your own domain (managed portals), set up payments, and remove the sample data. Each one ticks itself off when it is done. Hide it with its ×, and bring it back from Help in your account menu.

Sidebar menus built for your kind of business

• New portals get a sidebar designed for their business type (agency, consultant, IT services, professional services or something else), with related pages grouped: for example Work, Requests, Billing and Files. Labels fit the business, such as Requests, Support tickets or Engagement letters.
• Groups start open the first time you see them, then remember how you left them in that browser. The group for the page you are on always opens.
• Users, System Settings and Messages are in your account menu, so new admin sidebars stay focused on day-to-day work. Clients still see Messages in their sidebar. Sales reps and contractors now get their own menu instead of an empty one.
• Administrators see a small gear at the bottom of the sidebar that opens Settings → Menus.
• When you switch a module on later, it joins the right group, but only on a menu the wizard built and nobody has changed. Menus you have edited are never touched.
• Portals that already have menus keep them exactly as they are. Nothing is rewritten on upgrade.

Account menu

• The account menu in the header and the one at the bottom of the sidebar now show the same items in the same order with the same styling. Admin Utilities now appears under Admin on every portal.
• A new Help section offers Take the tour and Show Get started. Turn it off in System Settings → Core Features → Show Help in the account menu. It is on by default.
• Core Features now shows when a module is on but not reachable from any menu, with an Add it link. Nothing is added unless you click it.

Other changes

• Marketplace now starts off on new installs. It turns on during setup if you sell products or take payments online, or any time in Core Features. Portals that already use it are not affected.
• The floating "View portal as Sam" button is gone. View as Sam is on the finish screen, in the tour, on the Get started card and in Settings → General.
• Return to my account takes you back to the page you started from. Signing out while viewing as a client signs you out completely.
• A brand-new self-hosted install can sign in before setup has created the branded login page.
• The Calendar menu item gets its icon, including on portals set up before this release.
• The setup wizard no longer writes the words color or image into the login form's background colour, and portals where it did are repaired automatically.

v4.168.0 — October 5, 2026

ClientCove 4.168.0: managed portals open with sample content

Managed portals start with sample content

• New ClientCove Managed portals now open with a sample client, Acme Co., and a client user, Sam Sample, with a project in progress, a short message thread, a shared file and an open ticket. Everything is labelled Sample and worded for the kind of business chosen at checkout.
• Managed portals also start with the setup wizard's starter items, including a getting-started intake form for new clients.
• The setup wizard opens on "About your business" with your answer from checkout already filled in. Its Starter content section now shows which items are already in your portal, and applying the wizard never creates a second copy.
• Sample activity never notifies anyone: no emails, automations or in-app notifications are sent for sample records.

View portal as Sam

• Admins can click View portal as Sam (in the setup wizard's Finish step, the portal footer, or Settings → General) to see the portal exactly as a client does, then click Return to my account.
• It uses the existing View as User feature and only ever switches into the sample client. It never switches into a real client, staff member or admin.
• Sam Sample cannot sign in, reset a password or receive email. A message sent to Sam and others still reaches the others.

Remove sample data

• Remove sample data (setup wizard Finish step, or Settings → General) shows exactly what will be removed and kept before anything is deleted.
• It deletes the sample client, Sam Sample and all sample records, plus the starter items the portal came with that you have not changed or started using.
• Anything you edited or use is kept, for example an intake form that already has submissions. The internal team client is never removed.
• Removing sample data cannot be undone. The setup wizard can still add its starter items again, but not the sample client.

Self-hosted portals

• Nothing changes on update. No sample data is created on existing or self-hosted portals, and View portal as Sam and Remove sample data only do anything where sample data exists.

v4.167.1 — October 3, 2026

Magic-link sign-in is closed to the managed-hosting support account

• Fixed: on ClientCove Managed sites, the built-in support account could be sent a magic sign-in link like any other user. Magic links are no longer sent to it, and any existing link for it is refused. That account can now only be signed into through ClientCove's own one-time support access.
• Nothing changes for anyone else. Magic-link sign-in works exactly as before for every other user, and the sign-in page shows the same message whatever email is entered.

v4.167.0 — October 2, 2026

Client-only plans stay client-only, even when that client is in the trash

• Fixed: a plan or product assigned to a client became visible to every signed-in client while that client was in the trash, and could be bought by them. If it was also marked Show publicly, it appeared on your public pages too. It now stays restricted to that client, wherever it's shown or sold: the portal, checkout, guest checkout, the assistant and the Products Hub.
• The same applies when a client is deleted for good: their plans and products stay restricted rather than opening up to everyone. To make one available to others, open it in the Products Hub and remove the client.
• Saving a plan or product no longer quietly drops a client that's in the trash. The editor now lists trashed and deleted clients separately (for example "Acme (trashed)" or "Deleted client #12"). Uncheck one there to remove it on purpose.
• In the Products Hub, these items are labelled with the trashed client's name, or "Deleted client", instead of showing as Public, and the Embed option warns that they won't appear on other websites.

v4.166.0 — October 2, 2026

Plan and product pictures stay current on your public pages

• Replacing, editing or deleting the picture used for a plan or product now shows on your public product pages, product embeds and services page straight away. Before, the old or missing picture could stay for up to an hour.
• Turning the Marketplace back on in Core Features now always shows your plans and products as they are now, including any changes made while it was switched off.
• Nothing else changes, and there is nothing to set up.

v4.165.0 — October 2, 2026

Faster public product pages, and popups that sit above the sidebar

• Public product pages, product embeds, the public services page and guest checkout now load your list of plans and products once and reuse it, instead of rebuilding it on every visit. Pages with many plans and products load faster, especially on busy sites. Nothing changes in what visitors see.
• Changes still show up straight away. Saving a plan or product in the Products Hub, through the assistant, or anywhere else in the portal clears the saved copy immediately, so a plan you make private, inactive or client-only disappears from your public pages and embeds the moment you save it.
• Fixed: a plan or product assigned to a client could appear publicly while that client was in the trash, if it was also marked Show publicly. It now stays private. An item assigned only to a client you have deleted also stays private; clear its client to make it public again.
• Pop-up windows across the portal (for example New Group, Embed, Add User and the intake and contract editors) now always appear above the sidebar. Before, on narrower screens, the sidebar's menu, pinned list and chat box could cover part of the window.

v4.164.0 — October 1, 2026

Show your plans and products on any website

• In the Product Manager, open the ⋯ menu on any group or product and choose Embed. You get one line of code to paste into another website, such as your marketing site, and it shows that group or product there with your brand colour, prices and features. A group stays up to date: change its plans in the portal and every site it's embedded on shows the change.
• Buy and Subscribe buttons open checkout on your portal in a new tab, the same guest checkout your public pages already use. Checkout never runs inside the other website's page.
• Only plans and products that are public, active and not assigned to a client ever appear. If none in a group qualify, or a product isn't public, the embed shows a short "These products aren't available right now" message instead.
• Nothing appears on another website until you allow it. Add the site's address (for example https://acme.com) under "Sites allowed to embed" in the Embed window. Until then embeds only work inside your portal. The same list covers the support form embed under Tickets, so a site you allow there can show your products too, and the other way round.
• You can choose 1 to 4 columns for the embed. A group defaults to 3 and a single product to 1.
• The Embed option is shown to admins and tech staff, the same people who can manage the support form embed.

v4.163.0 — October 1, 2026

See who you're meeting, right on your calendar

• Click a meeting from your connected Google or Outlook calendar on the Calendar page and a details window opens: the time, the place, a Join button for the Meet, Zoom or Teams link, who organized it, every guest with their reply (going, maybe, not going, or no reply yet), the meeting notes, and a link to that day in Google Calendar or Outlook. Only you see your own meetings; clients never do.
• After you schedule a meeting from the portal and save it in Google Calendar or Outlook, coming back to the Calendar page now re-reads your calendar, so the new meeting shows up without waiting for the next automatic refresh.
• Coming next: connect your Google or Outlook account under My calendars and press Create meeting to add the meeting to your calendar, with a video link and invites sent from your own address, without leaving the portal. The Connect buttons appear on their own once this is switched on for ClientCove portals. Until then nothing changes, and scheduling a meeting works exactly as before.
• In My calendars, the button for adding a calendar's iCal address now reads "Add calendar address".

v4.162.1 — October 1, 2026

The assistant asks fewer questions

• "Set up a call next Tuesday at 2" now drafts the meeting straight away, even when it isn't about a project or client. You can add the details in your calendar before you send it.
• On ClientCove-managed AI, the assistant politely declines requests that have nothing to do with your work, such as poems, jokes, trivia or the weather, and offers something it can do instead. Help with writing, pricing, accounting, marketing and other business questions is still welcome.
• If the assistant ever comes back with an empty answer, it now tries again on its own, instead of replying that it had "no further comment".

v4.162.0 — October 1, 2026

A sharper assistant on ClientCove AI

• On ClientCove-managed AI, the assistant now acts on what's in front of you far more often. Ask it to send this invoice, run an automation by name, or list what's waiting, and it does the work instead of asking you for an ID or more details. In our testing it completed 51 of 57 everyday requests on the first try, up from 40 to 46 before.
• Answers can take about a second longer, while the assistant thinks before it acts.
• Nothing to set up. Sites that use their own AI provider key are unchanged.

v4.161.0 — October 1, 2026

Clear messages when the assistant can't answer, and a logo from day one

• If your site has used its AI allowance for the current period, the assistant now says so. It explains that the allowance renews with your plan, and that a site admin can see usage and add more under Settings → Subscribed Services. Before, it told you to check an API key you don't have.
• When ClientCove's AI service doesn't respond, the assistant asks you to try again in a moment and no longer mentions an API key. Sites that use their own AI provider key still get the hint to check it.
• A site with no uploaded logo now shows its name in the header, sidebar, login and checkout, with initials in the collapsed sidebar. Before, those spots showed a broken image or nothing. An uploaded logo always takes priority.

v4.160.0 — October 1, 2026

The assistant runs your automations by name

• Ask the assistant to "dry run the Weekly report automation" or "run New ticket triage now" and it finds the automation by name. You no longer need its ID. If the name fits more than one automation, it lists them and asks which one you mean.
• Behind the scenes, ClientCove-managed AI is ready for a faster way of calling the assistant's tools. It stays switched off for now while we make sure it is at least as accurate, so nothing changes in how the assistant behaves today.

v4.159.3 — October 1, 2026

Child theme: images and logo load correctly

• Sites running the ClientCove Child theme now load ClientCove's built-in images from the right place. Before this update, the fallback logo could disappear entirely, and the Login Designer preview images, the PDF icon in resource lists and the blank avatar on invoices could show as broken images. If you haven't uploaded a logo, upload one under Settings → Design: the login page has no built-in default logo to show.
• Nothing changes for sites that use the main ClientCove theme directly, and there's nothing to set up. Your own child-theme files and your generated custom styles stay exactly where they are.

September 2026

v4.159.2 — September 30, 2026

Agents: faster activity history for busy agents

• An agent's profile history, its Activity tab and its recent-activity lists now load quickly even when the agent has tens of thousands of logged actions. In testing, the first page of a busy agent's history went from about 150 ms to about 3 ms.
• The update adds one database index the first time the site loads after updating. It runs once, in the background of a normal page load, and nothing needs to be done. If it can't finish, the site keeps working as before and retries within an hour.

v4.159.1 — September 30, 2026

Agents: Profile button in the agent list

• Each agent in User Management → Agents now has a Profile button next to Details, Keyring and Token. It opens the agent's profile page, where you can see what the agent handles and everything it has done. Nothing else changes.

v4.159.0 — September 30, 2026

Agents: see everything an agent does on one page

• Every AI agent now has its own profile page. Open it from the agent's drawer ("Full profile") or the icon next to its name in User Management → Agents.
• The top of the page shows the agent's last 7 days: actions taken, how many of its drafts were accepted, how many you edited before publishing, what's waiting on you, and anything that was blocked.
• "What it handles" lists what the agent can do in plain words, grouped by area and marked Reads, Drafts for review, Acts live or Needs approval. It also shows which clients it covers and its standing instructions, plus one line on whether it can change anything live without asking.
• "What it's done" is a readable history. Each line names the ticket, project or invoice it touched and what happened next, for example "Drafted a reply → Edited, then published by Sam" or "Asked to send an invoice → Denied". Lookups are grouped into one line per sitting.
• "Needs you" lists the agent's pending requests and drafts, with a button to review them on the Actions page. You still approve and publish only from Actions, not from the profile.
• View as User on an agent now opens that agent's profile instead of switching you into it. Agents don't have a portal of their own, so there was nothing true to see there.
• The profile is for staff only. Clients never see agents or their profiles, and staff see only the agents they own, unless they can manage users.
• The page is read-only. Editing an agent, its tools and its tokens still happens in its drawer.
• Nothing changes on upgrade until someone opens a profile. No settings to turn on.

v4.158.4 — September 30, 2026

AI assistant: understands what you mean

• Refer to projects and tickets by number: "put Project 1026 on hold" or "what's the status of Ticket 1069" now find the right item. Confirmations show the item's real name, for example project 1026 "QA Empty Board Fix".
• "Send that to Jim" after the assistant writes something now sends that text, instead of asking what the message should say.
• Asking the assistant to write the content of a message you're about to send (a note, even a quote) now counts as writing help, so it writes it.
• Adding a card to a project board no longer asks which column when you don't say. It uses the board's first list and tells you which one.
• Draft message confirmations now show the text of the draft.

v4.158.3 — September 30, 2026

AI assistant: better with automations and email templates

• Asking for an automation (for example "when a new ticket comes in, draft an acknowledgement reply") now drafts steps that match what you asked. If a step isn't allowed in a drafted automation, the assistant says so before asking you to confirm, not after.
• "Do a dry run" or "test this automation" now previews each step without asking you to confirm, and nothing changes.
• Automation confirmations spell out day limits, for example "only on mon, fri".
• Rewording an email template ("make it friendlier") shows you the new wording for each part before you confirm.
• Asking for a new template ("write a welcome email for new clients") writes the whole template, no questions first.
• Email subject lines can't be changed from the assistant yet. It now tells you so instead of appearing to change them.
• Fixed: on sites using the included (managed) AI, requests with several parts, such as drafting an automation's steps, lost those details.

v4.158.2 — September 30, 2026

Schedule meeting: contractors can ask the assistant, and client meetings respect client assignments

• Contractors can now ask the assistant to set up a meeting, the same way they can already use the Schedule meeting button. They can start meetings for the projects they're assigned to and the conversations they're part of.
• Starting a meeting for a client now also requires that the person works for that client: team members who see every client are unaffected, and anyone assigned to specific clients can only prepare meetings, and see contacts, for those clients.
• Clients still never see Schedule meeting, and the portal still never creates or sends the meeting. You send it from your own calendar.

v4.158.1 — September 30, 2026

AI assistant: meetings open through the review button

• When you ask the assistant to set up a meeting, its reply now offers a single Review and open in your calendar button instead of listing Google Calendar and Outlook links. The button opens the meeting already filled in, so you can check the time, guests and agenda before it goes to your calendar.
• Nothing else changes: the portal still never creates or sends the meeting. You send it from your own calendar.
• Tools connected over MCP still receive the calendar links directly.

v4.158.0 — September 30, 2026

Schedule meeting: start a Google Calendar or Outlook meeting from the portal

• Your team can now start a meeting from a project, a client's Actions menu, a message thread, a day on the Calendar, or by asking the assistant (for example "set up a kickoff with Acme next Tuesday at 2").
• The meeting opens already filled in: a title from the project, client or conversation, the client's portal users or the people in the thread as guests, a short agenda, and a last line linking back to that page in your portal under your site's name. You can change any of it before you open it.
• Open it in Google Calendar, Outlook (work or school) or Outlook.com, or download an .ics file for Apple Calendar or desktop Outlook. The portal remembers the one you used last.
• The portal does not create, send or track the meeting. It opens in your own calendar, where you add Google Meet or Teams and press Send. Nothing reaches your client until you do.
• Times are shown in your own time zone.
• Only your team sees Schedule meeting; clients never do. There is nothing to set up, and nothing changes until someone clicks it.

v4.157.25 — September 30, 2026

AI assistant: automation confirmations describe the automation

• When the assistant sets up, changes or drafts an automation, the confirmation describes it. It says when it runs (for example "weekly on mon, fri at 09:00" or "when a ticket is created"), lists the steps in order, and names the client.
• If an automation would run destructive steps without asking, the confirmation warns you.
• New automations are still created turned off, for you to review and switch on.
• Setup and change confirmations appear about 3 seconds sooner.

v4.157.24 — September 30, 2026

AI assistant: safer ticket replies and clearer sends

• Fixed: asking the assistant to reply on a ticket number that doesn't exist could ask you to confirm a draft for a ticket that isn't there. It now tells you it can't find the ticket instead.
• Draft-reply confirmations now name the ticket.
• Before sending a message or email for you, the assistant shows who it goes to, the subject and the start of the text, and that it goes out as soon as you confirm. It also asks about 3 seconds sooner.

v4.157.23 — September 30, 2026

AI assistant: invoices, estimates and updates confirm clearly

• Before creating an invoice or estimate, the assistant shows the client, the number of line items, the amount (with tax rate and discount), and the dates. It says when a date is a default, and whether anything will be emailed.
• Changes to estimates, projects and clients are listed one by one, with people shown by name.
• Turning an automation on or off, or moving it to the trash, now names the automation.
• These confirmations appear about 3 seconds sooner.
• Fixed: asking to update something by a name that contains a number (like "Project 1026") could ask you to confirm a change to the wrong item. The assistant now finds the right one before asking.

v4.157.22 — September 30, 2026

AI assistant: clearer, faster confirmations for more actions

• When the assistant asks you to confirm a ticket reply, it now shows the words it will post and the ticket's title.
• Ticket updates list each change, for example "priority → High, due → 2026-10-02", with people and clients shown by name instead of by number.
• Confirmations for adding a user, creating a file, and invoicing billable hours now name the client and person.
• These, plus creating, updating or completing tasks, replying to several tickets at once, and discarding a draft, now ask for your YES about 3 seconds sooner.

v4.157.21 — September 29, 2026

AI assistant: works with newer Claude models

• Fixed: if your AI settings use a newer Claude model than the default, every message to the assistant failed with "The AI provider request failed". The assistant now works with the newer models too.
• Sites on the default model are not affected and need to do nothing.

v4.157.20 — September 29, 2026

AI assistant: faster confirmations

• When the assistant asks you to confirm something ("Needs your YES"), the question now appears about 3 seconds sooner. For example, sharing or moving files, drafting a reply, recording a payment, or creating an agent.
• The confirmation spells out exactly what will happen. Moving a file now names the folder it goes into.
• Nothing changes about how you confirm: type YES or use the button, as before.

v4.157.19 — September 29, 2026

AI assistant: share files with a client by asking

• Select files on the Resources page and ask the assistant to "send these to Acme". It shares them with that client after one confirmation, so they appear in the client's portal. Nothing is emailed.
• Sharing only adds access. Anyone who could already see a file still can. To remove access, use Assign on the file as before.
• If the client can already see all the selected files, the assistant says so and offers to let them know instead of asking you to confirm.
• After sharing, the suggested next step is to tell the client the files are there.
• Only staff can share files this way.

v4.157.18 — September 29, 2026

AI assistant: faster first reply when you come back

• If you step away from the assistant and come back within the hour, your first question is answered noticeably faster (about 2 seconds sooner in our testing). Before, anything longer than a five-minute pause made the next reply start from scratch.
• For sites using their own AI key, the AI usage page now prices this correctly.
• Nothing to configure.

v4.157.17 — September 29, 2026

AI assistant: see what it's doing while it works

• While the assistant works on a request, the chat now shows what it's doing, for example "Checking invoices…" or "Drafting reply…", instead of just a typing indicator. The final answer, the suggested next steps and any "Needs your YES" confirmation are unchanged.
• If the live progress connection is interrupted, the chat still shows the finished reply without running the request twice.
• When a client asks about their files ("where is my logo file?"), the assistant now looks in their own files straight away, so the answer comes back faster.
• Nothing to configure.

v4.157.16 — September 29, 2026

AI assistant: what it helps with, for your team and your clients

• Writing help for everyone: the assistant polishes or rewrites a reply, translates text, or helps word a message or question from a quick description. It no longer asks what you want to say first.
• Quick questions about math, accounting, IT, general business and marketing get a short, direct answer for both your team and your clients.
• Requests for a full plan or an in-depth consultation are pointed to you: clients are asked to open a ticket or send a message to your team, and staff are pointed to a specialist.
• Unrelated requests (poems, jokes, trivia, weather, general chat, medical or legal advice) get a brief, polite decline, now the same for staff and clients.
• Nothing to configure.

v4.157.15 — September 29, 2026

AI assistant: understands the page you're on, and writes what you ask

• On a client's page, the assistant now knows which client you mean. Requests like "invoice them for last month" or "what should I do next here?" work for that client without it asking "which client?".
• In a Messages conversation, short requests like "tell him thanks" now draft the reply in that conversation, instead of asking who to send it to or what to say. As always, a person publishes it.
• Questions about drafts now cover everything waiting in your Inbox, including drafts you wrote with the assistant and message drafts, so the assistant no longer reports a waiting draft as gone.
• Nothing to configure.

v4.157.14 — September 29, 2026

AI assistant: a tidier empty chat

• When the page you're on has its own suggestions (for example "Review 3 drafts" or "Draft a reply"), the empty chat now shows those first and fills the rest with your starter prompts, up to 4 buttons in total. Before, all of your starter prompts were stacked on top of the page's suggestions.
• On pages with no suggestions of their own, all of your starter prompts still show, as before.
• Nothing to configure.

v4.157.13 — September 29, 2026

AI assistant: what's waiting for you, and setting up agents

• Asking the assistant "what's waiting for me?" now lists every draft waiting in your Inbox, including ones you wrote with the assistant, along with any agent approval requests. Before, it could say nothing was waiting while drafts were still in your Inbox. It also answers faster.
• Describing the job you want an agent to do, like "set up an agent to handle my overnight ticket triage", now goes straight to a ready-to-review setup using the matching preset (Brief, Studio or Books), instead of a series of questions. As always, nothing is created until you confirm, and you can cancel or rename it.
• Nothing to configure.

v4.157.12 — September 29, 2026

AI assistant: move several files at once, faster answers

• In Resources, you can select several files and ask the assistant to move them into a folder. It moves them all with a single confirmation and tells you if any file couldn't be moved. Before, only one of the files was actually moved.
• If a request would need more than one confirmation at a time, the assistant now tells you so instead of silently dropping one of the actions.
• Questions like "how many open tickets do I have?" now get a short, direct answer, usually in about half the time. Before, you'd often get a long breakdown you didn't ask for.
• On a client's page, the "What needs doing" suggestion now gives the two or three things to do next for that client, faster and without other clients' deadlines mixed in.
• "Draft a reply" on a ticket writes the draft more reliably instead of asking what to say. As before, a person reviews and publishes every draft.
• Nothing to configure.

v4.157.11 — September 29, 2026

Security fix for ticket internal notes, AI assistant replies in Messages, and Empty Deleted Messages

• Internal ticket notes ("For technicians only") now stay with your team. Before, a client on a ticket could receive them in the ticket's data, its live updates and the "download all files" ZIP, even though the page hid them. Clients also no longer get a notification when your team adds an internal note.
• In Messages, asking the AI assistant to reply to an open conversation now drafts a reply inside that conversation. When someone publishes the draft from the Inbox or from Messages → Drafts, it's posted as a reply in that conversation, to everyone already in it. Before, it went out as a separate new message. Replies the assistant drafts are never sent without a person publishing them.
• A "Draft a reply" suggestion now appears when your team has a conversation open.
• In Messages → Drafts, a drafted reply shows which conversation it belongs to, and you can edit and send it without choosing recipients.
• New: an "Empty Deleted Messages" button permanently deletes everything in your Deleted folder after you confirm. Other people in those conversations keep their copies.
• Nothing to configure. We recommend installing this update promptly.

v4.157.10 — September 29, 2026

Security fix: client access to your internal records, and AI assistant wording

• Client users can no longer open your agency's own internal tickets, projects, invoices or estimates. Before, a client user could reach them through pinned items, the side panel or the AI assistant, even though the regular pages already blocked them. Your team, and anyone assigned to your internal client, keep their access. Clients can still find your team in search.
• When the AI assistant is waiting for you to confirm an action, its reply now always starts with "Needs your YES". Before, it sometimes said "Draft saved" when nothing had been saved yet.
• Nothing to configure. We recommend installing this update promptly.

v4.157.9 — September 29, 2026

Fix: the AI assistant on tickets

• The assistant now reads a ticket's full conversation. Before, it could only see the ticket itself, not the replies, so it could say a ticket had no replies when it had several.
• "Draft a reply" on a ticket now writes the draft from the conversation instead of asking what to say. As before, the draft waits for a person to review and publish it.
• Clients can no longer change a ticket's status or write internal notes through the assistant, matching what they can do on the ticket page. The assistant tells them so before asking them to confirm, and still posts their reply.
• When staff ask the assistant to reply and change a ticket's status, the confirmation now says which status it will set.
• Nothing to configure.

v4.157.8 — September 29, 2026

Fix: AI assistant suggestions and settings

• Starting a new conversation now refreshes the suggestions shown in the empty chat. Before, they could be out of date: for example, after you recorded a payment on an overdue invoice in the chat, a new conversation could still suggest "Record payment" on that invoice.
• Settings → AI Widget no longer shows the "Floating chat launcher" options. They had no effect since the assistant moved into the sidebar Chat view. The rest of the AI Widget settings are unchanged.
• Nothing to configure.

v4.157.7 — September 29, 2026

Fix: duplicate project numbers

• New projects now always get a number no other project has. Before, if some of your projects already had numbers higher than the last one the portal issued (for example projects that were imported or numbered by hand), the next project created could reuse one of those numbers.
• This applies to every way a project is created: the New Project form, building a project from an AI plan, and creating or updating a project through the assistant or connected AI tools.
• Existing projects keep their numbers. Nothing to configure.

v4.157.6 — September 29, 2026

Fix: an action waiting for your YES when you ask for something else

• When the AI assistant is waiting for you to confirm an action ("Needs your YES") and you ask it to do something different instead, it now drops the earlier action and tells you so. Before, the YES button stayed on screen and would still have carried out the earlier action, even though the conversation had moved on.
• Asking a question about the waiting action (for example "which ticket is this?") still keeps it waiting, and you can reply YES or CANCEL afterwards.
• Nothing is ever carried out without your YES, and there is nothing to configure.

v4.157.5 — September 29, 2026

Fix: deleting an AI assistant conversation

• Deleting a conversation from the assistant's chat history now also cancels any action that conversation was still waiting for you to confirm. Before, an action staged there (for example "Needs your YES") stayed pending for up to 15 minutes after the conversation was deleted.
• Clearing a conversation now removes it for good. Before, a cleared conversation could come back the next time it was opened.
• "New conversation" still keeps your previous chat in history, as before. Nothing to configure.

v4.157.4 — September 29, 2026

Fix: projects created or renamed by the AI assistant or a connected AI app

• A project created through the AI assistant or a connected AI app (such as Claude) now gets the next project number and shows its name on the Projects page, exactly like a project you create yourself. Before, it appeared in the list with no number and no name.
• Renaming a project through the assistant now changes the name you see. Before, the rename was saved somewhere the portal does not display.
• Projects already created this way without a number get one the next time the assistant or a connected app updates them. Projects that already have a number are never renumbered.
• Projects you create in the portal yourself are unchanged. Nothing to configure.

v4.157.3 — September 29, 2026

Fix: multi-line messages to the AI assistant

• When you pasted a list or a note with several lines into the AI assistant (or typed one with Shift+Enter), the line breaks were removed before the assistant read it, so it saw one long run-on line. Your message now reaches the assistant with its lines intact, and your own message bubble shows it the way you wrote it.
• Pressing Enter still sends the message; Shift+Enter still starts a new line.
• Replying YES or CANCEL to confirm an action works exactly as before. Nothing to configure.

v4.157.2 — September 29, 2026

Fix: the assistant's task count

• When you asked the AI assistant for your numbers (for example "how much is on my plate"), the task count it reported was always 0 or 1, however many tasks you had. It now reports the real number of tasks you created.
• Nothing else in the summary changed, and there is nothing to configure.

v4.157.1 — September 29, 2026

Fix: the assistant's summary counts for client users

• When a client user asked the AI assistant for their numbers (for example "how much is on my plate"), the project and resource counts it reported were totals for the whole portal, not for their own company. They now count only that client's projects and resources, the same way ticket and contract counts already did.
• Only the counts were affected: the assistant never listed or opened other clients' projects or files for them.
• Staff and admins are unchanged and still see portal-wide totals. Nothing to configure.

v4.157.0 — September 28, 2026

Tap a date on the Calendar page to create something there

• On the Calendar page, a single tap on any date now opens the create form on phones and iPad. Before, you had to press and hold for about a second.
• The form opens where it always has, below the calendar, and scrolls into view.
• On phones the Calendar shows Agenda, and each day heading now has a + that opens the form for that day.
• Nothing changes with a mouse: clicking a day, the form and its fields work exactly as before.

v4.156.0 — September 28, 2026

Tap a date on a client's Calendar tab to add a task, ticket or project

• On a client's Calendar tab, tap or click any date to add a task, ticket or project on that day for that client. The client is already filled in, and the date can be changed in the form.
• A single tap works on phones and iPad — no long-press needed. On phones the form slides up from the bottom; elsewhere it opens as a dialog. In Agenda view each day heading has a +, and the new Add button adds on today.
• Project now starts the project right there for this client, with the tapped date as its start date and an optional lead, board template and due date. Before, it sent you to the Projects page.
• The tab's filters work as before, and the main Calendar page is unchanged.

v4.155.1 — September 28, 2026

Fix: open a task from the My Tasks week view

• In the My Tasks week (calendar) view, clicking a task now opens it in the side panel, with your week still showing beside it. Before, clicking a task did nothing.
• Ticking a task's checkbox still just marks it done, and you can still drag tasks between days.
• Changes you save in the side panel now show up in My Tasks straight away, without reloading the page.

v4.155.0 — September 28, 2026

Tap a day to add a task in the My Tasks week view

• In My Tasks, switch to the week (calendar) view and tap any empty part of a day, including its date at the top, to add a task due that day. Before, only the small Add task row at the bottom of each day did this.
• Tapping a task, its checkbox or the open form works as before, and you can still drag tasks between days.
• On phones and iPad the Add task row and the form's buttons are bigger, and the title field no longer makes iPhone zoom in when you tap it.
• Nothing else changes: new tasks are still created with just a title, due on the day you tapped.

v4.154.0 — September 28, 2026

Tap a date to add a card on a project's Calendar and Timeline tabs

• On a project's Calendar tab and Timeline tab (Month and Week views), tap or click any date to add a board card there. A short New card form asks for a title and a list; the date is filled in and can be changed.
• The card starts and is due on that date and is assigned to you. Change anything on the card afterwards, the same as a card added on the Board.
• A single tap works on phones and iPad. In Agenda view, each day heading has a + to add a card on that day.
• Only people who can edit the project see this. View-only users and clients see no change.
• The main Calendar page and the client Calendar tab work exactly as before.

v4.153.0 — September 28, 2026

Calendar widget for dashboards

• The Calendar dashboard widget now shows your own work calendar — tasks, tickets and projects — in Month, Week or Agenda view, right on your dashboard. Drag an item to reschedule it, the same as on the full calendar.
• Tap any date to add a task, ticket or project on that day without leaving the dashboard. On phones the form slides up from the bottom; on iPad and desktop it opens as a dialog. A single tap works on touch screens — no long-press needed.
• On phones the widget shows Agenda view, with a + beside each day to add something there. The + Add button in the widget adds on today.
• New: start a project straight from the widget. Pick a client and, optionally, a lead, a board template and a due date — the tapped date becomes the start date.
• Dashboards that already had a Calendar widget (which showed "coming soon") now show the real calendar after this update. Nothing else changes until you add the widget.
• The full Calendar page works exactly as before.

v4.152.0 — September 28, 2026

Calendar icons for menus

• The menu icon picker (Settings → Menus → Choose Icon) now includes three calendar icons in the General group: Calendar, Calendar Event and Calendar Check.
• Search "calendar", "schedule", "event" or "booking" in the picker to find them.
• Nothing changes on upgrade — existing menu items keep their current icons until you pick a new one.

v4.151.1 — September 28, 2026

Clients page on phones

A small layout update to the Clients page on phones. Nothing changes on desktop or on upgrade, and there are no new settings.

• Card view: each client card lists its counts (Users, Locations, Assets, Resources, Projects, Tickets, Open Invoices) in two columns, and Created and Last login share a line. Cards are shorter, so you see more clients on one screen.
• List view: client logos are smaller on phones, so the client name and its counts have room instead of wrapping into a narrow column.

v4.151.0 — September 28, 2026

Delete forever for your own messages, and phone and tablet layouts across the portal

This release lets anyone clear a conversation out of their Deleted folder for good without affecting anyone else, and makes the main list pages, Messages and your Account page work properly on phones and tablets. Nothing changes on upgrade beyond what is listed here; there are no new settings.

Messages: deleting

• New: Delete forever. In Deleted Messages, every conversation now has Restore and Delete forever. Delete forever removes the conversation from your messages only. Everyone else in it keeps it wherever they have it: inbox, a label, or their own Deleted folder.
• Delete forever is not "delete for everyone". Before, only the person who started a conversation could permanently delete it, and that removed it for all participants. That option is gone from the conversation menu.
• A conversation is only removed from the system once every participant has deleted it forever.
• Delete forever only works from your Deleted folder. Delete still moves a conversation there first, and you can Restore it until you choose Delete forever.
• Delete and Delete forever no longer ask you to confirm. Delete is always restorable from Deleted Messages.
• Fixed: an empty Deleted folder could list all of your messages.

Messages: phones and tablets

• New message opens full screen, with the editor filling the space, the formatting toolbar at the bottom and Send beside Save draft. The fullscreen button is hidden below 1100px wide because the composer is already full screen.
• Reply opens as a panel at the bottom of the screen above the conversation. Before, the message bubbles covered it.
• "+ New" sits on the same line as "Back to Messages".
• Editing one of your messages opens full width.
• An expanded Google file preview uses the full width of the conversation.
• Deleted Messages rows show the date on the right like the inbox, with compact Restore and Delete forever buttons.

Messages: all screen sizes

• The To field shows its label inside the box, like Subject.
• Google file is an icon in the composer toolbar, next to Insert reference.
• In each message the date and time sit under the sender's name, and the person icon before the name is gone.
• The edit pencil on your own messages sits top right with Highlight and Create task, on the same line as your avatar, name and date.
• Google file names wrap between words instead of breaking mid-word.

Lists on phones and tablets

• Projects, Invoices, Estimates, Tickets, Assets, Locations and File Transfers show each row as a card on phones instead of a wide table you had to swipe. Every card shows all its details, with the actions on the card. Desktop keeps the table.
• File Transfers also shows cards on tablets, two per row, and whenever a pinned item leaves the list too narrow for the table.
• Invoices and Estimates: search stays on top and a Filters button opens Status, Client, From and To. The button shows how many filters are on.
• Projects on phones: the bulk-select checkboxes and the drag-to-category grip are hidden. Dragging onto a category needs a mouse, so the grip is also hidden on phones for Assets, Locations and Clients.
• Estimates: Create Template no longer runs off the screen.
• Fixed: the Invoices and Estimates "found" count ignored the filters. For example, it said "15 invoices found" while showing 2 drafts. It now counts what is shown.

Your Account page

• Profile and Security inputs and buttons are the same size as the rest of the portal. Before, they were oversized.
• Less padding around each tab, especially on phones.
• Overview values are no longer bold.
• On phones, Security shows each active session as a card with its Log Out button, and the Notifications Save and Reset buttons stay on screen.

v4.150.1 — September 28, 2026

Phone fixes for My Tasks, Tickets and pinned items

This release makes My Tasks, Tickets and pinned items work properly on phones, and fixes two bugs that also affected desktop. Nothing changes on upgrade beyond what is listed here; there are no new settings.

My Tasks on phones

• Each task's checkbox and title now have their own line. The time and date, and the ⋮ menu, sit on a second line below, so nothing runs off the edge of the screen.
• The ⋮ menu on each task opens toward the screen instead of off the right edge. This applies on desktop too.
• Filters show as a tidy two-column grid instead of a ragged centered stack.
• Bulk Edit has a compact toolbar: the number of tasks selected with an X to exit, and small Complete, Due Date, Client, Archive and Delete buttons. Before, most of these buttons were cut off on phones.
• Quick Add opens full screen on phones, covering the header, with Cancel and Create at the bottom.
• The Archived and Trash banners wrap properly instead of squeezing their text into one word per line.

Assigning a client to a task

• Assign Client is now a list of clients you tap, with a search box when there are more than six. One tap assigns the client and closes the window. It replaces the dropdown, which opened as a scroll wheel on iPhone.
• Fixed: choosing No client never saved, so a client could not be removed from a task once assigned. It now removes the client. This affected desktop too.

Tickets

• Fixed: on phones, the Tickets page could not scroll while a pinned item was open. This affected any page on a phone with a pinned item open.
• The Filter menu opens toward the screen instead of off the right edge, and on phones the Columns, Sort by and Filter buttons wrap to fit. The Assets page gets the same fix.
• On phones, each ticket's subject and client fit on screen. Swipe sideways to see the other columns, as before.
• Removed extra side padding on the Tickets page so it lines up with the rest of the portal.
• Fixed: the Priority editor in ticket details opened blank for tickets submitted through an embedded form. If you saved without choosing again, the priority was cleared. It now opens showing the ticket's current priority.

Pinned items on phones

• A pinned item opens just below the header and fills the screen to the bottom. Before, the header covered its top and the page showed through underneath.
• The Item and Page switch stays at the top of the screen when you view the page, so you can always switch back to the item. The item is not reloaded when you switch, so you keep your place and any unsaved edits.
• Tapping a pinned item that is already open brings you back to it from the page view.
• The Item button shows a pin icon.
• Long card titles in a pinned project card now wrap in full instead of being cut off.

v4.150.0 — September 28, 2026

New: see your Google or Outlook meetings on the Calendar

• Staff can connect their own Google Calendar or Outlook calendar from the new My calendars button on the Calendar page. Paste the calendar's private iCal / ICS address and your meetings appear beside your tasks, tickets and project dates, as violet items with their start time.
• Meetings are read-only. ClientCove never creates, changes or deletes anything in Google or Outlook, and meetings can't be dragged to another day. Change them in the calendar they came from.
• Meetings are private. Each person sees only their own, including managers in Team view. They never appear on a client's Calendar tab, a project's Calendar, dashboard widgets, or anywhere clients can see.
• Choose Meetings in the Type filter to see only meetings. All types includes them.
• Up to 5 calendars per person. Calendars are re-read about every 15 minutes, and the Refresh button in My calendars picks up changes sooner. Google itself can take several hours to publish changes to its iCal address.
• Clear messages when an address doesn't work, including how to fix a Google address that was reset or isn't shared.
• Nothing changes on upgrade: no one sees meetings until they connect a calendar themselves.

Guide: https://docs.clientcove.io/tasks/calendar-meetings

v4.149.0 — September 27, 2026

Tips on new team dashboards

• New dashboards for your team now start with the Tips widget. This applies to dashboards you create in the dashboard builder and to the admin and rep dashboards the setup wizard creates.
• Your existing dashboards are not changed. Add the Tips widget to them from the dashboard builder if you want it.
• Dashboards for clients never get the Tips widget: that means dashboards assigned to a client, or assigned only to client roles. Clients never see tips on any dashboard.
• You can remove the Tips widget from any dashboard in the dashboard builder, like any other widget.
• Developers can turn this default off from a child theme with the cove_tips_default_on_new_dashboards filter.

Image banner tips

• Tips can now be a single image banner. The whole image is the tip, and clicking it opens the linked page or plays the video.
• Screen readers read the tip's title and description, which are not shown on the image.
• The × button to dismiss a tip sits in the image's top-right corner.

v4.148.1 — September 27, 2026

Theme updates start with one click

• In Settings → License, clicking Update Now starts the update straight away. The "Install the ClientCove update now?" pop-up is gone.
• While the update installs, the button shows "Installing... the site may be briefly unresponsive". The page reloads on its own when the update finishes.
• Deactivating a license still asks you to confirm first, because it stops updates.

v4.148.0 — September 27, 2026

New: Tips dashboard widget

• A new Tips widget shows short how-to tips from the ClientCove team, one at a time, with images and short videos. Add it to any dashboard from the dashboard builder (it is listed as "Tips").
• Nothing changes on upgrade: the widget does not appear anywhere until an admin adds it to a dashboard.
• Only your team sees it. Clients never see the Tips widget, even on a dashboard that has it.
• Tips rotate every 8 seconds by default. In the widget's settings you can turn off "Rotate automatically" or set "Seconds between tips" (5 to 30). Rotation stops for the rest of the visit as soon as someone uses the arrows or dots, and never runs for people who have reduced motion turned on in their device settings.
• Each person can dismiss a tip with its × button. Dismissing hides it only for that person, and it stays hidden. When someone has dismissed every tip, the widget says "You're all caught up".
• Video tips open in a pop-up player (YouTube, Vimeo or Loom). Close it with Esc or the × button.
• Some tips have a button that opens a page in your portal, or a ClientCove page in a new tab.
• Tips come from account.clientcove.io. Your site checks for new tips about every 15 minutes, and only while someone is viewing a dashboard that has the widget. The request carries your theme version and the standard details WordPress includes in any outgoing request, such as your site address. It carries nothing about your users, clients or content. If account.clientcove.io can't be reached, the widget keeps showing the last tips it received.
• Admins see a "Refresh tips" button under the widget to check for new tips right away.

Fix: deleting a folder on Resources

• Deleting a folder now also deletes its subfolders and its Workbench. Before, they were left behind at the top level.
• Files inside the deleted folders are not deleted. They move to the deleted folder's parent folder, or become unfiled if you deleted a top-level folder.
• A Workbench left behind at the top level by the old behavior can now be deleted from its menu.
• The confirmation message now says that subfolders and the Workbench are deleted too.

v4.147.0 — September 27, 2026

Links to transfers and transfer tabs

• When you open a transfer on the File Transfers page, the address bar now shows a link to it (for example /transfers/?transfer=23). Copy or bookmark it to go straight back to that transfer.
• The Sharing and Requesting tabs have their own links too: /transfers/?tab=sharing and /transfers/?tab=requesting. The All tab is plain /transfers/.
• Your browser's Back and Forward buttons now move between the transfer list, its tabs, and the transfers you opened, instead of leaving the page.
• After you delete a transfer, Back returns to the list, not to the deleted transfer.
• The "View transfer" links in transfer emails work the same as before.
• Links that open the send or request form (/transfers/?action=send or ?action=request) still open it. The address bar then returns to /transfers/, so reloading the page doesn't open the form again.

v4.146.0 — September 27, 2026

Messages on tablets and smaller laptops

• On screens between 992 and 1299 pixels wide, clicking a message in the list now opens it. Previously the page showed one column at these widths but clicking a message did nothing.
• The open message fills the column beside the menu, and "Back to Messages" returns to the list. The reply box opens in the same column.
• A new "New" button next to Contacts, above the message list, starts a new message. It shows at every screen size.
• On phones and on screens up to 1299 pixels wide, the Messages page opens your last-viewed message, as it already did on phones. Wider screens are unchanged.

Menu on phones and tablets

• When you open the menu on a phone or tablet (below 992 pixels wide), it now has a solid background. Previously, with a background gradient set in Design, the page showed through the menu.
• The menu now scrolls as one list: all menu items, then Pinned, then Search, Notifications, and your name. Previously the Pinned list took most of the height and cut the menu items off.
• The menu on wider screens is unchanged.

Page spacing on smaller screens

• Below 992 pixels wide, page titles line up with the content under them instead of being indented.
• Below 768 pixels wide, page content runs to the edges of the screen. Previously this started below 576 pixels.
• Between 768 and 1400 pixels wide, the space on either side of page content is narrower (about 8 pixels instead of 20–24), giving pages more room. Wider screens are unchanged.

v4.145.0 — September 27, 2026

Settings on phones and narrow screens

• The tabs inside Settings → Managers (Clients, Dashboards, Invoices, and the rest) and Settings → Menus (Administrator Menu through Menu Priority) now fit their row. When space runs short, the tabs you are not on shrink to icons, then the last ones move into a "More" menu. The tab you are on keeps its name and never moves into the menu.
• Managers tabs no longer wrap onto several lines.
• Action buttons on every Settings tab (Save, Deactivate License, Test Connection, and the rest) are smaller: the same size as the search and filter buttons on list pages. Small buttons and buttons attached to a text field keep their size.
• On phones, rows of buttons wrap onto the next line instead of running off the edge of the screen. The License tab's three buttons now stack.
• On phones, the Services "Add to plan" button, the Global Tags Save button, and the General timezone dropdown now fit the screen. Previously they were wider than a phone screen.

Resources

• The search box and Filters button are smaller, matching the search and filter bars on other list pages. They stay side by side on narrow screens; the search box gets narrower instead of Filters moving to its own line.
• The search icon now sits inside the search box, instead of looking like a separate button.
• The Date and A-Z sort buttons are smaller.

Search boxes with an icon or button attached

• A text field joined to an icon or button (for example a search box with its magnifier, or a field with a Copy button) no longer shows rounded corners where the two meet. Your Form Fields corner setting in Design still applies to the outside corners. This takes effect when the update installs; you don't need to re-save your Design settings.

v4.144.0 — September 27, 2026

User Management tabs fit narrow screens

• On phones, or when a side panel is pinned, the Client Users, Contractors, Techs & Staff, Permissions, and Agents tabs shrink to icons, with each tab's count shown as a small badge on its icon. The tab you are on keeps its name.
• If the tabs still don't fit, the ones that don't fit move into a "More" menu. The tab you are on never moves into the menu.
• This works the same way as the tabs on a client's page, on My Tasks, and on project pages. Nothing changes on wide screens.

Search and filter bars look the same on every list page

• On Projects, Tickets, Clients, Locations, Assets, Dashboards, Estimates, Invoices, Intake Manager, Contracts, Agreements, Email Campaigns, App Integrations, and User Management, the search box, filters, and buttons in the bar above the list are now all the same height and text size.
• On narrower screens the search box moves onto its own full-width line above the filters. Filter dropdowns stop at a set width, so a long client name no longer squeezes the search box.
• On phones, the buttons next to a page's title now wrap under the title instead of running off the right edge.

Fewer false email deliverability alerts

• Email addressed to reserved test domains (such as .test, .example, .invalid, .localhost, .local, .demo, and example.com) is no longer sent. The email log still shows the message, marked as failed with the reason.
• The daily "Email deliverability alert" now names the newly blocked addresses instead of just giving a count, and it ignores test-domain addresses.
• Email to real addresses is sent exactly as before.

v4.143.0 — September 27, 2026

Create tasks and tickets from the Calendar with more detail

• Clicking a date on the Calendar opens a smaller, tidier form that matches the buttons and fields on project pages.
• New Notes field. On a task it becomes the task's notes. On a ticket it becomes the ticket's opening message.
• New "Relate to" option: link the new task or ticket to one project, asset, or location. The search only shows items that belong to the chosen client.
• If you pick a related item before choosing a client, the form fills in that item's client. An item that belongs to a different client can't be linked.
• "Assign to" now lists every staff and tech user, plus the chosen client's own users. Previously it only listed people who already had work showing on the calendar.
• The client list now shows every client, not only clients with work in the visible dates.
• Projects are still created from the Projects page, not from the Calendar.
• Opening a ticket from the Calendar still emails staff right away and still asks you to confirm first.

User Management on phones and narrow screens

• On phones, or when a side panel is pinned, each user on the Client Users, Contractors, and Techs & Staff tabs now shows as a compact card: name, email, and Actions on top, with role, clients, added by, last login, and date added underneath. Previously each user filled most of the screen.
• The search box and client filter go full width on phones. Nothing changes on wide screens.

Crew Dashboard

• The Crew Dashboard no longer sits on a white panel; the page background shows through, as on other pages.

v4.142.0 — September 27, 2026

Turning off the Knowledge Base now fully turns it off

• Behavior change: when the Knowledge Base is turned off in Settings → Core Features, it is now unavailable everywhere, not only hidden from the menus. Nothing changes on sites where the Knowledge Base is on.
• The Knowledge Base page shows a "Feature Currently Unavailable" message instead of your articles.
• Opening an article link shows the same message to signed-in users. Visitors who are not signed in get a "page not found", including for articles marked public.
• The public support page stops suggesting articles, but people can still open a ticket from it.
• The AI assistant can still answer from the official ClientCove guides if that source is on under Settings → Knowledge Base.

Easier to turn features back on

• When admins open a page for a feature that is turned off, such as the Knowledge Base, Estimates, or Automations, the message now includes a "Turn On in Core Features" button. Other users still see the same message without the button.

v4.141.1 — September 27, 2026

Fixes

• Settings → Knowledge Base: when the Knowledge Base is turned off in Core Features, the warning on this tab now correctly says it is hidden from the menus. It previously said the Knowledge Base page itself was hidden, but that page can still be opened by its address. Nothing else changes.

v4.141.0 — September 27, 2026

Knowledge Base settings

• New Settings → Knowledge Base tab for admins. It holds the official ClientCove docs source, who sees those docs, who can write articles, and which audiences new articles start with. The Knowledge Base on/off switch and its name stay in Core Features.
• The official ClientCove docs switch moved here from Settings → AI. Settings → AI now shows whether it is on and links to the new tab.
• Who can write articles: Admins always can. By default System Admins and Tech Admins can too, as before, and you can now add other staff roles. Client roles cannot write articles.
• New articles start visible to Admins, Staff, and Client Users, as before, and you can now change that default. Existing articles are not changed, and authors can still set the audience on each article.

Official ClientCove docs: on for your team, never for clients

• The official ClientCove how-to guides are now on by default for sites that have never changed this setting. Staff can search them in the Knowledge Base and the AI assistant can answer "how do I…" questions from them. If you turned the docs off before, they stay off.
• The guides are shown only to the roles checked under "Who sees the docs". Admins always see them, other staff roles see them by default, and clients and logged-out visitors do not.
• Behavior change: on sites that had the docs switched on, clients could see the ClientCove guides and the "System" tab in the Knowledge Base. They no longer can, unless you check their role under "Who sees the docs".
• The guides stay on docs.clientcove.io. Nothing is copied into your Knowledge Base.

Crew Dashboard

• The Crew Dashboard no longer draws its own colored background behind the page and crew list. It uses the same background as the rest of the portal, including in dark mode.

v4.140.0 — September 26, 2026

AI controls only appear when AI is connected

• AI features now show only when an AI provider is actually connected: a Current plan, your own API key, or a WordPress AI connector. Until then, the sidebar Chat view, the chat button on the collapsed sidebar, "Draft with AI" in the Knowledge Base editor, message polish, ticket assist, voice, and the AI summary widget are hidden instead of showing controls that could only fail. Nothing changes on sites that already have AI connected.
• Turning on "AI features" in Core Features alone no longer shows these controls; a provider must also be connected under Settings → AI.
• Search stays available without AI and falls back to keyword search. The Actions menu item stays visible whenever agents exist or approvals are waiting, since agents can connect from outside (for example Claude over MCP) without in-app AI.
• Admins without AI connected see a small note in the Knowledge Base editor linking to Current Wave or to Settings → AI to connect their own key. Other users see nothing.
• The AI Assistant dashboard widget now tells you when no provider is connected, instead of pointing you to the Core Features toggle.

Fixes

• User Management: after adding a user, the page now opens on that user's tab (Techs & Staff, Contractors, or Client Users) instead of switching back to another tab.
• File Transfers: the "Configure Cloud Storage" button now opens Settings → Storage. It previously reloaded the File Transfers page.

v4.139.0 — September 26, 2026

Housekeeping

• The "Notification Expiration System — Complete Installation" notice no longer appears in wp-admin, and the hidden installer page it linked to has been removed. It was never required: automatic cleanup of old notifications and the Settings → Notifications page work without it, and nothing about how or when notifications are cleaned up changes with this update.
• If you ran that installer before, the database indexes it added stay in place and keep working. Nothing needs to be done on upgrade.

v4.138.3 — September 26, 2026

ClientCove 4.138.3 fixes an error in the billing triage assistant tool introduced in 4.138.2.

AI tools

• The "surface billing triage" tool no longer fails with an error on sites that have the Tickets feature turned off but still have older tickets. This only affected 4.138.2. Sites with Tickets turned on were not affected.

What changes on upgrade

• Nothing needs setting up.

v4.138.2 — September 26, 2026

ClientCove 4.138.2 fixes tickets created from a project card, and gives the project loading screen your accent colors.

Tickets

• Tickets created with "Create ticket from card" no longer fail to open. Some of these tickets showed an error instead of loading because their activity history was saved in the wrong place. Affected tickets are repaired automatically the next time they are opened, and all of them are repaired the first time a staff member visits wp-admin after the update. No history is lost.
• A card's images and files are now attached to the ticket made from it, instead of being linked in the ticket's description. The old links stopped working a week after the ticket was created. Attachments keep working for as long as the file is stored.
• Tickets made from a card before this update keep their old description links, which may already have expired. Only new tickets get attachments.
• The ticket's internal staff history now records every entry. Before, most entries were silently dropped. It is still visible to staff only, never to clients.

Projects

• The "Loading project" screen now uses your App Designer accent gradient when one is set for the current light or dark mode. With no accent set, it keeps the plain page background.
• In dark mode the loading screen no longer flashes white before a project opens.

What changes on upgrade

• Nothing needs setting up. Damaged tickets are repaired automatically, as described above.

v4.138.1 — September 26, 2026

ClientCove 4.138.1 lines up page titles across the portal.

Layout

• Page titles and their breadcrumbs now sit indented inside the page's content column on every page, the way they already did on My Tasks. Before, most pages (Resources, Tickets, Actions, Projects, Clients, Invoices, Contracts, Calendar and others) showed the title flush against the left edge, out of line with the content below it.
• This applies on screens 769px wide and up. On phones and narrow windows, titles stay where they were.

What changes on upgrade

• Nothing needs setting up.

v4.138.0 — September 26, 2026

ClientCove 4.138.0 fixes message attachments that stopped opening after a week, makes Download All include every file, and gives each message thread its own link.

Fixes

• Fixed: files attached to a message stopped opening about seven days after they were sent, showing an "access denied" or expired-link error. Attachments now get a fresh secure link every time the thread is opened, so they keep working. This includes files attached before this update. You don't need to re-upload anything.
• Fixed: "Download All" on a message thread could produce a zip with fewer files than the thread had. Files with similar names overwrote each other, and files that couldn't be fetched were left out without a warning. Every file is now included under its full name, and if any file can't be fetched you'll see "Downloaded X of Y" instead of a success message.
• Attachment links are still private and time-limited. A fresh link is only created for someone who can already open the thread, and it expires after 24 hours.

New

• Each message thread now has its own address. When you open a thread, your browser's address bar shows it as /messages/?message_id= followed by the thread number, so you can bookmark it or share it with a teammate. The browser's Back and Forward buttons move between the threads you've opened.
• Sharing a thread link does not give anyone access to it. People who aren't part of the conversation still can't open it.
• Notification links now open the right thread even when it's under a different filter or further down your list.

What changes on upgrade

• Nothing needs setting up. Existing attachments start working again the next time their thread is opened.

v4.137.3 — September 26, 2026

ClientCove 4.137.3 is a small reliability fix for automations.

Fixes

• Fixed: sending a portal message, and saving some other records, wrote "Array to string conversion" warnings to your site's error log. The automations check that watches for status changes no longer reads unrelated fields.
• Fixed: in rare cases, that same check could stop a save with an error when a record stored a complex value. It now ignores those values.
• Automations that start on an invoice being paid, an estimate being accepted, declined or viewed, or a task being completed work exactly as before. No automation ran or was skipped because of this bug.

What changes on upgrade

• Nothing needs setting up.

v4.137.2 — September 26, 2026

ClientCove 4.137.2 carries your Accent Gradient into Messages, so the messages you send pick up the same tint as the rest of your design.

Messages

• Your own message bubbles on the Messages page now use the App Designer's Accent Gradient, running from its first color at the top to its second at the bottom. The colors are softened to 30% strength so text stays easy to read.
• Light and dark mode each use their own accent, the same as the Process, Status and Board views.
• Messages from other people are unchanged. They keep their plain card background.

What changes on upgrade

• Nothing, unless you have chosen an Accent Gradient. Until you choose one, your message bubbles keep the same solid tint of your primary color as before.

v4.137.1 — September 26, 2026

ClientCove 4.137.1 makes the "makes a promise" check on drafted client messages more accurate, so routine notices can auto-send and "it's fixed" claims always get a second look.

Drafts: "makes a promise"

• A drafted message is now flagged makes a promise only when it commits your firm to something it could later fail to keep: a future date or deadline, a promised action or refund, a guarantee, or a claim that a problem is fixed or resolved.
• Notices that something is ready, posted, uploaded or received, such as "your files are ready in Files" or "your invoice is posted", are no longer flagged. Before, they often were, which kept them waiting for a person and stopped them from auto-sending.
• Messages that say a problem is fixed or resolved ("the outage is resolved") are now always flagged for a person to check. Before, some slipped through.
• This affects drafts saved from now on. Drafts already waiting in Actions keep their existing flags.

What changes on upgrade

• Nothing needs setting up. Auto-send stays off unless an administrator has turned it on in Settings → Integrations → AI Connection → Draft auto-publish.

v4.137.0 — September 26, 2026

ClientCove 4.137.0 lets routine client drafts send on their own (off by default), and gives the App Designer accent gradients, gradient fine-tuning, border radius controls and new blue palettes.

New: Auto-send for routine client drafts (off by default)

• Every client-facing draft is now sorted when it is saved: either it needs a person, or it is routine and could send on its own. Actions shows which, and lists every reason a draft needs a person.
• A draft always needs a person if any of these apply: a risk flag was raised, it is not addressed to exactly one person, the client is new (under 30 days), it is the first staff reply on a ticket, the ticket is urgent, the message is signed by a named person, or it was edited in Actions. By default only portal messages can be routine; email drafts always need a person unless you change that setting.
• To turn auto-send on, an administrator chooses Also: routine client drafts send on their own after a delay in Settings → AI → Draft auto-publish. The delay is 0 to 30 minutes, 5 by default.
• While a routine draft is waiting it shows under Sending soon in Actions with the time it will send, and you can Hold it. Sent drafts show as "auto-sent as" the person they were sent as.
• Turning auto-send on does not release a backlog. Only drafts saved after you switch it on can send on their own.
• Every draft is checked again right before it sends. If anything has changed, it is held for a person with the reason shown. It is never sent anyway and never silently dropped.
• New per-client switch: Never auto-send to this client, under the client's Contacts → Manage Default Assignees. Use it for clients who should always get a personal reply.
• The Actions badge and the Your Week "Waiting on you" number now count only drafts that need you. Routine drafts are listed after everything that needs a judgment.
• Settings → AI → Draft auto-publish now shows the last 30 days of client-facing drafts: how long clients waited, how many were published without edits, and how many would have sent on their own.

App Designer

• New Accent Gradient: sets the tinted wash on the current stage in a project's Process and Status views and on the Board's list columns. Choose from six presets, separately for light and dark mode. Until you choose one, these surfaces look exactly as before.
• Two new background gradients: Deep Blue and Blue Gray.
• Turning a background gradient off is easier: click the selected gradient again, or choose None. Choosing None now clears a saved gradient from the live preview too.
• The Color Editor can now fine-tune both gradients for each mode: start, middle and end colors plus the angle for the background, and a tint and fade color for the accent. Editing any of these switches that gradient to Custom.
• New Border Radius section with sliders for the dock (Cove Dock layout only), cards, buttons and form fields. Buttons with their own shape, such as pill and icon buttons, keep it. Nothing changes until you save the design. After the first save, standard buttons round from 7.6px to 8px unless you move the slider.
• Three new Quick Start palettes, each with a matching dark version: Cobalt, Sky Blue and Blue Slate.
• The designer panel is reorganized: Theme Mode now sits under Layout Style, and Logo Settings, Content Area Spacing, Border Radius, Quick Start Palettes, Gradients and the Color Editor are all collapsible sections that remember whether you left them open.
• Settings → Design: the Open App Designer and Open Login Page Designer buttons now use your primary color.

Projects

• The current stage in the Process view no longer has an accent bar on its left edge. It is still marked by its tinted background and filled step number.

Fixes

• Fixed: after a database restore or import, publishing or discarding a draft in Actions could fail every time. The theme now detects the mismatch and repairs its drafts table on its own.

What changes on upgrade

• Auto-send is off. No draft sends on its own until an administrator turns it on.
• Your design is unchanged until you save it in the App Designer. No accent gradient or border radius override applies until then.

v4.136.0 — September 26, 2026

ClientCove 4.136.0 adds a Your Week dashboard card for staff and fixes who a drafted message is sent to.

New: Your Week dashboard card

• A new Your Week card shows each staff member their own week, Monday to Sunday: items waiting on them in Actions, their tasks due (and overdue), open tickets assigned to them (and how many are unanswered), and their calendar through Sunday. Each number links to its page.
• A heat reading at the top, Quiet, Steady, Busy or Heavy, adds those numbers up so a full week stands out at a glance. Overdue tasks and unanswered tickets count double. It is a simple total, not a prediction.
• The first three items waiting in Actions are listed with a direct link to each one.
• Client activity shows what the clients you work with did in the last 7 days compared with the 7 before: tickets opened, ticket replies, portal messages and file changes, plus the most active clients. "Clients you work with" means clients where you are the Primary Contact, plus clients of open tickets assigned to you. Administrators can switch to all clients. Your own team's activity is never counted.
• The card is not added to any dashboard automatically. An administrator adds it once in the dashboard builder, and everyone who sees that dashboard gets their own week. Client users never see it.

Dashboard builder

• Fixed: the Your To-Dos and Next 7 Days widgets now appear in the builder's Widget Library. Before, they could not be added from the builder at all. Existing dashboards are unchanged.

Fixes

• Fixed: a drafted message addressed to one person by name was sent to every user of that client when published. It now goes only to the named person. If the name matches nobody, or more than one person, publishing is refused and the draft stays waiting, so nothing is sent to the wrong people.
• The Actions preview now shows that named person as the recipient, or explains why publishing will be refused.
• Fixed: the Actions page now uses the standard page layout, with the page title, breadcrumb and full-width content, like every other page.
• Fixed: the Download permissions JSON link under User Management → Permissions → Import/Export returned an error instead of downloading the file.

What changes on upgrade

• Nothing needs setting up, and no dashboard changes on its own. To use Your Week, add it to a dashboard in the builder.

v4.135.0 — September 26, 2026

ClientCove 4.135.0 adds an Actions page and makes AI agents simpler to manage.

New: Actions

• A new Actions page, in the user menu directly under Messages, gathers everything AI agents and your own assistant have prepared for a person to decide. A count badge shows how much is waiting for you.
• Each item opens in full beside the list, so you read the whole message, reply or task before you publish it. Previously only a one-line summary was shown.
• You can fix the wording of portal messages, ticket replies and tasks before publishing. Messages written in the Messages composer are still edited in Messages. Other draft types can be published or discarded, not edited.
• What is published is exactly what you saw. If the draft changed after you opened it, Actions stops and asks you to review it again instead of sending the new version.
• For portal and email messages, Actions shows what will actually be sent: the final text and the real recipients. A message whose recipients do not match its client is refused and should be discarded.
• The Done tab keeps 30 days of decisions: what was published, approved, discarded, denied, expired or cancelled, and who decided. Anyone who can decide an item can mark it Checked as a spot-check. Checking is optional and never blocks anything.
• Administrators see their own items by default and can switch to All to see every agent's items.
• The inbox has moved: the Inbox section on User Management → Agents is replaced by a link to Actions, and links that used to open the inbox now open Actions.
• Actions is available to staff only. Client users never see it.

Agents: simpler lifecycle

• Revoking an agent is now final. Restore has been removed: a restored agent came back with no tools and no tokens, which was the same work as creating a new one. To replace an agent, create a new one.
• Revoking an agent now also discards its unpublished drafts. Its history stays on record.
• An agent that has never been connected and has no activity can now be deleted outright from its details panel. Any agent with history can only be revoked, so its audit trail is kept.
• The agents list now opens on Current, meaning active and paused agents. Revoked agents are under the Revoked filter.
• Agents can no longer be deleted from the Users list, in bulk, or from the WordPress admin. Use the Agents tab instead.

What changes on upgrade

• Nothing needs setting up. The Actions page is available at /actions/ as soon as the update installs.
• The first time you open the Done tab, drafts published in the last 30 days appear as unchecked. You do not need to check them.
• If your site already has a WordPress page with the address "actions", the new Actions screen takes over that address. Administrators see a notice on the Dashboard and Pages screens; rename that page's address to keep it reachable.

Fixes

• User Management → Permissions no longer shows errors in the browser console when the tab loads.

v4.134.0 — September 25, 2026

v4.134.0

Messaging contacts

• Fixed: System Admins now appear in the Contacts panel on Messages. Before, the System Administrators section only listed Administrators and Editors, so anyone with the System Admin role was missing, for staff and clients alike. System Admins assigned to a client now also show under that client's Account Managers.
• System Admins see every client in their Contacts panel, like Administrators and Editors. Before, they got the client-style view.
• This changes who is listed in the Contacts panel, not who can be messaged.
• Upgrade notes: nothing to do.

v4.133.0 — September 25, 2026

v4.133.0

Messaging security

• Fixed: clients can only message the people in their contacts. Before, the contacts list only limited who clients could pick in the composer. Someone sending requests directly could message any user on the site. The server now checks every message against the sender's contacts and refuses anyone outside them with "One or more recipients cannot be messaged from this account."
• Replies stay inside the conversation. Only people already in a conversation can reply to it. Reply and reply-all to people already in the conversation keep working, even if one of them has since left your contacts (for example, a reassigned account manager). A reply can add new people only from your contacts.
• Staff are not affected. Administrators, System Admins, editors, tech and sales roles can still message everyone.
• Upgrade notes: nothing to do. The message composer, project messages and message drafts work as before.

v4.132.0 — September 25, 2026

v4.132.0

Messaging contacts

• Fixed: newly added users now appear in everyone's contacts. Before, people added to a site (for example new System Admins) didn't show up in existing users' message contacts. The Administrator couldn't find them, and each new user only saw the people who already existed when they were added. Adding or removing a user, changing someone's role, or changing which client they belong to now refreshes everyone's contacts.
• Staff see all staff. Administrators, System Admins, editors, tech and sales roles see every user in their contacts. Contractors now also see other contractors, along with the rest of the team and their assigned clients' users.
• Fixed: moving a user to a different client now removes them from the old client's contacts.
• Upgrade notes: nothing to do. Every user's contacts refresh the first time they're used after updating, so people added before this release appear too.

v4.131.0 — September 25, 2026

v4.131.0

Invoices

• Paid invoices lock what was billed. Once an invoice is paid, its line items, tax rate, discount and totals can't be changed, and neither can its paid status. In the editor they're dimmed with "Locked — this invoice is paid", and the lock also applies to changes made any other way. You can still correct the payment date and method, and edit the client, PO number and notes.
• Refunded and cancelled invoices are not locked. Admins can still change line items from the WordPress admin invoice screen.

Tabs that fit the space

• My Tasks and client pages now fit their tabs to the space, like projects. When a tab row gets tight, the tabs you're not on shrink to their icons (the name shows on hover) and the tab you're on keeps its name. If there still isn't room, the last tabs move into a More menu. It follows the width of the tab row itself, so opening a side panel counts too.
• My Tasks filter tabs now all have icons, and their counts show as small badges when the tabs shrink. Trash and the client Settings tab now show their names.
• The active tab is readable in dark mode on all three pages.
• Nothing to configure.

v4.130.0 — September 25, 2026

v4.130.0

Scope tab

• Opens on the client view for everyone. Your team sees exactly what the client sees, plus a line such as "Last updated by Eric Larson · Sep 24, 2026, 11:18 PM".
• Manage scope opens the editor on purpose. People who can edit scope click Manage scope to open the editor beside a live preview of the client view, which updates as they type. Close manager puts it away and asks first if there are unsaved changes. On narrow screens, an Edit / Preview switch shows one side at a time.
• Change history. Every save that changes the scope is recorded with who made it, when, and whether they added, updated or cleared it. The latest 20 changes appear under History in the manager. Saving without changes records nothing. Only people who can edit scope see the history.
• Clients see a clean, read-only view: the objective, what's in and out of scope, deliverables and constraints. Empty sections are hidden.
• Fixed: scope list items with accents or curly quotes are no longer garbled when saved, and an item containing a straight quote no longer empties the whole list. Items damaged before this release have to be retyped.
• Security: editing a project's scope now also requires access to that project, both in the Scope tab and through the AI assistant.

Project users

• Client users show "(Client)" next to their name when you hover their avatar in the project header, and in the Project users drop-down.

Projects list

• Last Modified shows the real date. Some projects showed Jan 1, 1970. The column now shows the latest activity or edit, whichever is newer.
• Project lead under the project name. Each project shows "Project Lead: Name" under its name, when a lead is set.
• Fixed: project activity entries lost their time and author. On some projects, activity entries were being saved without a time or who made them. New entries are saved correctly from now on. Times and authors missing from earlier entries were never stored and can't be recovered.
• Fixed: status changes in the project activity log. They now appear in order, with their time and who made them. On projects with more than 100 entries, the newest entries are no longer dropped.

Invoices

• Edit paid invoices. Paid invoices now have an Edit button. It opens the editor, where you can correct the payment date and method, and revenue reports follow the corrected date. Stripe payments show the card and can't be changed. Line items stay editable: changing them changes the invoice total, but revenue keeps the amount actually collected.

Upgrade notes

• Nothing to configure. The Scope tab opens on the client view; click Manage scope to edit.

v4.129.0 — September 25, 2026

v4.129.0

Process tab, redesigned

• Stages run down the page. Each stage is its own card with its status and a count of what's done, for example 3/4. The count includes your checklist and the client's to-dos. A stage with nothing to count shows no number.
• Open a stage to see its details. Previous and current stages expand to the same details as Status: progress, the client's to-dos with Upload and Mark done, the checklist, sign-off with Approve and Request changes, and the latest update. Upcoming stages show their description but don't expand. The current stage opens automatically, and when you advance a stage the new current stage opens.
• A sidebar beside the stages. On wider screens, stages take the left side and the right side shows the project lead's contact card and a short note from your team. On narrower screens the sidebar moves below the stages. If there's no lead card and no note, the stages use the full width.
• Set it up in Manage stages. A new "Process page" section has Show project lead card (on by default), Note beside the stages (empty by default, and nothing shows until you write one), and Show stage photos on Process (off by default). When photos are on, they appear as a small row of thumbnails under each stage and never change the layout. The Status tab's photo view is unchanged.

Project lead card

• The lead's card shows their name, title, email and phone, with a Message button that opens a message to them. You won't see the Message button when you are the lead.
• On Process and Overview, clients see the lead's email and phone once the card is turned on, even if the Team tab isn't shared with them. Clients who can't see Process or Overview don't get the card.
• Overview can show the card too. A staff-only Show project lead button puts it above the files. It's off by default.

Overview

• Clients can view the Overview but not change it. They can read the description and preview or download files. Only your team can edit the text or upload and remove files.
• Saving a first description works. Before, text typed into an empty description could disappear when you clicked Save. A description can now also be cleared, and a description that's only an image or table is kept when saved.

Tasks

• One Assign control in the task window, right after the dates. Pick one or more people from the drop-down; each click saves. The separate Assign button on the right is gone. Assignment is the task's members, which is what My Tasks, the Calendar and task sync already used. The old single "assignee", which new tasks set to their creator automatically, is no longer shown or editable.
• List view: one Assignee(s) column replaces the separate Assignee and Members columns. The export does the same. Due date, Created and Last updated show the time on a second line; due dates without a time show just the date.
• Calendar: clicking a task on a project's Calendar tab opens the task window in place, like Board, List and Timeline, instead of reloading the project. Cmd or Ctrl-click opens it in a new tab.
• Team tab: your own card no longer shows a message envelope, since you can't message yourself.

Invoices and estimates

• Correct a paid invoice's payment date and method. A paid invoice's editor shows the payment date and method. Revenue reports follow the corrected date, and the amount collected doesn't change. Stripe payments show the card and can't be changed. Paid invoices still don't show an Edit button on the invoice page, so open the editor with a link ending in ?cove=<invoice id>.
• Editor links. The invoice and estimate editors keep ?cove=<id> in the address, so refreshing or sharing the link reopens the editor.

Upgrade notes

• Nothing to configure. Existing Process pages show the lead card (if the project has a lead) and no note or photos until you change them in Manage stages.
• Tasks that only had the old single assignee now show as unassigned. Pick people with the new Assign control if needed.

v4.128.0 — September 25, 2026

v4.128.0

A refreshed project page

• One look across every tab. Reference, Files, Team, Calendar, List and Scope now share the card style of Process and Status: the same headers, counts and compact buttons.
• Tabs fit the space they get. Layouts respond to the width of the tab itself, not the whole screen, so a tab narrowed by an open side panel reflows the way it would on a smaller screen. Team cards drop from four columns to one as space shrinks, and the Files tables hide Preview, Uploaded by, date and type (in that order) before stacking each file on narrow widths. Preview stays available from each file's actions.
• Board. Lists have a soft shaded background and a light shadow, and task cards have a light border, so cards stand out from their list. Add task and Add list are now small buttons. The new-task editor looks like a card, with Add task and cancel underneath. When one list's title wraps onto two lines, every list's header matches its height so the first cards line up. Hovering a card no longer makes its title jump to a new line. On screens wider than 1920px, the lists sit centred as a group.
• List view. Each list is a card with its task count in the header and a small Add task button.
• Scope. The fields sit in a card. In Scope and Out of Scope appear side by side when there's room.
• Calendar. The project Calendar sits in a card within the page width, with compact Month, Week and Agenda buttons. The main Calendar page is unchanged.

Dark mode on the project page

• The whole project page now follows dark mode: the tab bar and its menus, the date and people drop-downs, form fields, Board, List, Scope, Timeline, Decisions, the project Calendar and pasted overview text.
• Coloured status badges and panels keep their light fill with dark text so they stay readable.
• Not yet covered: the task detail and archive windows opened from the Board, the assignee picker, and the loading screen.

Stages

• Know when your client can't see stages. If a project's Process and Status tabs aren't shared with the client, the Advance stage drop-down (with Notify client checked) and the Client sign-off block now say the client won't be notified or won't see the request. Administrators get a Share tabs button there. Nothing is blocked; it's a warning only, and success messages no longer say the client was notified when they weren't.

Security

• Per-project permissions on project data. Board and card changes, file moves, overview uploads, the activity log, project users, project dates and Reference previews and searches now check that the person can see (and, for changes, edit) that specific project, and respect which tabs are shared with clients. Before, some client roles could read or change other projects' data by id.
• Download as ZIP and file downloads only include files that belong to the project being viewed. The server finds each file itself instead of fetching whatever address the browser sent.
• Changing a project's status needs edit rights on that project.
• View-only users no longer see editing controls they can't use (completing or dragging cards, timeline drag and resize, Files drag, project dates). If a change is refused, it's undone on screen with a message.

Upgrade notes

• Nothing to configure. Tab sharing, users and project data are unchanged.
• If you added custom CSS to board lists, note that the list background now comes from the theme's own colours instead of your theme's "secondary subtle" colour.

v4.127.0 — September 24, 2026

v4.127.0

New: choose which project tabs your client can see

• The client access line. Manage Project Tabs (the gear at the end of a project's tabs) now has a line through the list. Tabs above the line are shared with the client; tabs below it are internal and only your team sees them. Drag the line up or down, drag a tab across it, or hover a tab and click Make internal or Share with client. Arrow keys move a focused tab or the line one row at a time.
• See it before you save. "Client portal will show" lists exactly the tabs your client will see. Save stays disabled until you change something, and Cancel puts everything back.
• Internal really means internal. A client can't open an internal tab through a link, a pin or a bookmark — they land on the first tab they can see — and the data behind an internal tab (files, stages, scope, calendar, reference items, card data) is refused to them.
• Your team sees what's shared. In the tab bar, shared tabs show a small eye, for your team only.
• Decisions is always internal. It can't be shared with clients.
• Stage emails follow the line. Clients only get stage emails and notifications when Process or Status is shared with them, and the link takes them to a tab they can open. Stage photos are only shown to clients when Status is shared.
• When nothing is shared, the client sees the project header and "Sit tight while we put your project together." Administrators see "Clients can't see any tabs on this project yet." with a Share tabs button.

Project header

• Project dates open in a small drop-down under the date button instead of a window: start and due dates, Clear links, Cancel and Save. Enter saves; Esc or clicking away closes without saving. The Timeline and project Calendar update as soon as you save.
• Project users open in a drop-down too: the people on the project (with the lead badge, Make lead and remove) and an Add people search that filters client and internal users as you type. Changes save as you click.
• On phones, both appear as a sheet at the bottom of the screen.

Security

• Only administrators, editors, system admins and tech admins who can edit a project can change its tabs. Before, some client roles could change a project's tab settings.
• A project's overview text and overview file list are no longer available to users who can't see that project.

Upgrade notes

• Existing projects don't change: every tab your clients see today stays shared. The one visible change: if Decisions is switched on and sits among other tabs, it moves to the end of your team's tab bar.
• New projects share nothing with clients until someone on your team moves tabs above the line — including Board and List, which are usually internal. This applies to projects created from a template and to imported projects too.
• The project template page's "Manage Default Users" window is unchanged.

v4.126.0 — September 24, 2026

v4.126.0

New: project stages, lead and calendar

• Process and Status tabs. Give a project a list of stages and show clients where their project stands. Process shows each stage as a block; Status shows a progress stepper with photos (with captions and a full-screen viewer), the latest update, and what the team is working on. Start from a stage template (two starters are included; manage your own in Settings → Project Stages) or build the list by hand.
• Checklists, client to-dos and sign-off per stage. Each stage can carry a team checklist (To do → In progress → Done), to-dos for the client (mark done, or upload a file — uploads land in the project's Files tab), and an optional client sign-off (request, resend or cancel; the client approves or asks for changes).
• Advance a stage from one button. Advancing asks "Move to …?" and warns about open checklist items, open client to-dos and sign-off that is still pending. "Notify client" is on by default and sends an email plus a portal notification, with an optional note that replaces the stage update in the message.
• Clients get a read-only Status view with a progress bar, their to-dos, the sign-off card and the latest update. Only your team can change stages. Clients do not see the Process or Status tab until the project has stages.
• Project Calendar tab. A calendar locked to one project, showing its cards and the project's date span. Staff can drag the project bar to change its dates; clients see it read-only and only for projects they can already view.
• Project lead. Mark one Assigned User as the project lead with "Make lead" in Manage Users. The lead gets a star on the header avatar and a badge on the Team tab, and cannot be removed from the project while they are lead. The lead is always kept in Assigned Users, including when a project is created from a template.
• Clients can turn off stage emails in their notification preferences ("Email me when a project moves to a new stage or gets new stage photos"). It is on by default.

Project page

• The tab row fits any width without wrapping. When space is tight (a narrow window, a side panel, split view), inactive tabs shrink to icons with their name on hover, while the tab you are on keeps its label. If that still does not fit, the last tabs move into a "More" menu. The tab you are on never moves into "More".
• Search and the tag filter are icons. Search opens into a box when you click it, stays open and highlighted while a search is applied, and Escape clears it. The chosen tag shows in the tag button's tooltip.
• Export moved into the ⋯ menu as "Export Tasks to Excel". That menu is only shown to administrators, editors, system admins and tech admins, so other staff and client users can no longer export tasks from the project page.
• "Edit Project" was removed from the ⋯ menu, along with the form it opened, which did not work. "Unassigned" next to Company is now plain text instead of opening that form. Editing a project from the Projects list is unchanged.

Bug Fixes

• Creating a project from a template now uses the template. Before, the Scratch/Template choice was never sent, so every project started empty.
• Client users no longer get "page not found" on their own projects.
• A new project's board now lets you add the first list.
• The tab settings window no longer closes on every click.
• Cards created by the AI board import now appear on calendars.
• Emoji, quotes and backslashes in board list names, activity logs, ticket replies and ticket history are now kept intact. Before, each later save stripped part of them, so a list named "✏️ Draft" could turn into "u270fufe0f Draft". List names already damaged this way are repaired automatically; older activity-log and ticket entries that already lost characters are not.
• Ticket reply emails no longer show a backslash before apostrophes.
• On phones, the project tab dropdown now shows the tab you are actually on after the page reopens your last tab.

Upgrade notes

• Process, Status and Calendar are off on every project until you switch them on with the tab settings gear. Nothing is shown to clients because you upgraded.
• No project gets a lead on upgrade. Projects that already had a lead set have that person added to Assigned Users if they were missing.
• No emails are sent on upgrade. Stage emails go out only when someone advances a stage or requests sign-off with "Notify client" on.

v4.125.0 — September 23, 2026

v4.125.0

Bug Fixes

• Settings → AI → My own AI provider: "Use WordPress Connectors" now appears only when a WordPress AI provider plugin (Anthropic, OpenAI or Google) is active, since Connectors cannot work without one. Sites without a provider plugin see only "Store keys in ClientCove".
• If your site already uses WordPress Connectors and its provider plugin has been removed, the option stays visible with a warning that AI is off, so you can see what is selected and switch to storing your key in ClientCove. Your saved choice is not changed on upgrade.

v4.124.0 — September 23, 2026

v4.124.0

Bug Fixes

• Revenue: hovering a slice of the Receivables aging chart now shows its amount in a readable bubble. Before, the bubble took the slice's color while its text stayed dark, so the 61–90 days and 90+ days amounts were black on dark red. The bubble now matches the other Revenue charts, with a colored dot for the slice, in both light and dark mode.

v4.123.0 — September 23, 2026

v4.123.0

New Features

• The setup wizard now creates the Calendar page when Tasks, Tickets or Projects is on, and includes Calendar in the admin menu it builds for new sites. This update does not create the page by itself: to add it to an existing site, run the setup wizard again (Settings → Setup). The wizard never changes a menu you have already set up, so add Calendar to your admin menu yourself.
• If your site already has its own page at /calendar/, the wizard leaves it alone and creates the new Calendar page at /calendar-2/. An existing page is only reused when it already uses the Calendar template.
• The Calendar card in Admin Utilities opens your Calendar page wherever it lives, and is grayed out until the page exists. Before, it opened /calendar/, which showed "page not found" on sites without that page.

Bug Fixes

• Client pages now fit the space they have. With an item pinned in the side panel, or on a smaller screen, the tabs take the full width and the client's logo, name and addresses move below them. The tab bar scrolls sideways instead of wrapping onto several rows. Before, the tabs were squeezed into a narrow strip beside the client card. On a wide screen with no panel open, the page looks the same as before.

v4.122.0 — September 23, 2026

v4.122.0

Security

• Several portal data routes now check who is asking. Before, they returned the client list, a client's users, the staff list and project boards without checking permissions. Clients still see their own projects and boards. The client list at /wp-json/wp/v2/client is now for admins and editors only, so an outside integration that reads it with any other account will now be refused.

New Features

• New Calendar page: your tasks, tickets and project start and due dates in one month, week or agenda view. It is not created automatically. To add it, create a page and choose the "Calendar" template. It is for staff only; clients never see it.
• On the Calendar, staff see their own work and work for the clients they are assigned to. Crew Dashboard managers can switch to Team to see everyone's. Filter by type, assignee, and open or completed.
• Drag an item to another day to reschedule it. The new date is saved to the task, ticket or project, and the move is undone if the save fails.
• Click an empty day to create a task or ticket on that date. Projects are still created from the Projects page.
• Repeating tasks show their upcoming occurrences on the Calendar as faded placeholders.
• Project board cards with dates can be shown with the Cards filter. They are off by default, so the Calendar is not crowded after the update.
• Clicking a task on the Calendar opens it in the side panel. There you can change its due date, priority, assignee and notes, and mark it complete. The panel also lists everything the task is related to: its asset, the asset's location, a ticket, a project. Reassigning a task emails the new person, the same as assigning one when it is created.
• Each client page has a Calendar tab showing only that client's work.
• New "Next 7 Days" widget for your dashboard.
• The Calendar and Crew Dashboard link to each other: from a person on the Crew Dashboard to their calendar, and from a calendar filtered to one person back to the Crew Dashboard. The links only appear once both pages exist. A Crew Dashboard person view can be bookmarked or shared.
• The Calendar and Crew Dashboard adapt to the space they have, including when an item is pinned in the side panel. When the Calendar is too narrow for a grid it shows the agenda, then returns to your chosen view when there is room again.

Bug Fixes

• Pinning an item in the side panel no longer squeezes the Crew Dashboard, Email Designer, project pages and a few other pages down to nothing.
• On phones and tablets, switching from a pinned item back to the page shows the page at full width again, instead of a narrow strip.
• Small dropdowns no longer draw their arrow over the selected text.

v4.121.0 — September 23, 2026

v4.121.0

New Features

• Assets now have a Service Schedules panel on the Management tab. Add one or more routines per asset (daily, weekly, every 2 weeks, monthly, quarterly, every 6 months, or annually), anchored to a fixed date or to the last service, with a start date and an assigned tech. Each schedule is an ordinary recurring task linked to the asset, so it shows up in task lists and is edited there. The panel adds schedules only; to change or remove one, edit its task. Locations are not covered yet.
• An asset's Next Service Date now comes from its soonest open service schedule. Assets with no schedule keep the date they already had.

Bug Fixes

• Google Workspace / Gmail stays selected in Settings → Transactional Email after you save. Before, the page reloaded showing SendGrid, and saving it again switched your mailer back to SendGrid. The delivery banner and email log now report Gmail too, instead of "PHP mail() fallback".
• Daily asset service reminders now reach the assigned tech. They had been matching no assets, so no reminder email, bell notification or inbox message was sent. After this update, techs start receiving reminders for assets that are due.
• Recurring tasks set to quarterly, every 6 months or annually now repeat on that cadence. Before, completing one created the next occurrence the following day. A cadence the portal does not recognise is now refused instead of silently becoming daily.
• Ticket rows on the crew dashboard show each ticket's real priority, with matching badge colours, instead of "normal" for every ticket.
• Project start and due dates are stored in one consistent format, so project timelines and overdue/upcoming counts use the real dates instead of a default window. Existing dates are not rewritten on upgrade; the wp cove-project-dates normalize command reports what it would change, and --apply makes the changes.
• The setup wizard's sample ticket now opens with its status, priority and client set. Sample tickets created before this update are not changed automatically; the wp cove-seed-ticket backfill command reports them, and --apply repairs them without touching anything a person has edited since.

v4.120.0 — September 22, 2026

Automations that draft instead of send

Four new ready-made automations write a draft and stop: a ticket with no update for a day drafts a reply, an invoice past due drafts a reminder, an estimate about to expire drafts a follow-up, and Monday morning drafts a status message for each client. Every one of them fills your Inbox — nothing reaches a client until a person opens the draft and publishes it. They are options in the recipe library, not new behaviour: no automation starts running because you upgraded, and the send-now versions of the same four are still there for anyone who wants them.

When the assistant offers Automate: … after you have done the same thing three times for a client, taking it now drafts that exact recipe in one step. It still only drafts: an automation created this way arrives switched off, and switching it on stays a separate thing you do yourself.

Agents start with their instructions written down

Picking Brief, Studio or Books when you create an agent now fills in its standing instructions — the job it is for, followed by the house rules the agent already lives by: you draft, you do not send; after a draft, stop, a person publishes; if a tool is denied, stop. The text appears in the form before you save, so you can edit or clear it, and applying a preset to an existing agent adds instructions only when it has none. Instructions you wrote yourself are never overwritten.

These are words for the agent, not the fence. What an agent may actually do is still its keyring and its tier, exactly as before.

Suggestions that can be taken

The chips the assistant offers after a save or send now always reach the tool they name. Two suggestions that could not be delivered have been removed: automating a file upload or move, and automating a campaign send. Both needed parts of the portal that do not exist yet, and pressing them ended in a refusal — they will come back when they work.

Upgrade notes

• Nothing sends, publishes or enables on upgrade. No setting changes. Automations you already have are untouched.
• The AI tool router stays off, as it has been. If you ever switch it on, chips are now exempt from it: the portal wrote the sentence and knows the tool, so a chip never loses the tool it needs.
• One database change: the router's diagnostic table gains two columns on first load. It stays empty unless the router is set to Shadow.
• Developers: draft_automation takes recipe_id plus needs and the server expands the recipe before the tier gate sees it; an automation may now run a record-only draft step unattended, while steps that change a real record stay behind allow_destructive; next-move chips publish the tool they need and the chat endpoint accepts it as chip_tool; preset text comes from cove_agent_preset_instructions().

v4.119.0 — September 22, 2026

The assistant drafts first

On a ticket, "tell them we're on it, Friday" now writes a draft reply for you to publish instead of posting live. The live reply only happens when you say to post or send it. "Make this automatic if it happens again" drafts the automation straight away, shaped from the closest ready-made recipe, rather than stopping at a list of recipes; it is never created or switched on from chat. Drafting a message no longer asks whether it is a portal message or an email: it is a portal message unless you ask for an email. Recording a payment no longer asks for the date: it is today unless you give one.

Agents can draft on their own again

An autonomous agent's draft (a reply, task, message, estimate, intake or automation) now lands in the Inbox directly. Before this release, every draft first opened an approval request for permission to write the draft, which the owner then had to publish anyway. The Inbox draft is the control point. Edits to real records, such as changing a task, still need the owner's approval, and an agent with a send or reply tool on its keyring is still stopped before anything goes live.

Next moves

Chips after you save or send something for a client find that client again, so "Mention in ticket #4412" and "Tell Acme it is there" appear when they should. A client user who saves or moves a file is offered Ask staff; Create a folder is offered to staff only.

Collapsed sidebar with a background gradient

The sidebar that opens on hover now paints in the gradient's top colour, the lightest stop in every light preset, so it reads as part of the same sweep instead of a separate panel. It takes effect the next time the design is saved.

Upgrade notes

• No database changes. No setting changes. Nothing sends, publishes or enables on its own.
• Developers: tools that write only an Inbox draft declare writes_only_a_draft(); the policy decision point skips the destructive confirmation for an agent's call to those. The generated stylesheet emits --cove-bg-gradient-{light|dark}-top. The gold-trace conversations from the brief's §11 live in tests/fixtures/golden/gold-*.json and GoldTracesAgentTest; tests/eval/run-live.php scores them against the real model.

v4.118.0 — September 22, 2026

The assistant knows what is on your screen

Every message you send the assistant now carries a small, server-built picture of where you are: the item on the page you are viewing, the files you have ticked in the Resources library, the last thing you saved, sent or moved in the past fifteen minutes, your Inbox counts, what you have been doing this week, and your next deadlines. So "what are these two files?", "now share it with Acme" and "what did I just do?" get an answer instead of a question back. Everything in that picture is checked against your permissions before it is used; the assistant never sees an item you could not open yourself.

• Staff also get the list of automation recipes and a note when the same save, send or move has happened three times this week for one client, so the Automate suggestion names the right recipe.
• Client users get their own page, selection and activity, nothing about other clients.

Collapsed sidebar with a background gradient

When the sidebar is collapsed to the icon rail and a background gradient is on, the full sidebar that opens on hover was see-through and showed the page underneath. It now opens solid, in the sidebar color, with a soft shadow, and the rail itself is unchanged.

Upgrade notes

• No database changes. No setting changes. Nothing sends, publishes or enables on its own.
• Developers: the block is built by ClientCove_Chat_State; the cove_ai_chat_state_enabled filter removes it, cove_ai_chat_state reshapes it. List views publish a selection by setting window.coveAiSelection to an object with type and ids. A portal save or move that asks for next moves also becomes the assistant's "just did".

v4.117.0 — September 22, 2026

The clients directory fits the space it is given

Pin an item to the side panel and the clients page now lays itself out for the room that is left, rather than for the width of your window. Before, a wide screen with a panel open still asked for three columns of client cards and squeezed them into half the page, so titles wrapped and the counts ran together. The page now fits as many cards across as will actually read well, down to one, and it re-flows live as you drag the panel's edge. With no panel open nothing changes: the same three columns as before.

The list view fits too, without hiding anything from you

The list used to be a wide table you could only reach by scrolling sideways, which pushed the Status column out of sight. It now shows the columns that fit and folds the rest into a summary line under each client's name, so every number is still on screen — it moves, it does not disappear. Widen the page, or close the panel, and the columns come back.

• The client's name and status never go. Tickets and Open Invoices are the last counts to fold in, because they are the ones that mean there is work to do. Locations, Assets and Resources fold in first, then Users, Projects, Created and Last login.
• The page works out how much room your table needs from the features you actually have switched on, so a site with Locations and Assets off keeps its remaining columns down to a much narrower page.
• Sorting is unaffected. Sort by a column that is currently folded in and the list still sorts by it.

Upgrade notes

• Nothing to turn on and no settings to change. The clients page picks this up on its own.
• The same layout applies on a narrow window or a phone, where it replaces the old fixed breakpoints.

v4.116.0 — September 22, 2026

The assistant answers like an action bar, not a help desk

The assistant now follows one of four modes on every turn: act on what you asked, offer up to three choices when several items fit, ask one question when a fact is missing, or recommend two or three concrete next actions when you ask what to do. After it saves, sends, moves or drafts something it replies in a fixed shape: one status word (Saved, Sent, Moved, Draft saved, Published, Needs your YES, Nothing to do, or Can't with the reason), one sentence about what happened, and a link to the item. Then it stops. Next steps come as the chips under the reply, not as prose, and the old "What else can I help you with?" closer is gone.

• The page you are on is the default object. "What's the status of this?" or "draft a reply on this" works on a ticket, invoice or file page without the assistant asking which one.
• One intent per turn: if you ask for two things, the assistant does the first and offers the second, never a second surprise change.
• Nothing is sent, published or enabled unless you asked for it in that turn. Client-facing text you did not tell it to send is saved as a draft.
• Unprompted tutorials and feature tours are gone. Asking how something works still gets an answer, sourced from the documentation first.

Tone presets

The Friendly preset no longer suggests a "Great question" opener, and the Professional preset ends after the answer instead of offering next steps. Custom personality text you wrote yourself is untouched.

Upgrade notes

• No database changes. No setting changes. Nothing sends, publishes or enables on its own.
• Developers: the block is cove_ai_action_bar_guidance() in includes/functions/ai/ai-action-bar-prompt.php, sent in the cached stable part of the system prompt. The golden chat harness accepts a page per turn.

v4.115.0 — September 22, 2026

The assistant understands requests the way you say them

Every tool the assistant can use now introduces itself to the model in your words first: "Use when the user wants to file or move a file into a folder", with two example phrasings such as "put this in the Brand kit", before the technical detail. Each one also states plainly whether it only reads, only drafts, goes live after you confirm, or is privileged. The result is fewer clarifying questions and more first-try routing for everyday phrasing like "pause Brief", "list unpaid invoices" or "reply to #4412: fixed". The same descriptions reach Claude Desktop and Claude Code through the ClientCove connector.

• Nothing about what a tool does, asks for, or is allowed to do has changed. Only how it is described to the model.
• The agent keyring picker and the automation catalog keep their original short descriptions.

Faster, cheaper turns on your own API keys

For portals that store their own Anthropic key in ClientCove, the assistant's system prompt is now cached alongside its tool list. Only the part that changes per page is re-read each turn. Managed portals and WordPress Connectors portals are unchanged.

Client users see a smaller, correct tool list

Client-role users no longer see delete resource, draft estimate, draft automation or list users in the assistant's catalog. Each of these already refused to run for a client; the catalog now agrees. Staff and agents are unchanged.

Upgrade notes

• No database changes. No setting changes. Nothing sends, publishes or enables on its own.
• Developers: ClientCove_Tool::describe() composes the model-facing text; the verb map is includes/ai/tool-verbs.php and a registered tool without an entry fails the test suite. Filter cove_ai_cache_system_prefix disables the system-prompt breakpoint; cove_ai_cache_tools off disables both.

v4.114.0 — September 22, 2026

Drafts live in Messages now

Messages has a Drafts list and the composer has Save draft and Discard. A draft you save, and a message the assistant wrote for you but did not send, both sit there until you open them, edit them and press Send. Send from a draft sends exactly what is on screen, as you, through the same checks as a fresh message. Nothing in Drafts is ever sent on its own.

• The Agents Inbox and Messages → Drafts show the same drafts; publishing from either place is the same act.
• Client users can save and send their own drafts; nobody can open, send or discard someone else's.

The assistant suggests what to do next

After the assistant saves, sends, drafts or moves something, its reply ends with two or three chips: Record payment · Create next invoice after an invoice goes out, Publish task · Open board after a task is drafted, File in Brand kit · Mention in ticket #12 after a file is saved. The portal builds these from what just happened; the assistant does not make them up. Clicking a chip either opens a page or hands the assistant a sentence, which then goes through the usual confirmation, so a chip can never do something on its own. Chips are only ever things your account can do — a client user never sees a staff action. On a quiet page the assistant's opening suggestions now reflect the page: an open ticket offers Draft a reply, an overdue invoice offers Send reminder, pending drafts offer Review drafts.

• Moving files in the Resources library shows the same chips on its confirmation toast.
• A move, save or send you have done three times in a week for the same client offers Automate, which only drafts the automation — enabling it stays a separate, confirmed step.

Settings → AI → Draft auto-publish

Off by default, and nothing changes on upgrade. The one setting lets staff-to-staff notes that the draft scan found nothing in skip the Inbox. It can never apply to a message written by an agent, addressed to a client, or not cleanly scanned, and it does nothing at all without a TypeSafe key.

Upgrade notes

• No database changes. No setting changes. Nothing sends, publishes or enables on its own.
• Developers: the tool registry now fires clientcove_tool_executed after every executed call; clientcove/v1/ai/next-moves returns the chips for a portal event; coveToast.nextMoves() puts them on a toast.

v4.113.1 — September 21, 2026

Correction to the 4.113.0 note: the chat savings apply only to portals using their own provider keys

The 4.113.0 note said the assistant's action list "is now cached with the provider" and that chat "now appears in AI usage reports". Both are true only when Settings → AI is set to bring your own keys with "Store keys in ClientCove". Portals on the default ClientCove-managed AI, and portals using WordPress Connectors, saw no change from 4.113.0 — no caching, no chat rows in the usage report, and nothing to switch off. Nothing was broken by that release; the note claimed more than it delivered, and this one sets it straight. Bringing the same savings to the managed service is on the list and will be announced when it ships, not before.

The assistant and agents can now draft a message without sending it

Ask the assistant to "write Acme the Monday update but don't send it" and it saves a portal message or email as a draft in the Inbox (User Management → Agents) instead of sending it. Publish sends it as you, through the same checks as sending by hand; Discard throws it away. Agents on the Brief and Studio presets can draft messages the same way, and an autonomous agent still cannot send anything — the draft is the most it can do. An existing email campaign can be queued the same way, so "get the newsletter ready" puts it in the Inbox with Publish to send or schedule it.

• Drafts are listed by author: your own assistant drafts show as "You · assistant" and only you or a user manager can publish or discard them.
• If a TypeSafe key is set under Settings → AI, each draft is scanned and flagged when it mentions money, makes a promise, has a tone problem or touches sensitive content. The flags are shown for review and never block or send anything. Without a key there is simply no flag.
• Nothing auto-publishes. Site owners who want staff-to-staff notes with a clean scan to skip the Inbox can opt in with the cove_draft_auto_publish filter; it can never apply to a client-facing message or to an agent's draft.

Bug fixes

• Automations: editing or dry-running an automation no longer fails with "field_mappings is not iterable" when a step was saved without any field mappings.

Upgrade notes

• No database changes and no setting changes. Nothing sends or publishes on its own.

v4.113.0 — September 21, 2026

Faster, cheaper AI chat

The portal assistant sends its full list of available actions to the AI provider with every single message — roughly 30,000 tokens each time. That list is now cached with the provider, so from the second message of a conversation onward it is billed at about a tenth of the price and the assistant begins replying sooner. Nothing about what the assistant can do changes, and there is nothing to switch on.

Chat now appears in AI usage reports, so your totals will look higher

Chat was the only AI feature that never reported to Settings → AI usage. Every usage figure you have seen until now excluded the portal's busiest AI feature. It is counted from this release onward, so expect your monthly token count and estimated cost to rise noticeably — this is not new spending, it is spending that was always happening and was simply never recorded. Reports also now separate cached tokens from uncached ones, so you can see how much of the saving above you are actually getting.

A new "Chat tool router" panel appears under Settings → AI

It is switched off and does nothing at all until someone adds a TypeSafe API key and picks a mode. Leaving it alone keeps the assistant behaving exactly as it does today. It is groundwork for narrowing the assistant's action list to match each question; it is not ready to be switched on, and there is no reason to touch it yet.

Upgrade notes

• A small database update runs automatically on the first page load after upgrading. No action is needed.
• No setting changes, and no change to what the assistant can do or to who can use it.
• Site owners who want the caching turned off can define COVE_AI_DISABLE_TOOL_CACHE as true in wp-config.php, though there is no expected reason to.

v4.112.1 — September 21, 2026

Fixes an empty gap above the Folders bar in Resources

When a pinned item is open beside Resources — or the window is narrow — the folder tree collapses behind a "Folders" bar above your files. That bar could stretch to several times its height, leaving a tall blank band between it and the search box.

• It showed up when the folder you were in held only a few files and your screen was wide, so there was leftover space on the page for the bar to absorb.
• Nothing was lost while it happened; the bar and the folder structure behind it still worked. Only the spacing was wrong.

v4.112.0 — September 21, 2026

Background gradients for your portal

App Design has a new Background Gradient section with seven presets — Aurora, Mist, Dawn, Tide, Meadow, Ember and Halo. Each one ships a light and a dark version, and you pick them separately, so a gradient never washes out a dark portal.

• A gradient paints the background behind your content only: the page in Standard layout, or the surrounding dock surface in Cove Dock. Cards and the content area stay solid, so nothing changes about how readable your text is.
• Nothing changes until you choose one. "None" is the default and every existing portal stays exactly as it is on upgrade.

Palettes now set light and dark together

Choosing a palette sets its counterpart in the other mode too — pick Ocean Blue and dark mode becomes Midnight Blue — so one click leaves the portal coherent in both. Uncheck "Pair light & dark" above the palette grid to set the two modes independently; your choice is remembered in your browser. The palette you have applied also stays highlighted now when you switch between the Light and Dark tabs.

Three new palettes

Warm Clay (terracotta on warm cream), Spectrum (bright primaries on clean white) and Paper White (shades of white), each with a matching dark counterpart: Warm Clay Night, Spectrum Night and Graphite.

Color picker fixes

Two long-standing problems in App Design are fixed. The color swatch next to each field stopped updating once you applied a palette, so later changes you made in the picker never showed on the swatch. And a picker left open while you applied a palette kept showing the old color, which could push that old color back over the palette on your next adjustment.

Editors and system admins can save designs again

Anyone with the "Manage appearance designers" permission could open App Design and Login Design and change every control, then be told "Insufficient permissions" when they saved. Saving now uses the same permission as opening the page. If you had granted that permission to an editor or a tech role, it works as intended now — no change for administrators, who could always save.

Category sidebars on the list pages

The category sidebar on Projects, Clients, Assets and Locations adapts to the space it has.

• It no longer shrinks below a readable width on smaller screens.
• Pin an item and the sidebar folds into a narrow vertical strip instead of disappearing, the same way the message list does. Click the strip to bring it back.
• When the list gets genuinely narrow, the categories roll up into a dropdown next to the search box, and the View Archived button moves alongside it so it is never lost.

Projects also shows its Company and Category columns in a smaller type size, and the Projects, Assets and Locations cards now have the same border and shadow as the Clients card.

v4.111.1 — September 21, 2026

Fixes

• Pinned Team view fits the panel. The Team header wrapped awkwardly in the pinned panel and its search box ran off the edge. In the panel the search is gone (the team is a short list), the title, count and Message Team button sit in one compact block, and each person's card takes the full width. On the project page the header now wraps cleanly in a narrow window.

Nothing changes on upgrade.

v4.111.0 — September 20, 2026

New

• Pin a project view — or a single card — to your sidebar. The pin button on a project is now a Pin to sidebar menu listing that project's views: Team, Files, Timeline, Reference, Overview, Decisions and Scope (whichever are turned on; Board and List stay on the page). Open a card and there's a pin button beside Close to pin just that card. A pinned view opens beside whatever page you're on with everything working — the Team list, the files, the full card with its description, checklist, images, files, Google links, comments and activity. If you're already on that project, clicking the pin switches to that tab or opens the card. Pinning a whole project is gone; any old whole-project pins are removed.
• Link Google Drive and Docs files to a card. Open a card and click Google Doc: paste a Drive, Docs, Sheets, Slides or folder link and it's attached — with Open in Google, an inline preview, and remove — the same way ticket replies and resources link Google files. The card shows a Google badge with the count.

Design

• Cards are tinted by their tag. On the board and in the list, a card with a tag takes a faint wash of the tag's colour, and the tag dots sit in the card's bottom-right corner; the list has a tags column.
• Tighter project header and board. The header takes less height (breadcrumb, project number, dates, status and company are more compact); card dates and titles are tighter, and list titles are lighter.
• Tickets and Resources adapt to a narrow column. When a pinned panel is open, or the window is narrow, the Tickets page swaps its status pills and Categories sidebar for Status and Category dropdowns above the list (Closed tickets is in Status), and the Resources page folds its folder tree behind a Folders button.

Fixes

• Cards tagged from the global tag library (Settings → Global Tags) now show their tag in the list view.

Documentation

• New help page: Pinning Project Views & Cards.

Nothing changes on upgrade. No settings, permissions, projects or cards are touched. If you had a whole project pinned, that pin disappears — open the project and pin the view you actually use.

v4.110.0 — September 20, 2026

New

• The Products hub, rebuilt as cards. The Product Manager page is now titled Products and shows everything you sell as cards instead of tables, in your portal's own colors. The Catalog tab has filter pills (All · Plans · Products · Public · Client-scoped · Inactive), a live search, a Cards / Rows switch that remembers your choice, and a Plan sets strip showing each set's tiers as a small price chart. Every plan and product card has Add to page: pick a page (or create a draft page on the spot), the block is added, and the page studio opens with it selected. The Groups tab shows each group's tiers with Edit and Add to page, plus a New plan set card that starts the guided Plan Set Builder on a page you choose. The Pages tab shows a thumbnail of each page's blocks, its Live / Draft / Scheduled status, views over the last 7 days, Edit, and Preview as — which opens the studio's preview as a public visitor or a logged-in client. One + New menu creates a Plan set, Plan, Product, Group or Page.
• Preview as and the hub's Add to page open the studio directly on the right block or preview; nothing else about the studio changes.

Design

• Dialogs no longer darken the page. Modals and confirmation dialogs open over the page without the grey overlay; the dialog's shadow sets it apart, and clicking outside still closes it. This applies across the portal, not just the Products area.

Nothing changes on upgrade. No settings, permissions, plans, groups or pages are touched; the hub reads the same records the tables did. If you had the Product Manager page bookmarked, the address is the same.

v4.109.0 — September 20, 2026

New

• Plan Set Builder. Building a pricing page no longer starts in the product records. In the page studio, add a Plans block and choose "Create a plan set": a short guided flow names the set, lets you define one to four subscription tiers by editing the real plan cards in place (start from a preset, from a blank set, or let AI draft the tiers from four quick questions), asks where the set should appear, and then creates everything in one step — the Plans in your Catalog, a reusable Group, and the filled block on the page. Destinations you can pick: this page, a standalone link at /p/your-set-name, a new pricing page seeded with a hero, and a widget on a client dashboard. "Embed on an external site" is shown as coming soon. Afterwards the block's settings show the set, each tier, an "Edit plan set" button that re-enters the flow, and an "Also available at" list with copy buttons for every placement. Billing needs no extra setup — checkout handles the new plans automatically. Requires staff who can edit product pages; the AI option appears only when an AI provider is connected.
• Reorder plans and tiers. Drag the cards under "Per-item display" in a Plans or Products block to set the order clients see (the arrows still work too), and use ‹ › on the tier cards inside the Plan Set Builder.

Studio

• Draft / Live now sits beside the Save button as a small status select, instead of in the Page settings panel. "Go live automatically" stays in Page settings.
• Preview matches the live page. Plan and product cards were rendering as plain text in the studio's Preview tab; the preview now uses the same stylesheets as the front end, including your brand colors.
• Block settings read as a deeper level. When you open a block's settings the left rail takes a faint grey with a soft inset shadow, and returns to white when you go back to the block list.

Nothing changes on upgrade. No settings, permissions or existing pages are touched; the builder only appears when you choose it on a Plans block.

v4.108.3 — September 20, 2026

Design

• The buttons at the top right of every page are now the same size. Import, Export CSV, Add User on User Management, and the equivalent buttons on every other list page, now match the Add Ticket button on Tickets: the same text size, weight, padding and corner radius. Pages that had smaller or larger buttons up there fall in line automatically. The light button is the outlined white style; the primary button is unchanged in color.
• User Management's tabs now look like the tabs on a client's page. Client Users, Contractors, Techs & Staff, Permissions and Agents use the same tab style as Contacts, Locations, Assets and the rest of the single-client card, with an icon and a count beside each user tab. The tabs work exactly as before, including deep links and the remembered tab.

Nothing changes on upgrade beyond how those controls look.

v4.108.2 — September 20, 2026

Bug fix

• Narrow-layout tables: the column labels were printed on top of the values. In 4.108.1, when a table stacked into cards because the content area was narrow — User Management with an item pinned beside it, for example — each label ("Role", "Client", "Last login") landed directly over its value on pages that give their tables page-specific styling. The stacked layout now holds on every page: labels in their own column on the left, values lined up to the right. Nothing else changes.

v4.108.1 — September 20, 2026

Tickets

• Turn any ticket response into a task. Every response in a ticket thread now has a "Create task from this response" button, whoever wrote it — a client, a tech, support. It opens the familiar Add Task window with the response's author, date and text shown, and the task's notes carry that response rather than the ticket's original description. The task still links back to the ticket. Available to staff who can edit the ticket.
• The task shows up in your pinned My Tasks panel right away. If you have My Tasks pinned beside a ticket (or a ticket pinned beside the My Tasks page) and create a task from it, the task appears in the list immediately. No reload.
• "Assign to Another User" when adding a task from a ticket is offered to technicians, tech leads, technical administrators, representatives, sales representatives, admins and system admins. Other staff simply get the task on their own list; the choice isn't shown to them. The assignee list is every staff account plus the ticket's client users. This option previously computed the assignee but never sent it, so every task quietly landed on your own list; that is fixed.
• The Details column on a ticket now collapses by the ticket area's own width, not the browser's. Under about 1100px of ticket width — a narrow window, or a ticket beside a pinned panel — the column folds into a Details button next to "Now Viewing", which opens the same panel as an overlay sized to the ticket area. Press Escape, the X, or click outside to close it. The pinned split panel's own details button opens that overlay too. Under about 870px the Unanswered / Unclosed / Unassigned / Assigned to you / All links step aside.
• The Details overlay no longer shows its title twice, and the stage badge beside the ticket number is back to normal size.

Everywhere

• Tables no longer run off the page when the content area is narrow. With an item pinned beside a page like User Management, Clients or Tickets, or on a tablet or phone, a table that used to push the page sideways now stacks each row into a small card with the column names as labels, so every value and every action stays reachable. It switches on when the content column is narrower than 900px and back off when there's room. Tables that already scroll sideways inside their own box (invoice line items, for example) keep doing that.

Nothing changes on upgrade unless you have a narrow layout: no settings, permissions or data are touched. If a particular table reads better as a table even when narrow, add the class cove-table-nostack to it.

v4.108.0 — September 19, 2026

New

• Revenue page. A staff-only page (Settings → Features → Revenue Page, then add it to your menu) that answers four questions from one screen: how much came in, what is still owed, what is recurring, and who pays you. It shows collected revenue by month split into invoices, one-time orders, subscription renewals and refunds, with a comparison against the previous period; outstanding and overdue balances with an aging breakdown and your largest open invoices; monthly and annual recurring revenue with the subscriptions renewing in the next 30 days and any that are cancelled or ending; revenue by client and by product; and the most recent payments. The period picker sits in the page toolbar. It only appears to staff who can manage invoices, and only while Invoices is enabled.
• Payment ledger. The portal now keeps its own record of every payment: invoices paid in the portal or marked paid by hand, one-time orders, subscription renewals from Stripe, and refunds. Renewals were never stored before, so any report built from invoices and orders alone under-counted subscriptions after their first payment. The ledger fills in going forward on its own. To include your history, click "Backfill from Stripe" on the Revenue page (or run wp cove-ledger backfill); it is safe to run again and never creates duplicates. Nothing is written to Stripe.
• Export revenue to CSV. Staff with the "Export billing data" permission can download the ledger for the selected period, one row per payment or refund, ready for an accountant.

Orders

• The Orders list has been rebuilt. Every order now shows its amount, status, type (one-time, subscription or manual), items, client and buyer, and payment method. A summary strip at the top reports what has been collected, what is pending, active subscriptions and manual orders in progress for whatever you have filtered. Tabs, a client filter, a period picker, search, sortable columns and pagination replace the single unfiltered table.
• One purchase, one row. Purchases made through the on-site checkout used to appear twice — once as the order and once as the access record behind it. The duplicates are hidden; nothing is deleted.
• Client users with billing access see only their own client's orders.
• The old "Add order" button is gone. It opened a form that no longer exists in the theme; manual orders are still created the way they always have been.

Design

• Cards across the portal share one hairline border and a light shadow, in both light and dark themes: Orders, Revenue, Invoices, Estimates, Tickets, Tasks, Resources, Intake, Contracts, Agreements, Products, Cloud Files, Transfers, Automations, Settings, App Integrations, Users, Campaigns, Dashboards, Knowledge Base and the single client, project, ticket, invoice, estimate, agreement and article views. Dark mode gets a proper dark border for the first time; it previously reused the light one.
• The Revenue charts sit on translucent glass panels with a crisp edge, and their colors follow your brand color, so they look intentional under any palette.
• The colored top strips on the Application Design and Login Page Design cards in Settings are gone.

Requires

• Add refund.created and refund.updated to your Stripe webhook endpoint's event list if you want refunds to appear on the Revenue page. Renewals use invoice.paid, which most installs already send.
• Multi-currency ledgers are shown one currency at a time; the Revenue page never adds different currencies together.

v4.107.0 — September 18, 2026

Design

• Invoice and estimate PDFs are set considerably smaller. Body copy drops three points and everything scales with it, so a page holds noticeably more before it breaks. The amount at the top came down too but is still the largest thing on the page.
• The invoice PDF header is quieter. The "INVOICE" wordmark is gone, replaced by "Invoice number:" set at the same size as "Bill To" and every other label. The "From" caption above your company address is gone as well, and there is now a clear blank line between the issue date and the PO / reference beneath it.
• The invoice PDF no longer prints your portal name or email address at the bottom. Both the line beside "Thank you for your business!" and the running footer carried them; the footer now shows the invoice number on its own.
• A line item's description sits clear of its title instead of running straight on underneath it.

Fixed

• Columns in the PDF header line up. The due date sat lower than the issue date beside it, and so did every other pair of side-by-side blocks in both PDFs. A stylesheet rule meant to top-align those columns never applied, so shorter ones drifted to the middle of the row. This has been wrong since the layout was written.
• A document whose number already began with the word no longer repeats it. An invoice numbered "Invoice E2-17597" opened in a browser tab titled "Invoice Invoice E2-17597", and printed the same way in the footer.
• Every existing invoice and estimate rebuilds its PDF the first time someone opens or downloads it.

v4.106.0 — September 18, 2026

Fixed

• The PO / reference number now appears on the invoice PDF. It has always shown on the invoice page but never in the PDF, because the two read the field from different places and the PDF's copy never included it. It prints under the issue date, the same place the estimate PDF has always put it.
• Invoice PDFs no longer print their status. "Draft", "Sent" or "Viewed" appeared as a coloured chip under the invoice number and again in the footer of every page. That is internal bookkeeping and tells the person reading the invoice nothing, so both are gone. Worth knowing: a draft invoice's PDF now looks exactly like a sent one, and an overdue invoice is no longer labelled as overdue — its due date and balance still show.
• Estimates keep their status, where "Accepted" or "Declined" does tell the reader something.
• One name for one field. A client could receive an invoice PDF saying "PO / Reference" and an estimate PDF saying "PO Number" for the same thing; both now say "PO / Reference".
• Existing invoices and estimates rebuild their PDF the first time someone opens or downloads one.

v4.105.0 — September 18, 2026

Design

• Invoice and estimate PDFs have been redrawn to read like a printed document rather than a web page. Almost nothing is bold any more. Section and column labels — Bill To, Issue Date, Description, Notes — are sentence case in your brand colour instead of small grey capitals. The two grey filled areas are gone: the band behind the column headers is now a coloured rule above the line items, and the totals box is now plain ruled rows.
• Body text, addresses and item details are all a step larger, and the amount at the top of the page is much bigger, so the eye lands on what is owed. The total beside the figures is correspondingly smaller, because it no longer has to compete with it.
• Nothing moved. The same information is in the same place; only its size, weight and colour changed.
• Your brand colour is used for the labels and the rule. Where a brand colour is so dark that labels would be indistinguishable from the text beside them, it is lightened just enough to tell them apart, so the hierarchy holds whatever colour you use.
• Every existing invoice and estimate rebuilds its PDF the first time someone opens or downloads it.

v4.104.0 — September 18, 2026

New

• Choose whether the billing contact's email address prints on your documents. A new switch under Settings → Invoice Settings → Bill To Block: "Show the billing contact's email address". It is on by default, so nothing changes until you turn it off.
• The contact's name always prints. Turning the switch off shows the name and the postal address only, on invoices and estimates alike, on screen and in the PDF.
• It does not change who an invoice is emailed to — that still follows the client record. It does not hide your own company email in the document footer. And the contact picker you use while building an invoice still shows email addresses, so you can still tell two people with the same name apart.
• Documents that already have a saved PDF rebuild it the first time someone opens or downloads it after you change the switch, so an older invoice or estimate cannot keep handing out a PDF with the email still in it.

v4.103.0 — September 18, 2026

New

• Pick who an invoice or estimate is addressed to. A Billing Contact dropdown sits under the client on every create and edit screen, listing that client's own people with their user label — "Jane Doe — Accounts Payable". It starts on whoever the client record designates as the billing contact, and you can switch it for a single document without changing the client's default. Changing the client clears the choice, because that person belonged to the old one. Leave it on "Use the client's billing contact" and nothing about the document changes. This affects who the document is addressed to on screen and in the PDF; it does not change who the invoice email is sent to, which still follows the client record.
• Line item descriptions hold more than one line. The description box is now a text area that grows as you type, and pressing Enter starts a new line instead of doing nothing. Those breaks appear everywhere the item does — the invoice and estimate pages, the split-panel views, both PDFs, and the live preview while you type. The remembered-item autocomplete is still there, now as a dropdown you arrow through: Enter takes the highlighted suggestion, and with nothing highlighted Enter is simply a line break.
• Invoices and estimates that already have a saved PDF will rebuild it the first time someone opens or downloads it, so existing documents pick up both of the above rather than serving the older cached file.

Fixed

• Line breaks in a line item's description stopped disappearing. The previous release fixed this for the Details box underneath, but the Description field itself was a single-line input that could not hold a line break at all. Both fields now keep what you type. Descriptions and details saved before these two releases were flattened in the database and cannot be recovered — those items need their line breaks typed once more, and then they hold.

v4.102.0 — September 18, 2026

Security

• Client billing details are no longer readable without signing in. A client's record carried its billing block — the postal address, and as of this release the billing contact's name and email — to anyone who requested it over the site's public data feed, signed in or not. That block is now withheld from anyone who cannot edit the client. Nothing inside the portal changes: staff still see it in the invoice and estimate screens, and a client still sees their own details on their invoice, which is built on the server and never went through that feed. No action is needed on your part; the fix applies as soon as the theme updates.

New

• Invoices and estimates now address a person, not just a company. The client's Billing Contact prints under the company name and above the address, with their email below it — on the invoice and estimate pages, in both PDFs, in the split-panel views, and in the live preview inside every create and edit window. Set the contact on the client record under Billing. This does not change who an invoice is emailed to, and it does not create a contact for you: a client with no Billing Contact set shows the same company block it always did.
• Line item details can hold a real list. A line that starts with a dash, an asterisk or a bullet character becomes a bulleted list item, and any other line stays as its own sub-line under the item name. The PDF already read details this way; now every on-screen view matches it, so what you type, what your client reads in the browser, and what lands in the PDF all agree.
• Item details now appear in the split-panel invoice and estimate views. Those panels previously showed a line item's name, quantity and amount and dropped its details entirely.

Fixed

• Line breaks in a line item's details stopped disappearing. Typing a multi-line description on an invoice or estimate saved it as one run-on line: the text looked correct while you typed and was flattened the moment you saved. Details you saved before this release were flattened in the database and cannot be recovered — those items need their line breaks typed once more. Anything you type from now on holds.

v4.101.0 — September 17, 2026

Tasks, Invoices, and Estimates — a smoother edit experience

• My Tasks: when the task list is squeezed narrow, such as when you have an invoice, estimate, or ticket pinned open beside it, the Quick Stats and Tags panel now tucks away behind a menu button instead of crowding the list. Tap the menu button to slide it out; tap the X, the dimmed area, or press Escape to close it. Nothing is removed — the full two-column layout returns on its own as soon as there is room.
• My Tasks: the filter tabs (All Tasks, To Do, Completed, and so on) now use a slightly smaller label to match the rest of the portal.
• Invoices: fixed the Edit Invoice screen opening behind the left sidebar when you edit from an invoice's own page. It now opens full-screen, the same as editing from the Invoices list.
• Estimates: the Edit button on an estimate now opens the full-screen estimate editor, including its line items. It previously did nothing when clicked.

v4.100.0 — September 17, 2026

Drag records straight into categories

You can now organize your directories by dragging. On Projects, Clients, Locations, and Assets, grab the handle at the start of a row — or a card, in the Clients grid — and drop it onto a category in the left sidebar to file it there, without opening the record. Drop it on "All categories" to clear the category instead. If you have rows selected with the checkboxes, dragging any one of them moves the whole selection at once.

Assigning a category this way replaces the record's category rather than adding a second one — each record still belongs to a single category, exactly as it did before. Nothing is re-filed automatically on upgrade; records keep the categories they already have until you move them.

The Assets filters now work

The filter controls on the Assets directory were not doing anything, and they are fixed. Changing the Client, Location, or Status now applies right away; the Location list fills in with the locations for the client you pick; and Reset, Sort, the install-date ranges, and the column show/hide menu all work. Filtering by a location that has assets on it also no longer comes back empty.

Locations: "Assign to category" for a selection

Selecting several locations and choosing "Assign to category" now files them all. That button previously did nothing.

v4.99.0 — September 17, 2026

Fixes

• Pinned invoices and estimates now show their line items correctly in the side panel. On larger amounts the figure could be cut off at the right edge of the panel; the table now fits the panel at any width, wraps long descriptions, and keeps the full amount in view.

v4.98.0 — September 16, 2026

v4.98.0 — Send big batches of files without hitting a wall

Clients uploading a large batch of files to a transfer link (for example a folder of images) could hit a "too many requests" error after about a hundred files. Uploads now have a much higher hourly allowance and no longer compete with downloading — so large transfers go through, and files continue to upload straight to your cloud storage as before.

v4.97.0 — September 16, 2026

v4.97.0 — Messages now show their body

Fixes a bug where a message created for you — by the assistant, by an automation (like a new-ticket auto-responder), by an asset service reminder, or by an intake form's follow-up — could appear in the inbox with an empty body and no bubble. These messages now display their text correctly. (Messages already sent while the bug was present aren't changed.)

v4.96.0 — September 16, 2026

v4.96.0 — Message anyone by name, in a click

• Ask the assistant to send a message and it just works: name the person ("message Tim about the proposal"), and it finds the right contact, drafts the note, and asks you to confirm before sending. If the name is unclear or matches more than one person, it asks who you mean instead of guessing — so a message never goes to the wrong person.

v4.95.0 — September 16, 2026

v4.95.0 — Set up products by chat, and a cleaner checkout

• Products & pricing from a chat. Ask the assistant to create a plan or a one-time product, bundle products into a group, or spin up a pricing page — it walks you through it and hands you a link to what it made so you can review and publish. You can also connect an intake form to a product to onboard buyers automatically after they purchase.

• A cleaner checkout. The Activate checkout page now runs edge to edge, with the order summary filling the full width, and is kept distraction-free so buyers stay focused on completing their purchase.

v4.94.0 — September 16, 2026

v4.94.0 — Your assistant sets things up, and shows you where

Describe what you want, and the assistant builds it for you:

• Automations from a chat. Ask for an auto-responder that acknowledges every new support ticket, a thank-you when an invoice is paid, reminders for overdue invoices, or a heads-up before a subscription renews — the assistant sets it up as a draft you can review, test with a dry run, and switch on when you're ready.

• It links what it makes. When the assistant creates an intake form or an automation, it hands you a link straight to it, plus a short note on how to put it to work with clients.

• Forms that start workflows. When a client submits an intake form, an automation can now notify your team and open a follow-up task automatically.

• Friendlier "add a user." Ask how to add a user and the assistant offers to add them with you right there — or points you to User Management for the full form and bulk uploads.

v4.93.0 — September 15, 2026

Maintenance: retired legacy API endpoints removed

This release finishes retiring a set of old per-resource API endpoints that were replaced by the single governed tools endpoint used by the AI assistant and the MCP bridge. Those old endpoints had already been answering "Gone — use the new endpoint" since 4.82.0, and monitoring confirmed nothing was still calling them, so they have now been removed entirely.

• There is no change to how the portal, the AI assistant, or the MCP integration behave — those all use the current tools endpoint and are unaffected.
• If you built a custom script directly against one of the old clientcove/v1 project, ticket, or resource endpoints, it now returns a standard 404 instead of the previous "Gone" notice. Point it at the current tools endpoint (see docs.clientcove.io).
• No settings change and nothing to do on upgrade.

v4.92.0 — September 15, 2026

Two new tabs on every client page: Billing and Agents

Open any client and you will find two read-only tabs that pull together information that used to live in several places.

Billing shows the rate card in effect for that client — where the rate comes from, what has been used against it, and the price that applies right now. If you set a client-specific override, an editor on the tab lets you adjust it; with no override the client simply inherits your default rate card, and the tab says so plainly.

Agents shows what AI agents are doing for that client, in three parts:

• Waiting on a person — approval requests and drafts for this client that still need someone to act.
• Recent activity — the agent actions recorded under this client, most recent first.
• Agents that can act on this client — the agents whose scope includes it, each with a link to open them.

A few things the tabs deliberately do not do. The Agents tab is a view only: approvals, denials, and replies still happen in the agent inbox, not here. An agent's private instructions and the exact details of its calls are never shown on the tab. Both tabs appear only for people who can already view the client.

Nothing changes for your existing clients until you open a page. No rate cards are created or altered on upgrade — a client with no override keeps inheriting your default. Agent activity recorded before this release is listed honestly as recorded without a client rather than guessed onto the wrong one.

v4.91.0 — September 15, 2026

Plans & Rate Cards in the portal

Rate cards and plan scope no longer live only behind the admin screens. System Settings gains a Plans & Rate Cards panel that shows every rate card with its source: the account default, each subscription plan with its subscriber count, and each client override.

• See which plan any client resolves to: pick a client and the panel shows the override → plan → account default chain with the step in effect highlighted, the rate card in effect, and this period's usage — the same answer the assistant gives.
• Edit the account default, a plan's card, or a client override in place. Every save is validated as a whole: work types must be unique on a card, rates cannot be negative, and nothing is saved partially.
• A plan or override with no rates says so plainly ("no rows — estimates come back needs-pricing") instead of looking as if it borrows from the account default; it never does.
• Turning a client override off keeps its rows for later and only switches the override off.
• The account default stays the fail-safe: it can be Always billable or Feature scope, never a metered allowance.

Who can edit: the account default and plan cards need the settings permission; a client override needs client-edit rights on that client.

v4.90.0 — September 15, 2026

v4.90.0 — The assistant knows your agents by name

Ask the assistant about your agents the way you would ask a colleague.

• The assistant sees your agent situation live: which agents are active, paused or revoked, and what is waiting on you — approval requests and drafts, soonest-expiring first. "What's waiting on me?" and "Show my agents" are answered on the spot, and two matching suggestion chips appear when you have agents.
• Name an agent instead of hunting for its id: "pause Brief", "approve the Acme reply", "show what Books did today". An ambiguous name gets a short list to pick from, never a guess.
• A pending confirmation only commits on a clear yes. "Ok, but first show me the invoice" now shows you the invoice and keeps the action waiting; "no, use the other client instead" is a question, not a cancel.
• Chat in bring-your-own-key mode sends a much smaller prompt on every message, so replies start faster and cost less.
• The Actions menu on a client's page works again: archive, move to trash and permanent delete.

v4.89.0 — September 15, 2026

v4.89.0 — Agents can check on their own requests and drafts

Agents can now check on their own approval requests and drafts.

• Two new tools every preset includes: an agent can list its own approval requests and its own drafts, each with what to do next — wait and check again, run the approved action now, don't retry a denied one, or ask again after an approval lapsed. No more blind retrying.
• Only the agent itself can read its list. People keep the Agents tab and the assistant's own tools; nobody sees another agent's queue, and the lists never include the draft contents or anyone's name.
• Approvals that lapse before the agent uses them are now marked expired everywhere, and an agent's own inbox tools can never be set to require approval themselves.

v4.88.0 — September 15, 2026

v4.88.0 — Pause an agent, and restore a revoked one

Pause an agent without losing its setup, and restore a revoked one — an admin's stop can only be undone by an admin.

• Pause: the agent keeps its tools, client scope and tokens, but nothing it calls will run until a person resumes it. Its client is told plainly that it is paused. No new token can be issued while paused.
• Restore: a revoked agent's identity can come back — with an empty keyring and no tokens, so you re-key it and issue a new token before it can act again. Revoking now also cancels any approvals the agent was still waiting on.
• Who can undo a stop: an owner can resume or restore only a pause or revoke that was theirs; a user-management admin can undo any. The agent panel shows who stopped an agent and when, and explains when only an administrator can undo it.
• The Agents tab shows Paused alongside Active and Revoked, with its own filter, and the assistant can pause, resume and restore agents for you (after you confirm).

v4.87.0 — September 15, 2026

v4.87.0 — Standing instructions, guided connect, and agents on your phone

Give each agent standing instructions it reads when it connects, copy a ready-made connection snippet for Claude Code, Cursor or Claude Desktop, and manage agents comfortably from a phone.

• Standing instructions: write the persona and standing orders for an agent when you create it or from its panel (up to 4,000 characters). The agent receives them when it identifies itself over MCP, and the assistant can read and update them for you.
• Add to a client: the agent panel's Connect section now hands you a ready-made snippet for Claude Code, Cursor or Claude Desktop, with the steps to follow and a clear note that claude.ai's own connectors sign in as you, not as an agent. Tokens are never pasted into a snippet for you.
• The Connect section also tells you when MCP is enabled but the site wasn't reachable on public HTTPS, and warns when an agent can't identify itself yet because the whoami tool isn't on its keyring.
• The Agents tab and the agent panel were checked on a phone-sized screen: the panel fills the width, the client picker and connection steps stack cleanly, and long snippets scroll.

v4.86.1 — September 15, 2026

v4.86.1 — Agent tokens that last, and a fix for the Agents tab's forms

• Agent MCP tokens now last 30 days instead of 1 hour, so an agent whose MCP client only holds a bearer keeps working without a refresh dance. Your own connections are unchanged (1-hour tokens, refreshed by your client). Revoke tokens in the agent's panel, or revoke the agent, still cuts a token off immediately. Installs can tune the agent lifetime between 1 hour and 90 days with the cove_mcp_oauth_agent_access_ttl filter.
• Fixed: in 4.86.0 the New agent form and the agent panel's Edit form lost their styling (the autonomy switch, tier pills, client-scope grid and all-clients switch showed as plain checkboxes and text). They look right again, on desktop and on phones.

v4.86.0 — September 15, 2026

v4.86.0 — Every agent gets its own detail panel

Every agent now has its own detail panel: see what it may do, what it has done, connect it, or revoke it — all in one place, and nothing on the Agents tab reloads the page any more.

• Click any agent to open its panel. Overview shows who owns it, its model, autonomy, tier ceiling, client scope and what is waiting on you, with Edit right there.
• Keyring: grant or remove tools, require confirmation per tool, or apply a Brief, Studio or Books preset to an existing agent. Tools the agent can't hold are listed, never silently dropped.
• Activity: the agent's audit trail with tool and outcome filters.
• Connect: the site's connector URL, a token issued and shown once with its lifetime, live connections, and revoke tokens.
• Revoke lives in a clear danger zone; a revoked agent's keyring becomes read-only.
• The agent list updates in place after every change — creating, editing, re-keying or revoking never reloads the page.
• Share a link straight to an agent's panel from the Agents tab.

v4.85.0 — September 15, 2026

v4.85.0 — A cleaner Agents tab

A cleaner Agents tab: one inbox for everything waiting on you, a searchable agent list, and agents are visible only to their owner and admins.

• One inbox: approval requests and drafts appear in a single list, most urgent first, with counts you can filter by. Approve, deny, publish or discard right there, without leaving the tab.
• A badge on the Agents tab shows how many items are waiting for you.
• Search your agents by name, filter by active or revoked, and (for admins) by owner.
• Each agent row shows what is pending, how many connections it has, and when it was last active.
• Visibility is now consistent everywhere: an agent can be seen, edited, re-keyed or revoked only by its owner or a user-management admin, matching what the assistant already enforced.

v4.84.0 — September 15, 2026

v4.84.0 — Approve, deny, publish and manage your AI agents from the assistant

Act on your agents without leaving the conversation. Following last release's status tools, staff can now tell the portal assistant to approve or deny an agent's pending request, discard a draft (or publish it), and manage agents outright — rename them, change their model, autonomy or permission ceiling, adjust their client scope, grant or remove tools, revoke them, or create a new one from a preset. Every action asks you to confirm first, runs with exactly the same permissions and audit trail as the Agents tab, and is refused for anyone who isn't the agent's owner or a user-management admin. Agents themselves can never use these tools, they cannot be run by automations or on someone else's behalf, and connection tokens are never issued through chat.

Safer confirmations everywhere. The assistant no longer sees the confirmation code behind a destructive action — only your YES or CANCEL can commit it, on every AI provider. This closes a path where a model could have confirmed an action by itself inside a single turn, and it applies to all destructive actions, not just the new agent ones.

v4.83.0 — September 15, 2026

v4.83.0 — Ask the assistant about your AI agents

Your AI agents, on demand. Staff can now ask the portal assistant — in the in-portal chat, or from any connected MCP client signed in as themselves — what their AI agents are doing and what is waiting on them. Five new tools answer it: list agents (each agent's owner, model, autonomy, permission ceiling, client scope, granted tools, active or revoked, and live counts), get agent (one agent in full, with its recent activity), agent activity (its audit trail), agent requests (live actions awaiting your approval, with whether each is still actionable) and agent drafts (work waiting for a human to publish).

Built to be safe to ask. You only see agents you own — or every agent, if you manage users. Agents themselves can never use these tools. Anything an agent wrote (request summaries, draft titles, activity messages) is returned clearly marked as agent-authored text so the assistant reports it rather than acting on it, and the full draft bodies, raw inputs and credentials are never included. Approving, denying and publishing still happen in the Agents tab; the next release brings those actions to the assistant too.

v4.82.0 — September 15, 2026

v4.82.0 — Unified tools API: legacy endpoints retired, ticket priorities aligned

Retired the old per-resource API endpoints. The early per-resource endpoints (projects, resources, tickets, board cards and lists) have been replaced by the unified tools API that the MCP bridge uses for everything. They now answer 410 Gone with a pointer to the replacement, are no longer listed in the API index, and each install keeps a private count of any remaining calls so nothing is removed while it is still in use. Every capability lives on as a tool of the same name; the hosted MCP bridge switched over ahead of this release, so connected AI clients need no change. If you self-host the bridge, update it.

Ticket priorities are consistent everywhere. Tickets opened or updated through the API stored their priority in a different spelling from the portal, so they showed no priority badge and never matched an "Urgent" rule. They now use the portal's own Low / Medium / High / Urgent labels — including tickets created from inbound email — the API's update_ticket tool can set priority and product, or clear a due date, and priority conditions in automations match by label, so existing rules keep working.

Quick-action New Ticket modal fixed. The dashboard's New Ticket quick action now files through the same path as the Ticket Form widget; staff pick the client, clients file against their own account.

v4.81.1 — September 14, 2026

A new Setup Wizard builds your portal around your business

Answer five questions and ClientCove turns on the right features, creates the pages and navigation for them, adds starter content, and sets your logo and colors. About five minutes from activation to a working portal.

• Start it from the Welcome to ClientCove notice in WordPress admin, or any time from Settings → Setup inside your portal. The old setup page under Tools now sends you there.
• Five question cards: what kind of business, what you deliver, how you get paid, who will log in, and a sentence about your business. Every option shows what it turns on.
• Your answers become a blueprint you can edit before anything is written: modules, pages, the three navigation menus, starter content, and a suggested palette. When AI is connected the blueprint is written for your business; without it you get the built-in recommendations, and either way you can finish offline.
• Applying is additive and safe to repeat. Existing pages are reused, menus that already have items are left alone, and a setting you have already saved is never overwritten. If a step fails, only the failed steps re-run.
• Look & feel in one screen: logo, palette, accent, color mode, and a login welcome line, with live previews of the portal and login page. The Login Page Designer still handles video backgrounds, custom links, and layout.
• The finish screen explains how each feature you turned on works, written for your business, and leaves a Finish setting up checklist on your dashboard until it is done: connect your email sender, connect Stripe, invite your team, add your first client, polish the login page, add your logo, and (optionally) move to cloud storage. Items tick themselves off as you complete them.
• File Transfers, Messages, and AI Features are on for every kind of business. A feature you already use on an existing site is never switched off.

Your home page is a real dashboard from the first login

• The wizard now assigns each role's dashboard to the Welcome page and gives it starter cards: a welcome message, quick links to the pages you have, and, for administrators, counts of clients, projects, and open tickets. Previously a fresh site landed on "No Dashboard Assigned".
• Dashboards you have already customised are not touched. Starter cards are added only to a dashboard that has none.
• Administrators who reach a page with no dashboard now get a link to Dashboards instead of "contact an administrator".

Fixes

• Site Health no longer reports a fatal error on a fresh install.
• The getting-started intake form was skipped by the wizard's starter content on every new site; it is created now.
• The setup notice on the WordPress dashboard describes what the wizard actually does.
• A console error no longer appears on the login and setup pages.
• WP-CLI commands no longer re-run a one-time user migration on every invocation. It is now its own command, wp cove messageable-migrate.

Nothing changes on an existing site until an administrator opens the wizard and applies a blueprint.

This release contains the same code as 4.81.0, which shipped minutes earlier with only the feature-scope plan notes. Everything above was already in 4.81.0; this note completes the record.

v4.81.0 — September 14, 2026

Feature-scope plans: show the included scope, and never assume it's covered

For portals that use AI agents, plans whose coverage is described in words — rather than a set number of requests or hours — are now handled correctly everywhere billing scope is shown.

• On a feature-scope plan, the ticket and the triage note now show the plan's described coverage and a clear prompt to review the plan scope and decide — never a "within allowance" badge, because there's no number to count against.
• The described scope is pulled from the plan and shown to your team so they can judge whether a request is included; the agent surfaces it and prepares a draft, and you make the call.
• Estimates on feature-scope plans are still priced from your rate card as usual.

What it does not do:

• It never decides on its own whether feature-scope work is covered or billable — that's your judgment against the described scope. The agent will not draft a "no charge" reply for a feature-scope plan.
• The plan's described scope is staff-only; your client never sees it.

Where to set it: a subscription plan can use Feature Scope as its allowance type, with the coverage written in the plan's features. Nothing changes until you configure a plan that way.

v4.80.0 — September 14, 2026

Automatically flag new requests for billing triage

For portals that use AI agents, you can now have new client requests flagged for billing review the moment they arrive — so nothing sits unquoted.

• Turn on the "New request: flag for billing triage" automation. When a ticket of a type you've designated as a request is opened, the system posts a staff-only note on that ticket showing where the client stands against their plan — within allowance, over allowance, or always billable — with a prompt to reply or prepare an estimate.
• The note is computed by the system from the client's own plan usage, not by the agent, and it appears once per ticket.
• From there you review it and act — draft a covered reply or a priced estimate — exactly as you do today.

What it does not do:

• It only flags — it never replies to the client, never creates or sends an estimate, and never charges or waives anything. Every client-facing action stays a person's decision.
• The triage note and the plan-usage numbers are staff-only; your client never sees them.
• It runs only for the request ticket types you've configured, and only when a plan is set up — otherwise it does nothing.

Where to turn it on: the Automations page — enable the "New request: flag for billing triage" recipe. Nothing changes until you enable it and configure your plans and request types.

v4.79.0 — September 14, 2026

Review agent-drafted estimates from one place on the Estimates page

For portals that use AI agents, agent-prepared estimates now gather in a "Pending agent estimate drafts" queue at the top of your Estimates page — so you can review and publish them from the pipeline, not only from each ticket.

• The queue shows each drafted estimate with its client, the ticket it answers, the line items and total, and — for plan-based clients — the same plan-usage summary you see on the ticket. Publish or discard each one right there.
• Publishing creates the real estimate as you (never as the agent) and it appears in your estimates list immediately; the client is not emailed until you send it.
• The same safeguards apply here as on the ticket: a line that still needs a price blocks publishing, and for an hours plan the system re-checks the client's current usage at publish, so the estimate always bills the right hours.

What it does not do:

• You only see drafts you are allowed to act on; the queue never shows an estimate you could not publish, and plan usage stays staff-only.
• Nothing is created, changed, or sent until you publish — the agent only prepares the draft.

Where it shows up: at the top of the Estimates page, for staff who can publish estimates, whenever an agent has estimates waiting for review. Nothing changes until an agent drafts one.

v4.78.0 — September 13, 2026

Bill only the hours beyond an hourly plan — the system does the split

For portals that use AI agents on hours-per-month plans, an agent can now prepare an estimate that charges only for the hours a request runs over the client's included time — and it can never quietly under-bill.

• The agent proposes its estimate of the total hours for a request; the system subtracts the hours still included in the client's plan and prepares an estimate for only the overage, priced from your rate card.
• The estimate card shows you the split — the agent's estimated hours (marked as an estimate), the hours the plan covers, and the hours that would be billed — so you review it before publishing.
• When you publish, the system re-checks the client's current plan usage. If they have logged more hours since the estimate was prepared, publishing is held and asks you to re-draft, so the estimate always bills the right number of hours.

What it does not do:

• The agent never sets a price, and never decides on its own what is covered — the hours still included come from the system's own count, and you publish. The agent's hours figure is only a starting estimate, clearly marked as unverified.
• If the plan usage can't be confirmed, the request is quoted in full rather than assumed covered — nothing is given away by mistake.
• The plan, the included hours, and the usage math stay staff-only; your client sees only the hours being billed.

Where it shows up: on a ticket for an hours-per-month client, when an agent prepares an estimate. Nothing changes until you configure an hours plan and open a ticket.

v4.77.0 — September 13, 2026

See where a client stands against an hourly plan allowance

For portals that use AI agents, a ticket can now show a client's usage against an hours-per-month plan — so you know how much of their included time is left before you quote new work.

• Set an allowance in hours on a plan or a client — for example "20 hours per month". As billable time is logged on that client's tasks, the system keeps a running total for the current period.
• When an agent drafts an estimate on the client's ticket, the card shows the plan and the hours used this period, with a clear "over allowance" or "within allowance" badge. The total is computed by the system from the client's own logged hours — not by the agent.
• Hours are counted from the point the feature is switched on. Until a full period has passed, the ticket marks the figure as still filling in, so an early, partial total is never mistaken for the final count.

What it does not do:

• It never charges, waives, or sends anything on its own. It shows you the hours used and prepares a draft; you decide and publish.
• For hourly plans it does not guess whether a new request "fits" — it shows the hours remaining and leaves the reply-or-estimate decision to you.
• Nothing here is shown to your client — the plan, the allowance, and the hours used are staff-only, on the ticket.

Where to set it: a subscription plan (and a client, to override) can now use an hours-per-month allowance alongside the request allowance and rate card. Nothing changes until you configure a plan and log billable time.

v4.76.0 — September 13, 2026

Confirm a request is covered by the client's plan — and reply, no charge

Following the plan-usage badge on estimates, an agent can now also handle the other side of the request: when a ticket is within the client's monthly plan allowance, it drafts a short "this is included in your plan" reply for you to review — and you confirm the no-charge decision yourself, on the ticket.

• On a ticket that's within allowance, the agent's drafted reply shows a green "within allowance" panel with the plan and the client's usage this month — the count is computed by the system from the client's own tickets, not by the agent.
• You have two clear actions: Confirm covered (no charge) & reply sends the drafted reply as you, or Confirm covered — no reply records the no-charge decision without sending anything. Either way, the decision is logged to the ticket's staff-only history.
• The drafted reply never mentions numbers, limits, or rates — your client simply sees that the work is included.

What it does not do:

• It never waives a charge on its own. Recording a request as covered is always your explicit action, and it's recorded with the system's own usage figures.
• If the client is actually over their allowance, the covered path is not offered — the system steers you to an estimate instead, so nothing is quietly given away.
• Nothing here is shown to your client: the plan, the allowance, and the usage count stay staff-only, on the ticket.

Where it shows up: on a ticket, when an agent has drafted a covered reply and the client is within their plan's monthly request allowance. Nothing changes until you configure a plan allowance and open a ticket.

v4.75.0 — September 13, 2026

Know at a glance when a request is over a client's plan

For portals that use AI agents, a ticket now tells you where a client stands against their plan's monthly request allowance — so you can see when new work is billable before you quote it.

• Set an allowance on a plan or a client — for example "3 requests per month" — and choose which ticket types count as a request.
• When an agent drafts an estimate on a ticket, the estimate card shows the plan and the client's usage this month, with a clear "over allowance" or "within allowance" badge. The numbers are computed by the system from the client's own tickets — not by the agent — so what you see is the real count.
• Prices on the drafted estimate still come only from the rate card you set; nothing is invented, and you review and publish it yourself.

What it does not do:

• It never charges, waives, or sends anything on its own. It only shows you the plan usage and prepares a draft; you decide and publish.
• Nothing here is shown to your client — the plan, the allowance, and the usage count are staff-only, on the ticket.
• Until you set which ticket types count as a request, the system treats requests as billable rather than assuming they are covered, so nothing is quietly given away.

Where to set it: a subscription plan (and a client, to override) now has an allowance and a list of request ticket types, alongside the rate card. Nothing changes until you configure a plan and open a ticket.

v4.74.0 — September 13, 2026

Review agent-drafted ticket changes and priced estimates, right on the ticket

For portals that use AI agents, more of an agent's work now arrives as a draft you review in place — and nothing goes out until you publish it.

• Ticket changes. Alongside drafted replies, an agent can now propose a ticket's status or assignment change. It appears as a card on the ticket showing exactly what would change; publish it to apply the change and notify the ticket's people, or discard it. Publishing acts as you.
• Priced estimates from a ticket. An agent can draft an estimate in response to a request. It shows on the ticket as a line-by-line quote with a total, for you to review and publish as an unsent estimate. You publish and send it — the agent cannot.
• Your rates set the prices. Estimate prices come only from a rate card you define — set named rates (for example Design, Development, Consulting) on a subscription plan, or per client. Any line whose work type has no rate is marked "needs pricing" so you set it before publishing; the agent never invents a price.

What it does not do:

• An agent never publishes, sends, or applies anything on its own. Publishing a change, publishing an estimate, and sending it are always a person's action, done as that person — your client sees it from you, never from the agent.
• A drafted estimate is created unsent, and it cannot be published while any line still needs a price.
• Your rate card, and everything the agent used to prepare a draft, stay internal — they are never shown to your client.

Where to set rates: a subscription product now has a rate card and scope settings; a client can override them. If you set none, drafted estimate lines simply come through unpriced for you to fill in. Nothing changes until you open the ticket.

v4.73.0 — September 12, 2026

Review and publish AI agent work, right where the work lives

For portals that use AI agents, an agent can now prepare more of your day-to-day work as a draft for a person to review, and you approve it in the normal portal screens — nothing an agent prepares goes out until you publish it.

• Agents can draft a reply, a to-do, an intake form, a ticket update (status or assignment), an automation, or an estimate. Each one waits as a draft until a person publishes it.
• Review a drafted ticket reply right on the ticket. A card above the reply box shows the proposed reply; publish it and it posts as your reply, or discard it. You never leave the ticket to approve it.
• When you publish an agent's draft, it goes out as you — your client sees it from you or your team, never from the agent. Your ticket's internal history records which agent drafted it, for your own accountability.

What it does not do:

• An agent cannot publish anything itself, and it cannot send an estimate or enable an automation. Publishing, sending, and enabling are always a person's action. A drafted estimate is created unsent; a drafted automation is created switched off until you turn it on.
• Agents only ever act within the clients you scope them to, and only with the tools you grant them. An agent can only prepare drafts using tools at the "draft" level — it can never be given a tool that sends or posts on its own.

A privacy fix for ticket history

A ticket's internal history and staff notes are now sent only to your staff — never included in the data a client's browser receives. The internal history drawer was already staff-only on screen; this closes the underlying data as well. Clients see no change; nothing you do changes.

v4.72.0 — September 11, 2026

A redesigned User Management page

The whole User Management area has been rebuilt to match the rest of your portal, with the same clean look as your intake and project pages. Client Users, Contractors, Techs & Staff, and Permissions all work exactly as before — only the look and feel has changed.

• The page is easier to scan, reads better on smaller screens, and reopens on the tab you were last using.
• Nothing about who can see or do what has changed. Your existing users, roles, and permissions carry over untouched.

Clearer AI agent setup

For portals that use AI agents, adding an agent is now a guided flow rather than a form.

• Creating an agent walks you through what an agent is, what it is allowed to do, and which clients it should be limited to, so you can set one up without guesswork.
• You can start from a ready-made template and adjust from there instead of configuring every agent from scratch. Each template only turns on the tools an agent is actually allowed to hold, and tells you when a tool was left off.
• Fixed: an agent's assigned clients now always save and display correctly. Before this release an agent could be created but show "No clients" even when a client had been selected, and it would act as if it had no client access.

Nothing changes until you open the page. Your users, roles, and permissions are exactly as you left them.

v4.71.1 — September 8, 2026

Google file links: refinements

Follow-up improvements to linking Google Drive and Docs files, which arrived in 4.71.0.

• Messages: each linked Google file now sits directly under the message it was sent with, joined by a connector line, so it is clear which reply it belongs to. Expanding a file opens it at the full width of the conversation.
• Messages and tickets: a linked file now shows its real file name (for example "Proposal.docx") instead of a generic label, and appears on the message or reply right away without a page refresh.
• Resources: linked Google files are read-only while viewing a resource. You add or remove them from the resource's edit screen. This closes a gap where the add and remove controls appeared on the view screen.

Nothing changes until you link a file, and removing a link never changes or deletes the file in Google.

v4.71.0 — September 8, 2026

Link Google Drive files right inside the portal

You can now attach a Google Drive, Docs, Sheets, Slides, or folder link anywhere you share with a client: on a resource, on a brand-new message, on a message reply, and on a support ticket reply. Paste the share link and it appears as a titled card with the file's real name.

• Files such as Docs, Sheets, Slides, and PDFs get an "Expand preview" button that shows the file inline, without leaving the page.
• Every file and folder also gets an "Open in Google" button that opens it in a new tab. Folders open in Google rather than previewing inline.
• The card shows the file's real name automatically, for example "Proposal.docx", read from the shared link. A file shared with only specific people falls back to a generic name like "Google doc".

What it does not do:

• It does not upload, copy, or move anything. The file stays in your Google Drive and the portal only links to it. Removing a link never changes or deletes the file in Google.
• It does not change Google sharing and does not sign anyone in to Google. If a client cannot open a linked file, set that file's sharing in Google to "Anyone with the link", or share it to the client's email, and it will open for them.
• The inline preview depends on the viewer's browser allowing Google's cookies. If a preview comes up blank, the "Open in Google" button always works.

Nothing changes until you paste a link. There is no Google account to connect and no setup to do, so the feature stays out of your way until you use it.

v4.70.0 — September 8, 2026

ClientCove 4.70.0

Google Drive & Docs

• Link Google Drive and Docs files right into your portal. Paste a Google Drive, Docs, Sheets, Slides, or folder link onto a resource or into a message conversation and it appears as a card your clients can open in Google or preview inline — no downloading and re-uploading.
• A heads-up when a link isn't shared. If a linked file isn't set so your client can open it, ClientCove flags it with a "Check sharing" note, so you can fix the sharing in Google before your client hits a sign-in wall.

v4.69.7 — September 8, 2026

ClientCove 4.69.7

Messages

• Inserting a reference now works even when the person you're replying to isn't tied to a specific client, and in staff-to-staff threads. Staff can reference any client's items, so when there's no single client to narrow to, the picker searches everything you can access instead of coming up empty. When you're replying to a client contact, it still narrows to that client's items.
• Composing from an empty mailbox is easy again. When you have no messages (or none open), a "Send new message" button now sits front and center.
• No more sideways scrollbars in the message list or a conversation. Long subject lines are shortened in the list (the full subject shows when you open the message), and long links, embeds, and images in a conversation now wrap to fit.

v4.69.6 — September 8, 2026

ClientCove 4.69.6

Fixes

• The public Support page stays clean. Pinned items no longer appear on the /support/ page when you're signed in as staff — that page is a standalone public canvas, so the pinned side panel is now kept off it entirely.

v4.69.5 — September 8, 2026

ClientCove 4.69.5

AI assistant

• Your assistant keeps its name and face everywhere. The name and avatar you set under Settings → AI → Assistant Widget now appear on the pinned panel and the sidebar launcher too, not just inside the chat — so it never falls back to a generic "Assistant".
• The "Summarize this page" action is tidier, sitting on the assistant's status line instead of taking up its own row.

v4.69.4 — September 8, 2026

ClientCove 4.69.4

Pinned items

• Minimize a pinned item instead of closing it. A new minus button, next to the close button on a pinned panel, tucks it into a slim strip and it stays minimized as you move between pages — click the strip to bring it back. Minimizing keeps the pin; closing still removes it entirely.

v4.69.3 — September 8, 2026

ClientCove 4.69.3

Performance

• Messages stays fast as your account grows. The recipient picker no longer slows down as your team and client list get larger, and the message list now loads one page at a time instead of pulling your entire message history on every visit — so a big mailbox opens just as quickly as a small one.

v4.69.2 — September 8, 2026

ClientCove 4.69.2

Fixes

• Toolbar buttons on messages and tickets no longer go blank on hover. The pin, print, and more-actions controls now darken with a white icon instead of turning an unreadable white-on-white.

Changes

• On a message, Print and both delete options — delete for yourself, and, if you started the thread, permanently delete for everyone — now sit together under a single more-actions (three-dot) menu at the top of the conversation.
• The New message button now sits at the top of the open conversation, alongside those controls, rather than only above the message list.
• Message and ticket header buttons now share one consistent style, so the same control looks the same wherever you meet it.

v4.69.1 — September 8, 2026

ClientCove 4.69.1

• Pinned resources: opening a file from a resource pinned in the side panel now works — clicking a file preview opens the full-screen image/PDF viewer as it does on the resource page.

v4.69.0 — September 8, 2026

ClientCove 4.69.0

Ticket replies:

• Insert a reference: the ticket reply editor gains a reference button that lets you drop a link to a related resource, project, ticket, invoice, estimate or file transfer into your reply — searchable and scoped to the ticket's client.

• Send files onward: from a ticket's Files list you can now select attachments and send them to a project, add them to an existing resource, or create a new resource from them — the same file actions available in Messages.

• A cleaner reply toolbar and a redesigned submit button: the toolbar is now compact icons, and "Submit" is a split button whose caret opens a status picker (Open, Pending, In Progress, Hold, Closed) so you can set the reply's status in one place.

v4.68.0 — September 7, 2026

ClientCove 4.68.0

Tickets and message files:

• Pin alongside a ticket: opening a ticket with a pinned item now docks the pinned panel beside the ticket instead of hiding it, matching how the rest of the app handles pinned items.

• Cleaner ticket page: the buttons and status badges on a ticket are smaller and more condensed, so more of the conversation fits on screen.

• Message files reach their destination: sending a message attachment to a Resource or Project now actually adds the file (with its preview) to that Resource or Project. Previously the file could silently fail to appear.

v4.67.0 — September 7, 2026

ClientCove 4.67.0

More you can pin, and an assistant that reads the page:

• Pin invoices and estimates: open any invoice or estimate in the side panel from a new pin button on its page, and see a compact summary — number, status, who it's for, dates, line items and totals — with one click through to the full document. Their full pages also lay out correctly now when a pinned item is open, instead of being squeezed into a narrow column.

• Pin the assistant: a new button beside the sidebar "Pinned" heading opens the AI assistant in the side panel so it stays with you as you work. It includes a "Summarize this page" button that gives a short, plain-language summary of whatever page you're looking at — handy for getting your bearings fast.

• On asset and location pages, a long title no longer overlaps the client logo, and the title now scales to fit when the page is shown in a narrow side panel.

v4.66.0 — September 7, 2026

ClientCove 4.66.0

Working with a pinned side panel:

• Messages: opening the message list no longer hides the pinned item, and pinning an item no longer hides the message list. Whichever one you're not using tucks into a slim strip you can click to bring back, so both stay within reach side by side. The Files panel can also be collapsed to a slim strip to give the conversation more room.

• Account and Settings: when a pinned item makes these pages narrow, their side navigation now folds into a single dropdown at the top — the same style as the sidebar menu — so the page content gets the full width instead of being squeezed next to a nav column.

v4.65.0 — September 7, 2026

ClientCove 4.65.0

My Tasks in the sidebar panel:

• A new button beside the sidebar "Pinned" heading opens a compact My Tasks view in the side panel — Todos / All Tasks with Add task, Quick add, Bulk edit and Share. Expand any task to edit its note, due date, repeat, priority, time spent, client and tags without leaving the panel. The full task page remains one click away for everything else.

Dashboard:

• Dashboard widgets now reflow to the width of their area, so the dashboard looks right when it's shown alongside an open side panel instead of only reacting to the whole window size.

Resources in the side panel:

• Gallery, diagram, ad-group and web-preview resources now show a clean "open the full page" card in the side panel instead of a blank or stuck view, since those render best on their own page.

v4.64.0 — September 6, 2026

ClientCove 4.64.0

Resources:

• You can now pin a resource to the sidebar straight from the resources grid quick-view, without opening the full resource page. The pin button sits in the quick-view drawer header and shows whether the resource is already pinned.

v4.63.3 — September 6, 2026

ClientCove 4.63.3

Split-panel fix:

• When you open a pinned item's panel while already viewing that same item on the page, the panel no longer shows a blank "viewing this item on the page" placeholder. It collapses to a clean full-width page and re-opens automatically when you move to another page.

v4.63.2 — September 6, 2026

ClientCove 4.63.2

Resources in the split-panel:

• When a resource is opened in a pinned split-panel, its "Back to Resources" sidebar and related/attachments column are hidden so the resource content uses the full width of the panel.

v4.63.1 — September 6, 2026

ClientCove 4.63.1

Sidebar fix:

• Pinned items in the sidebar now reliably use the sidebar menu colour on every theme. On some colour schemes they were still picking up the site's link colour; this makes the menu colour win consistently.

v4.63.0 — September 6, 2026

ClientCove 4.63.0

Responsive record layouts:

• Assets, Locations and Tickets now collapse to a clean single column on phones, tablets, and inside a pinned split-panel — using tabs to keep every section reachable. The full-width two-column layout returns automatically when there is room. A pinned record on a wide screen no longer shows a cramped, squeezed two-column view.

Sidebar polish:

• Pinned items in the sidebar now use the same icon and text colour as the rest of the sidebar menu, instead of a mismatched link colour.

v4.62.5 — September 6, 2026

ClientCove 4.62.5

Settings polish:

• Every tab in the app settings navigation now shows an icon that matches its topic. Previously some tabs (Core Features, General, Design, Menus and others) rendered without an icon, leaving the menu looking unfinished.

v4.62.4 — September 6, 2026

ClientCove 4.62.4

Sidebar polish:

• In the chat view, the current-page selector button now uses the same text and icon colour as the rest of the sidebar menu, so it blends in cleanly instead of standing out in a slightly different shade.

v4.62.3 — September 6, 2026

ClientCove 4.62.3

Sidebar visual polish:

• The chat view's navigation dropdown now uses the same background as the sidebar menu, so the open menu blends in cleanly instead of standing out.
• On the Standard Block layout, the portal logo shows in the header as intended and no longer leaves an empty gap at the top of the sidebar.

v4.62.2 — September 6, 2026

ClientCove 4.62.2 — Sidebar toggle tint

A small visual fix: the active Menu/Chat toggle in the sidebar uses a lighter tint of your app's primary color so it reads as a subtle selection rather than a heavy fill.

v4.62.1 — September 6, 2026

ClientCove 4.62.1 — Sidebar polish and test coverage

A maintenance release. In the sidebar, the Pinned heading and your role now use the sidebar heading color so they read like the menu section headings instead of faint gray, and the active Menu/Chat toggle picks up your app's primary color. Under the hood this adds regression tests for the split-panel access gate and a local runner for the permission test suite.

v4.62.0 — September 6, 2026

ClientCove 4.62.0 — Split-view panels for pinned items

Open a pinned item in a panel beside the page you're on instead of navigating away. The panel opens on the side you choose, resizes with a drag bar, and stays put as you move between pages and refreshes. Resources, assets, locations, projects, tickets and message threads all open in the panel: tickets keep their full reply editor and a collapsible details sidebar, and message threads let you reply inline, jump to and highlight a message, and download attachments. Pin a message straight from its header, insert references when composing on a post, and on the Messages page the message list steps aside to make room for the panel.

v4.61.0 — September 6, 2026

ClientCove 4.61.0 — In-sidebar assistant, pinned items, page-aware chat

The sidebar now has an integrated Menu and Chat view. Pin the tickets, projects, resources, contracts, assets and locations you're working on to a Pinned section that persists across pages, and open the AI assistant right in the sidebar with context about the page you're viewing. Chat history persists across navigation and browser restarts. The collapsed rail shows centered icons and your avatar, and sign-out moves under your name with quick links to Account, Messages, Transfers and the Knowledge Base.

v4.60.2 — September 5, 2026

ClientCove 4.60.2

Quick access to the Crew Dashboard from the profile menu.

The profile dropdown (top-right, and the mobile sidebar version) now includes a Crew Dashboard link. Administrators see it at the top of the Admin section; assigned Crew Dashboard managers see it in their menu even without full admin access, so managers can jump straight to team oversight.

v4.60.1 — September 5, 2026

ClientCove 4.60.1

Outbound Email (Google Workspace / Gmail): clearer setup help.

The Gmail option now spells out where to get an App Password — with direct links to turn on 2-Step Verification and to Google's App passwords page — and notes Google's daily send limits (about 2,000/day on Workspace, fewer on personal Gmail), so you can pick the right provider for your volume.

Set it up: Outbound Email Setup.

v4.60.0 — September 5, 2026

ClientCove 4.60.0

Send outbound email through Google Workspace / Gmail.

Under Settings → Communication → Outbound Email, "My own outbound transactional email" now offers a third provider alongside SendGrid and Postmark: Google Workspace / Gmail. Enter your Google address and a 16-character App Password and notifications, magic links, ticket replies and invoices send over Gmail's SMTP (smtp.gmail.com, TLS). A "Test Connection" button verifies the sign-in.

Note: Gmail sends as the authenticated account, so your Sender Email must be that address or a verified "Send mail as" alias, and 2-Step Verification must be on to create an App Password.

Set it up: Outbound Email Setup.

v4.59.5 — September 5, 2026

ClientCove 4.59.5

Settings → License & Updates: the save/status message now appears below the page heading and above the Installed Version row, so confirmations show up in context rather than at the very top of the panel.

v4.59.4 — September 5, 2026

ClientCove 4.59.4

Consistent page titles across Settings.

Every Settings page now uses the same page-title heading — same size, weight, line height and spacing — so moving between Settings sections feels uniform. Previously each section styled its title differently.

v4.59.3 — September 5, 2026

ClientCove 4.59.3

Redesigned the Design Settings panel.

The two visual designers — Application Design and Login Page Design — are now the prominent pair at the top of Settings → Design, each with a plain-language description and a live preview, opening the App Designer and Login Page Designer. The logo and favicon uploads are grouped below under a "Brand assets" heading.

v4.59.2 — September 5, 2026

ClientCove 4.59.2

Fix: Settings navigation highlighted multiple items at once.

The Settings page's left navigation is grouped into collapsible sections (System, Appearance, Feature Settings, and so on), each its own tab set. Picking a tab in one group left the previously chosen tab in another group still highlighted. Now only the tab you're actually viewing stays highlighted, and any lingering highlights are cleared on load.

v4.59.1 — September 5, 2026

ClientCove 4.59.1

Fix: sidebar section highlighting.

• The homepage no longer wrongly highlights and expands the "Client Management" menu — only the Welcome item is marked active there.
• When you open a page inside a parent menu (Estimates, Invoices, Locations, etc.), that parent now stays expanded and highlighted while you're in the section, instead of collapsing.

v4.59.0 — September 5, 2026

ClientCove 4.59.0

Sidebar and portal UI polish.

• The main sidebar now highlights the section you're in — open a list like Tickets or Projects, or a single ticket, and its menu item stays lit (parent sections expand automatically).
• Tightened sidebar menu icons (size and spacing).
• My Tasks: tag chips show a smaller title and count, and their edit/delete buttons now appear only when you hover the chip.
• Messages: the Reply, Mark Unread and Delete actions are now clean icon buttons; Mark Unread uses an envelope-with-check icon.
• Projects: the list table is no longer all-bold, and the Last Modified and Status columns use a smaller, calmer size.
• Inline hint text (e.g. "Press Ctrl+Enter to send") is now a consistent size and weight across the portal.

v4.58.2 — September 5, 2026

ClientCove 4.58.2

Shared intake forms now appear in the Intake Manager for clients too.

Matching 4.58.1's search behaviour, a client's Intake Manager list now includes shared/global intake forms (those not assigned to a specific client) alongside the forms assigned to their client. Forms assigned to another client stay hidden.

v4.58.1 — September 5, 2026

ClientCove 4.58.1

Clients can now find shared intake forms in search.

Following 4.58.0's per-client search scoping, an intake form that isn't assigned to a specific client is treated as a shared/global form: every client can now find and start it from the header search. Intake forms assigned to a particular client remain visible only to that client.

v4.58.0 — September 5, 2026

ClientCove 4.58.0

Security: header search now scopes results to the client you belong to.

Previously the universal search could return records belonging to other clients to a signed-in client or contractor user. Search now filters every base result to what the viewer may actually see:

• Clients and contractors only get records for their assigned client(s) — projects, tickets, contracts, resources, assets, locations, invoices, intake forms — plus their own tasks, messages and file transfers.
• Looking up another client's record by number (e.g. "project 1021") no longer returns it.
• Marketplace items stay visible to everyone; staff, sales and reps are unaffected and continue to search across all clients.

Unknown record types are hidden from client search by default, so a future feature can't leak into a client's results before its access rule is set.

v4.57.0 — September 5, 2026

ClientCove 4.57.0

New: control what each audience can search, by area.

Under AI → Configuration → Search Options, a new "What each audience can search" panel lets you set every search area — People, Clients, Tickets, Projects, Tasks, Resources, Locations, Assets, Contracts, Intake Forms, File Transfers, Marketplace — to either Everyone or Staff only. "Staff only" hides that area from client and basic users while keeping it for your team, contractors, sales and reps.

Results are always scoped to what a user can access; this simply controls whether an area shows up in search at all. Everything defaults to Everyone, so existing installs are unchanged until you restrict an area.

v4.56.0 — September 5, 2026

ClientCove 4.56.0

Header search: searching a client now brings back everything for that client.

Search a company name and you'll see the client, its people, and its records across every area you have enabled — projects, tickets, contracts, resources, invoices, assets and locations — all in one result list.

Matching is now forgiving of spacing and punctuation: "So Cal", "Socal" and "So Cal Edison" all find the same client.

As always, results respect access — you only ever see the records of clients you already have access to.

v4.55.2 — September 5, 2026

ClientCove 4.55.2

Fix: projects now show their friendly name in the header search.

The search was showing a project's internal "Project N" title instead of the name you gave it. Projects now display their friendly name first, followed by the "Project N" reference — e.g. "Brand Review — Project 1021".

v4.55.1 — September 5, 2026

ClientCove 4.55.1

Fix: search results no longer show a project's number twice.

A project with no separate name was displayed as "Project 1022 — Project 1022" in the header search. Projects now show their title once; a project that does have its own name shows the name first, followed by its "Project N" reference.

v4.55.0 — September 5, 2026

ClientCove 4.55.0

Header search: searching a client now shows its people too.

When you search a company name in the universal search, the people at that client now appear alongside the client itself — so one search gets you both the account and its contacts. Selecting a person opens their contact card.

Who you can find is unchanged and still respects access: you only see the contacts of clients you already have access to.

v4.54.0 — September 5, 2026

ClientCove 4.54.0

Find people in the header search.

The universal search (the search box in the header, or ⌘K / Ctrl-K) now returns people alongside tickets, projects, resources and everything else. Search a name — or type "who is Jane", "user Jane", "contact Jane" — and matching people appear at the top of the results.

Selecting a person opens a contact card with their photo, name, client, subscription (if any), email and phone. Staff also see when the person last logged in.

Who you can find respects your access:

• Staff (team, sales, and reps) can search everyone.
• Contractors can search people at their assigned clients.
• Clients can search people at their own client and your internal team.

v4.53.0 — September 5, 2026

ClientCove 4.53.0

Jerry (your AI assistant) can now offer one-tap "Open" buttons for two more areas when you ask how to do something:

• File Transfers — jump straight to sending or managing secure file transfers.
• Campaigns — open Email Campaigns to build or send a campaign.

These join the existing feature buttons (Contracts, Invoices, Tickets, Projects, Resources, Estimates, My Tasks, Intake Forms). As before, a button only appears when the feature is available to you.

v4.52.0 — September 5, 2026

Assistant offers a button to open the feature

When the AI assistant explains how to do something, it now shows a button to open that feature (e.g. "Open Contracts") right in the chat — but only for features that are turned on for you. Works in both the pop-up assistant and the dashboard assistant.

v4.51.0 — September 5, 2026

Delete archived tasks

The Archived tab in My Tasks now has a Delete button on each task, plus a "Delete All Archived" button. Deleting sends the task to Trash (where it can be restored for a couple of days before it's permanently removed), so you can finally clear out old archived tasks instead of only being able to restore them.

v4.50.3 — September 5, 2026

Expanded assistant is ready to type

When you expand the AI assistant on your dashboard, the message box is now focused automatically so you can start typing right away.

v4.50.2 — September 5, 2026

Fix: assistant now actually creates the user/client on Yes

When you asked the assistant to add a user or client and clicked "Yes, do it", the account was sometimes not created on installs using their own AI key. That's fixed — confirming now reliably completes the action.

v4.50.1 — September 5, 2026

Expand the assistant on your dashboard too

The AI assistant widget on your dashboard now has the same expand button as the floating one — click it to open a larger, centered window with more room to work, and click it again (or click outside) to return it to the dashboard.

v4.50.0 — September 5, 2026

Expandable assistant + friendlier setup prompts

The AI assistant now has an expand button that opens it as a larger, centered window so you have more room to work; click it again (or click outside) to shrink back. When it helps you add a user or client, it now asks one question at a time instead of a long list, and shows role names in plain language (Client Standard, Client Admin) rather than internal codes.

v4.49.1 — September 5, 2026

Insert-reference popup sits over the message

The "Insert reference" picker now opens centered over the message window you opened it from, instead of floating in the middle of the screen away from the form.

v4.49.0 — September 5, 2026

Add users & clients from the assistant

Admins can now add a user or a client right from the AI assistant. It offers to either walk you through the details in chat — asking one field at a time — or point you to the User Management page for the individual form or a CSV import.

Note: creating a user or client through the assistant is now limited to administrators (Administrator, System Admin, Tech Admin). Previously any staff role could create a client this way.

v4.48.1 — September 4, 2026

Drop files onto the editor too

Drag-and-drop attach now works when you drop a file directly onto the message text area itself, not just the surrounding form — dropped files attach instead of landing inside the message.

v4.48.0 — September 4, 2026

Drag files in to attach

You can now drag files straight onto the New Message window or a reply and drop them to attach — the form highlights as you drag over it. The attachment button still works too.

v4.47.0 — September 4, 2026

Insert references when replying

The reply box now has the same quick tools as the New Message window — insert image, icon, attachment, reference, and proof — as clean icon buttons. Staff can insert a reference right in a reply: it searches the people on the conversation and drops in a link to their resource, ticket, file transfer, and more. The Label dropdown text was also resized to match the Subject field.

v4.46.1 — September 4, 2026

Cleaner message Subject field

Fixes the "New Message" compose window so the Subject label no longer sits on top of its own placeholder text. The label now floats up neatly as you type, and the To/Subject labels size to fit.

v4.46.0 — September 4, 2026

A more consistent message composer

The compose windows now share one look wherever you write a message. The composer you open from a resource, asset, location, ticket, or contract gets the cleaner, wider layout with the same recipient field as the Messages page, and the Messages composer picks up the tidy floating subject field and compact icon toolbar. Same buttons, same behavior — just consistent and easier on the eyes from every direction.

v4.45.0 — September 4, 2026

Reference a file transfer in a message

Staff can now attach a file transfer to a message from the compose window's "Insert reference" picker. Search a recipient's transfers by name and insert one as a chip that links straight to its secure share page — the same upload/download link you'd send otherwise. Results stay scoped to the recipient's client, and the option appears only when File Transfers is enabled.

v4.44.1 — September 4, 2026

v4.44.1 — Reference picker polish

The Insert Reference picker now opens cleanly above the compose window without a dimmed background.

v4.44.0 — September 4, 2026

v4.44.0 — Attach references to a message

Staff can now attach references to a message from the compose window: click Reference, search a recipient's resources, tickets, invoices, estimates, contracts, assets, locations, and intake forms, and drop them in as tidy chips — as many as you need. References are scoped to the recipient's client. Also in this release: a tidier, wider compose form (the Priority field was removed and the Label field gained a tag icon).

v4.43.1 — September 4, 2026

v4.43.1 — Tidier new-message form

The compose form on the Messages page has a cleaner, tighter layout: the recipient and priority fields sit on one aligned row, subject and label on the next, so composing a message takes less vertical space and reads more clearly.

v4.43.0 — September 4, 2026

v4.43.0 — Support tickets: attach files from the dashboard

Clients can now attach files when they open a support ticket from the dashboard — drag them onto the card or pick them (up to 5 files, 10 MB each). Site owners can turn attachments off per widget. The Ticket Form widget's default heading is now "Open a support ticket".

v4.42.0 — September 4, 2026

v4.42.0 — Ticket Form widget: priority & type

The dashboard Ticket Form widget now lets clients set a Priority and Type when they open a ticket. Every ticket continues to record who submitted it, when, and which client it belongs to.

v4.41.1 — September 4, 2026

v4.41.1 — Dashboard Ticket/Intake widgets: card styling

The Ticket Form and Intake Form dashboard widgets now render inside the standard dashboard card, with a titled header and tidier layout, matching the other widgets.

v4.41.0 — September 4, 2026

v4.41.0 — Dashboard widgets: open a ticket, start an intake

Two new dashboard widgets. The Ticket Form widget lets a signed-in client open a support ticket right from their dashboard — subject, details, done. The Intake Form widget adds a button that sends clients straight to an intake form you choose. Add either from the dashboard builder.

v4.40.0 — September 4, 2026

v4.40.0 — Create invoice: next number preview + correct issue date

The create-invoice screen now shows the actual next invoice number in the live preview (labelled "next"), instead of a generic "Auto-generated". It also fixes an off-by-one on displayed dates: issue and due dates could show a day earlier than the date selected, depending on your time zone — they now match exactly.

v4.39.0 — September 3, 2026

v4.39.0 — Set your own invoice numbers

Settings → Invoices now lets you choose your invoice number prefix, the starting number, and whether to include the year. Numbers you've already issued are never changed — the settings only affect new invoices, and a starting number acts as a floor so you can pick up where a previous system left off.

v4.38.0 — September 3, 2026

v4.38.0 — Mark invoices paid in one click

Mark an invoice paid straight from the invoices list — one at a time or several at once. Pick the payment method and date once and it applies to every selected invoice. Recorded payment methods now display correctly everywhere (for example, ACH / Bank Transfer).

v4.37.0 — September 3, 2026

v4.37.0 — Manage your company profile from your account

A new "My Company" tab on your account page lets you complete and update your company details — name, description, address, and primary/billing contacts — right where you manage your account, with a progress meter that celebrates as you fill it in. No separate form to chase down. While your profile is incomplete, a reminder appears in your To-Do Center; it clears itself once you're done.

August 2026

v4.36.0 — August 24, 2026

v4.36.0 — To-Do Center: estimates to review

The client dashboard To-Do Center now shows estimates that are waiting on your decision. When you have an estimate that's been sent to you but not yet accepted or declined, it appears in the To-Do Center with a Review link that takes you straight to it.

This completes the To-Do Center: in one place, a client now sees everything that needs their attention — onboarding forms to finish, invoices to pay, contracts and agreements to sign, and estimates to review — with the most urgent items first.

v4.35.0 — August 24, 2026

Contracts and agreements now appear in the client To-Do Center.

Sign and accept from the dashboard

• A client's To-Do Center now lists contracts awaiting their signature ("Sign") and agreements they need to accept ("Accept"), each linking straight to the document.
• Only documents actually assigned to that client show, and already-signed or already-accepted ones drop off automatically.

v4.34.0 — August 24, 2026

Unpaid invoices now appear in the client To-Do Center.

Pay from the dashboard

• A client's To-Do Center now lists their unpaid invoices (sent, viewed, or overdue) with a one-click Pay link — no login needed to pay. Overdue invoices are shown first.
• Draft and paid invoices are never shown, and a client only ever sees their own.

v4.33.0 — August 24, 2026

The client dashboard widget is now a To-Do Center.

Everything a client needs to act on, in one place

• The client onboarding widget is now the To-Do Center — a single widget that surfaces what the signed-in client needs to do. It starts with their onboarding, with a link to complete each form.
• More action items — invoices to pay, contracts to sign, estimates to review — are being added to it in upcoming updates, so it becomes the client's one-stop action list.
• It only ever shows the client's own items.

v4.32.0 — August 24, 2026

A "My To-Dos" widget for your clients.

Clients see what they need to do

• A new "My To-Dos" dashboard widget shows a signed-in client their own outstanding onboarding, with a one-click link to complete each intake. When a new customer logs in, they see exactly what to finish to get their account set up.
• It only ever shows the viewer's own tasks. Add it from the dashboard builder to a client dashboard.
• The existing staff widget is now labeled "Client To-Dos (staff)" — the staff view of every client's onboarding.

v4.31.6 — August 24, 2026

Fix: new customers can now complete their onboarding intake.

• After landing in their onboarding form, a new customer can now load, fill, save, and submit it. Previously the form showed "Failed to load intake configuration."

v4.31.5 — August 24, 2026

Onboarding intake access + widget visibility fixes.

New customers can open their onboarding intake

• A buyer clicking the link to their onboarding intake now lands in the form to fill it out, instead of being bounced to the dashboard.

Client To-Dos is staff-only

• The Client To-Dos widget now only ever shows to staff. It will not render for a client, even if it's placed on a dashboard a client can see — so one client can never see another client's onboarding.

v4.31.4 — August 24, 2026

Fix: all staff can send an intake (Request input / intake sharing).

• Sending an intake to a client — from the Client To-Dos widget's "Request input" button or the intake manager — now works for every staff role, not only core administrators and editors. Staff on custom roles (system admin, tech admin, technician, etc.) previously got a "not allowed" error.

v4.31.3 — August 24, 2026

Fix: Client To-Dos "Request input" now works on the dashboard view.

• The "Request input" action on the Client To-Dos widget now works when viewing a saved dashboard (not just specific page templates). Send an intake to a client straight from the widget.

v4.31.2 — August 24, 2026

Fix: the Client To-Dos widget's "Request input" now sends reliably.

• The "Request input" button on the Client To-Dos widget now works on the live dashboard. Send an intake to a client straight from the widget.

v4.31.1 — August 24, 2026

Fix: the Client To-Dos widget now shows in the dashboard builder.

• The Client To-Dos widget introduced in 4.31.0 wasn't listed in the dashboard builder. It now appears and can be added to a dashboard like any other widget.

v4.31.0 — August 24, 2026

A new Client To-Dos dashboard widget.

See what each client needs next

• A new Client To-Dos widget for your staff dashboards lists customers whose onboarding isn't finished — the intake they still need to submit — with a one-click link to open it.
• Right from the widget you can send any of your intake forms to a client to request more input, without leaving the dashboard.
• Add it from the dashboard builder like any other widget, and set how many rows it shows.

v4.30.0 — August 24, 2026

Buyers become client users automatically.

A purchase now creates a real client

• When someone buys a plan or product, they're set up as a client user (Client Basic role) and given their own client record — so they land on the client dashboard and menus, not a bare subscriber view. It happens in one step; no switching roles afterward.
• If the buyer already has a client (an existing customer, or your staff buying something), their role and client are left exactly as they are.
• A new buyer's client is first named after them, then updated to their company name when they complete onboarding — no duplicate client records.

v4.29.4 — August 24, 2026

Orders now has a card in Admin Utilities.

Find and toggle Orders from the launcher

• The Admin Utilities grid now includes an Orders card, alongside Estimates, Invoices, and Product Manager. Open your customer orders — subscriptions and one-time purchases from your plans and products — directly from there.
• Like the other feature cards, it has an on/off switch, so you can enable or disable the Orders feature right from the launcher instead of digging through settings.

v4.29.3 — August 24, 2026

Customers can always view their own orders.

Receipts stay accessible

• A customer can now open an order they placed — their own receipt — even when the staff-facing Orders feature is turned off in settings. Before, the order page showed an "order management is currently disabled" message to the buyer.
• The Orders feature toggle still controls staff order management exactly as before; only a buyer viewing their own order is exempt.

v4.29.2 — August 23, 2026

Cleaner onboarding email for new customers.

One welcome, not two

• When someone buys a plan or product that has an onboarding form attached, they're guided through setting their password and into the form right on the page, and they get your onboarding email. The extra "Login Details" set-password email that used to also go out is no longer sent for these purchases — it was redundant and could confuse a brand-new customer.
• Purchases without an onboarding form are unchanged: the buyer still gets the "Login Details" email to set their password.

v4.29.1 — August 23, 2026

Password setup and reset now stay on your branded login page.

Branded password flow

• When a new customer sets their password — including a buyer who purchased publicly through guest checkout — the link in their welcome email now opens your styled ClientCove login page, not the plain WordPress screen.
• Password resets do the same: the "set a new password" link lands on your branded page instead of stock WordPress.
• The "forgot password" request page (enter your email to get a reset link) is now branded too, so the whole sign-in and password flow matches the rest of your portal.
• Nothing to set up — this applies automatically to every password email your portal sends.

v4.29.0 — August 23, 2026

Set up onboarding by asking — the assistant can now build intake forms and connect them to what you sell.

Create intake forms with the assistant

• A new assistant action builds a complete intake form for you: give it a title and the questions to ask, or start from one of the built-in templates for onboarding a client or capturing a resource, an asset, or a location. The form is created as a draft and opens in the form studio for you to review.
• Questions are described in plain terms — short text, paragraph, multiple choice, yes/no, image upload, file upload, and address — so you can lay out a form in a single request.
• New forms are only ever created as drafts. Nothing is sent to anyone and no form goes live until you review it and assign it yourself.

Connect a product to onboarding, hands-free

• The assistant can now attach an intake form to a product or plan and set its onboarding email, so a public purchase registers the buyer and starts their onboarding — the whole setup can be done in a conversation, end to end.
• Connecting an intake stays opt-in per item. A product with no onboarding intake behaves exactly as it did before, and you can disconnect one at any time.

Staff only

• Creating forms and connecting products are staff actions. Client and contractor logins cannot reach them, through the assistant or the connected tools.

v4.28.0 — August 23, 2026

Sell to the public and onboard the buyer automatically — a purchase can now register a new client and start a custom intake, all without you lifting a finger.

Post-purchase onboarding

• Connect any product or plan to an intake form: edit the item and set Onboarding Intake. When someone buys it, they are guided into that form to get their project started.
• A customizable email carries them there. A new Onboarding email template is added to the Email Designer, editable like any other, and each product can point at its own template if you want different wording per plan. Leave it and the default is used.
• The email's button opens the intake directly — the buyer completes it without hunting for anything.

New buyers register themselves

• When a brand-new customer buys publicly, the thank-you page walks them through finishing their account: they set a password and enter their company name, and that creates their client record automatically. No manual client setup on your side.
• Company name is all that's asked at this step — everything else about their project belongs in your intake, where it's yours to design.
• Buyers who close the tab get an email link back to the same finish-setup page. The link is single-use and personal to them.
• A returning customer who already has an account and company is recognized — no duplicate setup, and their purchase attaches to their existing client. They simply get the onboarding email and a Start onboarding button.

Staff can see onboarding at a glance

• An order shows its onboarding status — which intakes were sent and which are complete — both on the order page in your portal and on the order's admin screen.

Automation trigger

• A new automation event, An order is completed (purchase), is available in the Automations builder, so you can layer your own follow-ups — assign a task, notify an account manager — on top of any purchase.

A note on setup

• Public purchasing needs a checkout page: assign the Guest Checkout template to any page (Pages → the template dropdown). Without one, plan buttons send visitors to log in instead of buy.
• Connecting a product to an intake is opt-in per product. Products with no onboarding intake behave exactly as before — nothing changes until you wire one up.

v4.27.3 — August 23, 2026

A security fix for shared resource links. Update promptly.

Security: resource pages now validate their share link

• Resource pages did not check the share link before rendering, so a visitor who was not signed in could view a resource without a valid link. Assets and locations were not affected. With this update, resources validate the link's code, active status and expiry exactly as assets and locations always have, and an invalid link goes to the login page.
• This also means the Require a PIN to view setting now works on resource share links — previously the PIN gate never appeared on resources. Assets and locations were already gating correctly.
• No action needed beyond updating. Valid share links keep working unchanged.

The PIN gate asks only for the PIN

• The email field is gone from the PIN entry form — on share links, QR stickers, the embedded support form, everywhere. The PIN alone identifies its owner; the email was an extra step that added nothing for the visitor.

A note on older shares

• A share link created before PIN gating existed carries no PIN setting, and deliberately stays open so links already in your clients' hands keep working. To gate one, open that record's Share Settings and save — the setting turns on and says so before you save it.

v4.27.2 — August 22, 2026

A tidier message composer that follows your app's colors.

The floating composer

• The compose window now takes its colors from your Application Designer settings instead of staying white — the window itself, the message body, and the editor area all follow the app background and footer colors you designed. Portals that have never saved app-designer styles keep the white look they have today.
• Tighter padding around the editor, so more of the window is your message.

The linked-item badge

• When a message is linked to a resource, asset, project, location or contract, the reference used to sit in a full-width blue bar under the subject. It is now a compact pill inline with the insert and attach buttons, showing just the item's name — hover it for the type, and the X still unlinks exactly as before.
• Long names truncate with the full name in the tooltip, and on a narrow window the pill wraps to its own line rather than squeezing the buttons.

Under the hood

• The composer's script is now cache-busted on every theme update. Previously a browser could keep running the old script after an update until its cache expired — if you have ever updated and not seen a composer change until a hard refresh, this was why, and it is fixed for all eight pages that load the composer.

v4.27.1 — August 22, 2026

Icons for the login page's custom links, and a Login Designer layout fix.

Link icons

• Each custom link in the Login Designer can now carry an icon — arrows, chevrons, external link, house, person-plus, envelope, telephone, globe, credit card, cart, star — placed before or after the label. The natural pairings: an arrow ahead of "Back to our website", a person-plus after "Sign up here".
• Icons take the link's color automatically, including a color you picked in the designer, and preview live as you choose.
• The icon list is fixed on purpose: only icons from the picker ever render, and choosing none leaves the link exactly as it was in 4.27.0.

Login Designer fix

• The Top Link and Bottom Link controls in 4.27.0 rendered their fields crushed side by side behind a horizontal scrollbar. They now lay out properly — one field per row, with the icon, destination, and button-style rows appearing only when they apply.
• This was a display problem in the designer only. Links configured through the broken layout were saved and rendered correctly on the login page all along.

v4.27.0 — August 22, 2026

Two custom links on your login page — styled your way — and tighter bot protection.

Custom links in the Login Designer

• The Login Designer now has two link slots: a top link above the form heading (the "Back to our website" spot) and a bottom link under the form (the "Don't have an account? Sign up" spot).
• Label and destination are fully yours. The bottom link can point at the built-in registration page — it tracks your registration-page setting automatically — or at any custom URL, such as a paid signup or sales page.
• Each link renders as a text link or a button, with a color picker and, for buttons, a solid or outline style. On a solid button the text color flips black or white automatically so it stays readable on any fill. Leave the color empty and the link uses your theme's default look.
• Everything previews live in the designer as you type and pick.
• Nothing appears until a slot has both a label and a destination. Existing login pages are unchanged until you configure a link — there is no default content in either slot.

Bot protection on sign-in, scoped tighter

• Cloudflare Turnstile has protected the login, registration and forgot-password forms since it was introduced in Settings → Authentication, invisible on login until repeated failures make it show a visible challenge. This release scopes it tighter: a verification token minted on one form no longer passes on another — registration tokens cannot be replayed against login.
• Hostname checking is available for the strict-minded: verification can require the token to have been solved on your own domain. It is off by default and log-only, because on proxied or aliased installs a wrong hostname guess would lock everyone out; enable it with the cove_turnstile_enforce_hostname filter once you have confirmed your setup.
• Nothing changes on upgrade. If Turnstile is off, it stays off. If it is on, the only new behavior is the cross-form token rejection — and tokens from pages loaded before the upgrade are tolerated during the transition, so nobody mid-session is locked out.
• A reminder for local development: a Turnstile sitekey only works on the domains you allowed in Cloudflare. If your login page's browser console shows error 110200, add that domain — or localhost — to the widget in your Cloudflare dashboard.

v4.26.0 — August 22, 2026

Invoices your clients can pay in one click — no portal login, no friction.

Payment links

• Every invoice now has a payment link: copy it from the invoice list (the link icon) or let the invoice email carry it. Anyone with the link sees that one invoice — read only, with the payment form ready — and can pay by card without an account or a sign-in.
• The emailed Pay Now button uses this link and opens the payment form on arrival. One click from inbox to card form.
• The link grants exactly one invoice's page and its payment, nothing else: not your invoice list, not other invoices, not the PDF download. A visitor who wants the PDF copy sees "Log in to download a copy" instead of a button that dead-ends at the login page.
• The link is minted once and stays stable, so re-copying it never breaks the copy already sitting in a client's inbox. Payments made through it are verified with your payment processor before the invoice changes state, and the amount always comes from the invoice itself.
• A payment link is not a password. Anyone who has it can view and pay that invoice, exactly like a resource share link — treat it accordingly.

Sending asks instead of failing

• Sending an invoice for a client with no billing email on file now asks you for one on the spot, with a checkbox to save it to the client so you are asked once, not every time. The address is saved only after the email actually sends.
• Invoice emails now go to the client's designated billing contact first, then the client's email, then an assigned user — previously the billing contact field was never consulted.

The attached PDF is always current

• The invoice email now renders its PDF fresh at every send, so the attachment always carries the current design and the current numbers. Previously it attached the last stored file, however old — an edited invoice could go out with an outdated PDF.
• Invoices with an uploaded PDF are untouched: your uploaded file attaches exactly as-is.

Offline payment

• New in Settings → Invoices: Offline Payment Instructions — bank transfer details, where to mail a check, a phone number. Set it and it appears in invoice emails under "Other ways to pay" (together with the invoice's own payment terms) and beside the card form on the payment page.
• Leave it empty and nothing changes: card payment stays the only offer.

Refreshed invoice emails

• The built-in New Invoice, Payment Received and Overdue Reminder templates got the polished look: branded banner header, your logo above the content, a Pay Now button that needs no login, and the payment-instructions section.
• Templates you have edited in the Email Designer are not touched. Only the stock templates, unmodified since install, are refreshed — anything you customized stays exactly as you left it, and the new payment-instructions variable is available in the designer if you want to add it yourself.

v4.25.0 — August 18, 2026

Download a whole selection as one zip, and tell the resource types apart at a glance.

Download as zip

• Select resources on the index and the action bar now offers Download as zip alongside Move, Tag and Delete.
• You get one archive with a folder per resource, named after it. Files that share a name across different resources stay apart, and it is obvious which came from where.
• Files, bundles and galleries contribute their files. Web previews, design imports and ad groups contribute the original zip they were built from.
• It respects "Offer the original zip for download". A design with that switch turned off is left out of the zip, exactly as it is left out of its own page. Selecting it is not a way around the switch.
• Some resources have nothing to download — articles, FAQs, color sets, diagrams, videos and apps have no file set. Those are named back to you, with the reason, before the download starts. Select only those and it says so rather than building an empty archive.
• It only ever includes what you can already see. Up to 100 resources at a time.

Every resource type has its own color

• Web previews, design imports, ad groups, diagrams, files, bundles, galleries, videos, color sets, articles and FAQs each carry a color on the resources index. The top of the card is washed in it and the icon confirms it, so three web previews read as a set from across a grid.
• Image cards keep their thumbnail, inset slightly so the color still frames it.
• The colors are yours to change. In the Add Resource modal, each type now has a small swatch — click it to pick a different color for every resource of that type, shift-click to put it back. Only administrators can change them, and a change applies to everyone on the site.
• The palette sits outside your brand colors on purpose, so a white-labeled portal keeps its own look and these stay readable against it.
• Two fixes in the same area: web previews had no icon at all on the index, and color sets were the one type whose card never picked up its tint.

Share Settings only asks what applies

• Require a PIN to view and Link Expiration now appear once Activate Public Link is on. Both describe how a public link behaves, so neither means anything before there is one. Off, the panel is a single switch.
• Nothing changes for links that already exist, and nothing changes about how they work — this is only what the panel shows you.
• Labels and the expiry options are smaller, so the whole form fits on screen without scrolling.

The embed form's third step is optional

• Tie it to one asset or location is marked Optional and folded away. Steps 1 and 2 give you a working support form; open step 3 only when you want a QR sticker link or a snippet bound to one specific record.
• Everything inside it is unchanged, and any embed already on a customer's site keeps working exactly as before.

v4.24.2 — August 18, 2026

A single new control: whether a design's original zip is offered for download.

Offer the original zip for download

• Web previews, design imports and ad groups all keep the zip they were built from, and all three have always offered it to viewers as a download. Edit mode now has a switch per resource: Offer the original zip for download.
• Turned off, the download buttons disappear from the preview. Viewers can still look at the design, page through its screens and resize it — they are just not handed the source.
• It does not make the file private. The zip is stored at a public address, so anyone who already has that link — from an earlier visit, a copied URL, browser history — can still fetch it. The note under the switch says so. Treat it as "don't offer this", not as "this is now secret".
• Nothing changes on upgrade. Downloads stay on for every existing resource, and stay on until someone turns one off.

v4.24.1 — August 17, 2026

A repair release for Web Preview, plus one thing it was missing.

The Web Preview edit panel now works

• Its Default viewport and Entry screen dropdowns did not save. Replace Design Zip did nothing when clicked or dropped on. The clear button, the retry button and the status refresh were equally inert.
• One cause behind all of it: the panel's JavaScript sat inside a region of the edit page that gets rebuilt as it loads, which removed the script before it ever ran. The markup was fine, which is why the panel looked complete and did nothing.
• If you have been re-uploading a zip to change which screen opens first, you no longer need to.

Delete a screen from a Web Preview

• Multi-screen previews now list their screens in edit mode, each with a delete button. Deleting one removes its HTML file and drops it from the preview.
• Shared images, CSS and scripts are left alone, because the remaining screens are still using them.
• Deleting the screen that opens first moves that to whichever screen is now first, and tells you which. The last remaining screen cannot be deleted — a preview with no screens is not a preview, so use Clear to remove the whole thing.

A Web Preview's description now appears

• Anything typed into the description field on a web preview or design import rendered nowhere at all. It now shows below the preview, formatted the same way descriptions are on every other resource type.

Access PIN screens explain themselves

• The PIN screen now says why it asks for an email: it identifies which account's PIN to check. Without it a six-digit code is shared across everyone who holds one, so the email is what keeps a PIN worth something.
• Added "Don't know your PIN? Find it in your account under Security", which opens in a new tab so nobody loses the form they were part-way through.

Nothing in this release changes a setting or turns anything on. If you are not using Web Preview resources, there is nothing here that affects you.

v4.24.0 — August 12, 2026

A release about the people who are not sitting at the portal: the technician standing in front of a broken machine, the client contact on someone else's website, the person you sent a share link to. Each of them can now be recognised — and each can report a problem against the exact thing they are looking at.

Access PINs

• Every user can hold a six-digit access PIN, from Account → Security → Access PIN. Administrators can set one on a user's behalf.
• A PIN is not a second password and does not sign anyone in. It answers "who is this?" in front of a single form, so the portal can record who did something and file it as them. That is all it does.
• Each entry opens exactly one thing. A session for one asset cannot be reused on another asset, or on a support form, or anywhere else.
• Sessions are short-lived, every entry is rate limited, and changing a PIN immediately invalidates everything it had open.

A support form you can embed on your own site

• Tickets → Embed form gives you a snippet to paste into a customer's website. Someone there enters their PIN and files a ticket straight into your portal.
• The form is served from your portal inside a frame rather than built into their page, so nothing else running on that site can read what is typed into it.
• You choose who may embed it. One origin per line on that same screen. Until you add a site, nobody can embed the form anywhere — the safe default, and deliberately not "allow everyone".
• The snippet can be tied to a single asset or location, so requests arrive already attached to the equipment they are about.

QR access for assets and locations

• Each asset and location has a scan link you can print on a sticker, from the same Embed form screen. Scan it, enter your PIN, and you see that record plus a way to report a fault against it — no login, no app.
• The code on the sticker carries only which record it is. It holds no key and no PIN, because a sticker on a wall is readable by anyone in the room and often ends up in photographs. A scanned code on its own is worth nothing.
• People see only what their account already allows. A PIN belonging to one client cannot open another client's asset, whatever is in the link.

"Require a PIN to view" on share links

• Share Settings on Resources, Assets and Locations gains a Require a PIN to view switch. With it on, the link alone is not enough — the visitor identifies themselves first, and you know who looked.
• It is still a public view of that one record. The PIN does not sign anyone in and opens nothing else.
• New shares get it on by default. Links you have already sent are not touched. Turning it on retroactively would have broken every live link from the recipient's side with no warning, so an existing share keeps working exactly as before until someone opens its settings.

A support form on asset and location pages

• Assets and locations can carry a "Report a problem" form on their own page, filing a ticket already attached to that record.
• Off by default. Switch it on per record under Edit → Settings → Show the support form on this asset/location, which appears once asset or location tickets are enabled in Core Features. Nothing changes on upgrade: no existing record starts accepting reports until you ask it to.
• On a public share view the form takes the place of the Tickets tab, labeled Support Form — a list of the record's ticket history was never what an outside visitor came for. Signed-in viewers keep the Tickets tab.
• Signed-in staff and clients file directly. Someone on a share link is asked for their PIN first, unless the share was already PIN-gated, in which case they are recognised from that and not asked twice.
• There is no anonymous route. Someone the portal cannot identify cannot open a ticket. The ticket belongs to the record's client, not to whoever noticed the problem, so a fault on a client's equipment lands in the right place even when your own team reports it.

Seeing who has been looking

• Assets and locations gain a Viewed From Outside panel above their activity log: everyone who opened the record without signing in, by code or through a PIN-gated share link, with who, when and where from. The record keeps its most recent fifty.
• Visible to anyone who can edit the record, so a client administrator sees it for their own equipment and nobody else's. It does not widen when a record is shared — sending someone a link never shows them who else has opened it.

Field notes from a shared page

• Someone who unlocked a shared asset or location with their PIN can now add an entry to its activity log, if their own account was already allowed to. The PIN identified them at the gate; that identity used to be discarded the moment the page rendered.
• Nothing widens. Whatever an account could do signed in it can do here, and whatever it could not it still cannot. Entries are attributed to the person behind the PIN, never to "unknown".

Fixes

• The embedded support form now explains itself when it cannot load. Pasting the snippet into a site that has not been added to the allowed list produced an empty space and nothing else — the browser refuses the frame before any portal code runs inside it, so there was nothing left to report the problem. It now replaces itself with a note naming the exact origin to add.
• The share settings dialog was being written into asset and location pages twice, which also re-ran QR code generation on every page load.

v4.22.0 — August 11, 2026

Last login times are now correct and consistent everywhere.

The fix

• Sign-in times could be recorded in either the site's local time or UTC depending on which piece of code happened to run last, so the same login could be stored — and shown — hours out. Sign-ins are now recorded one way, every time.
• Last login now displays in your portal's own timezone on every screen that shows it: the user management tables, client screens, the crew dashboard activity feed, and the account and profile pages.
• Existing records are corrected automatically as they are read. Nothing needs re-entering, and no times are lost.

If a login has ever looked like it happened at the wrong hour, or two screens disagreed about when someone last signed in, that is what this fixes.

v4.21.0 — August 11, 2026

Ask the assistant who has and has not been signing in.

What is new

• Ask the AI assistant questions like "who logged in most recently?", "which client users have never signed in?" or "who has not been back in 30 days?" and get an answer from the portal's own records instead of scrolling User Management.
• Narrow the answer by role, by client, or by a name or email search, and set your own time window.
• Available to administrators, system admins and tech admins only. Everyone else cannot ask it, so no one can find out when a colleague — or someone at another client — last signed in.
• Also available to Claude and other connected AI tools through the MCP connection, with the same restriction.

Worth knowing

• These are sign-ins, not activity. The portal records when someone logs in, not what they do afterwards, so a person who signed in a few weeks ago and has been using the portal daily since will still show that earlier sign-in. The assistant says so when it answers.

v4.20.0 — August 10, 2026

Turn core features on and off straight from Admin Utilities.

Admin Utilities used to be a read-only launcher: a card for a switched-off feature was grayed out, and turning it back on meant a trip to Settings, finding the right tab, flicking a switch and saving. The switch is now on the card itself.

What is new

• Every feature card carries an On/Off switch. Flip it and it saves immediately — no Save button, no page reload.
• Switching a feature off grays its card out on the spot; switching it on brings it straight back.
• Clicking anywhere else on a card still opens that feature, exactly as before.
• Admin Utilities and Settings stay in step. A change made in either place shows up in the other.

Only administrators see the switches. System Admins and Tech Admins still get the launcher, but changing core features stays where it always was — with full administrators.

Cards for features that depend on more than one setting keep working as before and have no switch: Crew Dashboard follows Tasks, Tickets and Projects together, and Cloud Files depends on which storage provider is configured.

v4.19.0 — August 10, 2026

Redesigned invoice and estimate PDFs.

The PDF your client downloads has been rebuilt from scratch. It now matches the look of the portal instead of trailing years behind it: a clear headline amount, a status chip, a clean hairline line-item table, and a totals card that puts the emphasis where it belongs.

What is new:

• Invoices and estimates now share one design, so a client who receives both sees a consistent set of documents.
• Line-item details can now be a bulleted list. Start a line in the Details field with a dash and it renders as a bullet; existing single-line details are unchanged.
• The status is always shown on the document, so an overdue invoice reads as overdue at a glance.
• The document picks up your brand color for the total, and automatically darkens it if it would be too light to read on paper.
• Payment details, terms and notes are still included, restyled to sit quietly alongside the totals rather than competing with them.
• Bulk invoice downloads now produce exactly the same document as a single download; previously they used a different page size.
• Every page prints on US Letter, and long invoices repeat the table header and never split a line item across a page break.

Existing PDFs are regenerated automatically the next time they are downloaded, so nothing needs to be re-issued by hand.

v4.18.0 — August 10, 2026

A maintenance release. There are no changes to the portal itself — this version only improves the internal tooling that builds and publishes updates, making failed publishes report their cause instead of failing quietly.

No action is needed beyond applying the update.

v4.17.0 — August 10, 2026

Invoice imports handle real-world exports from other billing systems, and client matching is smarter about company names. This release also carries the unreleased 4.15.1 and 4.16 work.

Import invoices without editing the file

• A FreshBooks "Invoices Export" now imports as-is. Previously the importer only accepted its own column names and rejected the file outright.
• Column names from FreshBooks, QuickBooks and the portal's own format are all recognised, so exports drop straight in.
• Line descriptions and their longer detail text are both preserved rather than one being dropped.
• Per-line tax and per-line percentage discounts from the source file are converted into the invoice's tax rate and discount amount, reproducing the original totals.
• A missing rate is worked out from the line total, so partial exports still import.

Client matching

• Client names now match across legal-suffix variants, so "Acme Inc", "Acme, Inc." and "Acme Incorporated" resolve to the same client on import instead of creating duplicates.

v4.15.0 — August 9, 2026

Leads captured in LeadCove CRM can now become clients in the portal, and dashboards get a layout control. This release also carries the unreleased 4.14 work.

Converted leads arrive from LeadCove CRM

• When a lead is marked converted in LeadCove CRM, it can be handed straight to the portal as a client record — no re-typing, and no export-import round trip.

Dashboards

• A per-dashboard option to hide the title heading, for dashboards where the heading only repeats what the page already says.

July 2026

v4.13.0 — July 27, 2026

A polish-and-hardening release: the product system is easier to find and set up, Resources search reaches further, and a cross-client visibility bug in Resources is fixed.

Product Sales Tools

• The "Marketplace" feature is now called Product Sales Tools — the same system, named for what it does: a catalog of plans and products, reusable groups, block-based landing pages, and guest or signed-in checkout.
• The Product Manager hub and the checkout page now create themselves automatically when the feature is switched on, so upgraded installs never land on a missing page.

Resources search that reaches further

• Inside a folder, an active search or filter now shows a scope toggle: search just this folder, or everywhere across all folders.
• Searching everywhere from inside a folder keeps a read-only "also in this folder" strip in view, so you never lose your place. One click returns to browsing.

Fixes

• Resources visibility (important). A client viewing all resources with a type or tag filter applied could, in some cases, see resources belonging to other clients. Client visibility is now enforced independently of any filter, so a filter can only ever narrow what a client sees. Folder views were never affected.
• The Invoices index page now stays selected after you save Core Features.
• Admin Utilities gained an instant filter box once there are enough cards to warrant it.

v4.12.0 — July 24, 2026

The product system grows up: sell to the public, build landing pages the way you build dashboards, and manage it all from one hub. This release also carries the unreleased 4.10 and 4.11 work — read it as one upgrade.

Product landing pages — a new page builder

• A new Product Page type built from blocks: hero, rich text, plans, products, groups, comparison table, testimonials and dividers, arranged in a full-screen drag-and-drop studio — the same building experience as dashboards.
• Every block declares its audience: everyone, public only, members, or specific clients and client segments. One page can serve logged-out visitors, logged-in clients and individually targeted clients, with per-client pricing and exclusions so an item never appears twice with conflicting offers.
• Preview exactly what each audience sees — a public visitor, any member, or one specific client.
• Per-block appearance controls for background, padding and alignment. Public visitors get a clean standalone page; logged-in users see it inside the portal.
• Default Plans, Products and Marketplace pages are created for you, and your existing URLs keep working. Existing layouts and product groups migrate automatically — nothing is deleted.

Product Manager — one hub for everything you sell

• One place for the catalog (plans and products with search, filters and stat cards), reusable groups you can drop onto pages and dashboards, and your landing pages with 7-day view and buy counts.
• Create plans, products, groups and pages from a single New button, and start from a ready-made preset: a pricing page, a services overview, or a client offer.
• The old separate product manager and subscription layout builder are retired. Every path now lands on the hub.

Sell to the public

• Flag any item public and it appears on your public catalog and landing pages, browsable and buyable by visitors without an account.
• Guest checkout creates the customer's account on purchase: they pay, receive a set-password email only after payment succeeds, and land in the portal as a client.
• Client-assigned items can never leak publicly. Visibility fails closed at every layer, and only staff can flip the public flag.

Also in this release

• Schedule a landing page to go live: give a draft a date and time and it publishes itself, even if nobody is looking.
• Place any product group on any dashboard as a widget.
• Lightweight page analytics — views by audience and buy-button clicks.
• Client segments: group clients once, then target or exclude whole segments anywhere audiences appear.
• Fixed: deleting an item failed silently for everyone, including administrators.

v4.9.0 — July 9, 2026

File transfer notifications now actually send, and every outbound email the portal attempts is recorded in a log you can search.

File transfer emails: fixed at the root

• Creating a transfer never triggered a notification email — the docs promised it, but only a manual button existed. Inbound file requests now email the recipient the moment the request is created, and outbound transfers email once every file in the batch has finished uploading. Never on a partial batch, so nobody receives a link to an incomplete transfer.
• "Notification email sent" used to appear even when nothing was sent, because the send result was never checked. The resend button and the creation toasts now report the truth: success names the recipient, and failure says so and points you at your mail settings.
• Failed sends are recorded in the transfer's history alongside the successful ones.

New: the Outbound Email Log

• Every email the portal sends is logged: recipient, subject, type, the related record, which service actually carried it, and the outcome — sent, or failed with the exact error. Message bodies are never stored.
• Ask the AI assistant "did the transfer email to jane@example.com go out yesterday?" and it answers from the real send record, filterable by recipient, subject, status, type and date.
• Entries are cleared automatically after 180 days, and an administrator can purge the log at any time.

v4.8.1 — July 7, 2026

AI Polish: resilient and polite

• Polish now retries on the standard model tier when the fast tier is unavailable — fixing plans where Polish failed while other AI features worked — and failures show a friendly toast ("Your draft is untouched — please try again in a moment") instead of a browser error dialog. Upstream failures are now always logged with the provider's actual error.

Tickets index: laptop fix

• Removed the redundant Category column (already shown in the Subject cell), gave Subject a guaranteed minimum width, and kept compact columns on one line — narrow screens scroll instead of squishing.

v4.8.0 — July 7, 2026

Crew Dashboard: task assignment

• Create tasks for any crew member or client user from the roster — one person or several at once. Assignees get a designed email + bell notification; managers complete/edit inline; delegated tasks show an "assigned by" chip.
• New Your To-Dos dashboard widget: open tasks, due-date sorted, one-click complete — perfect for client dashboards.
• The AI assistant and MCP can assign too ("add X to Dena's tasks"), gated to crew managers.
• Crew surfaces show first/last names instead of email display-names.

Tasks: related items, client-scoped

• Tasks can reference tickets, projects, invoices, estimates, assets, locations, intakes, and marketplace items — clickable links with identifying numbers, a picker in the Add Task modal, and server-enforced client scoping (a client's item only relates to that client's tasks; clientless tasks adopt the item's client).

Connect Claude from your account page

• A new Claude tab on the Account page lets non-admins connect Claude to the portal (per-user OAuth — Claude acts as them, with their permissions). Admins choose who sees it: admins only, staff, or everyone.

Resource fixes

• New resources without a folder no longer land in Trash; update_resource can create folders (including a client's scoped library); MCP confirmation flow fixed for add_user/write_notes.

v4.7.0 — July 7, 2026

Day-of-week automations

• Weekly schedules accept multiple days ("every Mon/Wed/Fri at 9:00"), and a new on_day_of_week condition lets event automations act only on chosen weekdays ("if a ticket opens on a weekend, escalate"). The AI assistant and MCP understand both from plain language.

MCP: full tool coverage (97 tools)

• The MCP bridge now exposes the portal's entire tool registry — campaigns, email templates, estimates, invoices, payments, assets, locations, reports, queries, subscriptions, and more — with the same permission scoping, act-as guards, and confirmation flows as the native assistant.

Fixes

• Edit-project modal shows a live Active / On Hold chip, and projects with a never-set active flag no longer read as deactivated (saving untouched used to silently put them On Hold).

v4.6.0 — July 6, 2026

AI can act as another user

• Every AI/MCP tool accepts an optional _act_as user ID — replies, board cards, and notes are authored under that user's name and avatar. Guarded by the same rules as View as User (capability + strict role hierarchy), enforced for the tool too (acting as a client can't unlock staff tools), and fully audited with both identities.

Kanban boards, end to end

• New create_board_list tool adds columns to a project board, and update_board_task can now move cards between columns — an assistant can build a board and walk cards through it.

Resources: edit and delete

• New update_resource (title, description, type, URL, publish/draft, move between folders) and delete_resource (trash by default; admins may force-delete). Same client-ownership rules as reads.

Project scope, writable

• New get_project_scope / set_project_scope tools manage the objective, in-scope/out-of-scope lists, deliverables, and constraints. Updates are partial — untouched fields survive.

Assets: records and files

• New create_asset / update_asset tools mirror the portal's asset editor, and image_url / file_url fetch a remote file server-side and attach it to the asset — no upload step needed.

Quiet user provisioning

• add_user gains send_invite: false (create the account without the invitation email), plus first/last name, username, and a role option capped strictly below your own level. Also fixed: MCP email invites previously always failed with "missing fields."

v4.5.0 — July 6, 2026

Email deliverability, fixed at the root

• Ticket emails carried two Message-ID headers — Gmail rejected them as RFC-invalid and the provider then silently suppressed the recipients, killing all later email to them. One Message-ID now ships per message (threading intact), and suppressions were cleared.
• New Deliverability Check in Settings → Outbound Email: see whether an address is on the provider's suppression lists (bounces, blocks, spam reports) and clear it with one click. The page also shows which email transport is active.

Resources: search by file type

• Searching tiff, PDF, or jpg (aliases included) finds files of that type — even inside folder resources — not just title matches.

Knowledge Base: System tab browses the catalog

• The System source tab (renamed from the raw docs hostname) now shows all official documentation grouped by topic instead of a blank page, with a friendly fallback when the docs site is unreachable.

Notifications: real management tools

• Delete individual notifications, Clear read, or Clear all — plus settings shortcuts on both the notifications page and the bell dropdown that deep-link to your notification preferences.

Dashboard

• Marketplace Items cards no longer clip their action buttons in narrow layouts.

v4.4.0 — July 6, 2026

AI: resource collections (folders)

• New list_resource_collections tool — the assistant can list and search your resource folders (staff see all; client users only folders holding their resources), and list_resources accepts a folder filter with sub-folders included. "What's in the Proposals folder?" now just works, in chat and over MCP.

Ticket update emails: delivery fixed

• The batching rate limiter allowed one ticket email per 15 minutes total — one email muted every other ticket. Batching is now per-ticket and only counts emails that actually sent.
• Batched and quiet-hours notifications were queued for a daily summary that never existed — a real daily 5 PM digest now delivers them.
• Status changes from the ticket page sidebar now send templated notifications (previously they emailed no one).

Client access: keyless-client 404s self-heal

• Clients created via MCP, AI, REST, or import never got a tenant key, so their users hit 404 on every single ticket, resource, and project. Keys now generate themselves — at creation, on upgrade, and on-demand on first page view — and content stays reachable through its client relationship even without a key.

v4.3.1 — July 5, 2026

• Knowledge Base images fixed. Documentation images from docs.clientcove.io now render correctly in the in-portal KB reader (previously showed as broken images).

v4.3.0 — July 5, 2026

Email Designer: estimates + layout controls

• Estimate emails are now designable. Estimate sent, accepted, and changes-requested notifications render through Email Designer templates, with a new Estimates category, default templates, and estimate variables.
• Left-justified layout. A new Layout setting lets a template sit directly on the recipient's own mail-client background — logo, text, buttons, and footer left-aligned — instead of the classic centered colored page.
• Cleaner defaults. The colored top bar on headers is off by default (toggle it back for the gradient banner), a new toggle removes the container border & shadow, and the corner-style control hides when the border is removed.
• The preview tells the truth. Builder preview, preview window, and the sent email now render identically — logo, button styles, and layout settings included.

Tickets: status, visibility, and email fixes

• "Open" now means open. Status filters (AI tools included) treat New and Reopened as open, and 18 tickets stored with a corrupted status format — invisible to every filter — were healed, with the root cause fixed.
• No more 404 on your own ticket. Tickets created from the portal form, AI, MCP, or intake were invisible to their creators because client-scope keys only synced on wp-admin saves. Keys now sync on every creation path (projects and locations too), with a one-time backfill.
• New-ticket confirmations use your template. The "support request received" email now renders through the Email Designer instead of raw HTML, and ticket admins no longer get a duplicate untemplated copy.
• AI ticket replies appear instantly on open ticket pages and are logged in the ticket history timeline.

v4.2.0 — July 5, 2026

AI everywhere: campaigns, assets, locations (12 new tools — 85 total)

• Email campaigns by AI. Draft, update, and inspect campaigns (with open/click stats), preview exactly who a campaign reaches (opt-outs included) without sending, and — admin-only — send or schedule with a confirmation that states the real recipient count.
• Smarter template authoring. The AI reads the full {{variable}} reference instead of guessing, can author marketing templates for campaigns, and can restructure templates — adding, removing, and reordering blocks.
• Assets & locations. List, inspect, and search both — scoped to each user's clients — and link them to tickets by name.
• Every new tool lands simultaneously in the native assistant, the MCP server, and automation action steps.

Chat history

• The dashboard AI widget saves every conversation. A new history panel lists your last 30 sessions — reopen any of them and continue with full context, or delete them. "Clear" became "New conversation" and keeps the old session.

AI reliability

• Bulk ticket replies with a single confirmation ("respond to all open tickets" previously staged nine confirmations and completed none).
• Estimates & invoices created by AI now total correctly (previously $0 until manually edited), default their dates, and come back with a clean link.
• Yes/Cancel confirmation buttons now render on all AI provider types, and honesty guards prevent the assistant from claiming actions it never performed.
• Fixed a bug where any conversation involving a no-argument tool call failed on every following turn.

v4.1.0 — July 5, 2026

Ticket email notifications, rebuilt

• Your templates, everywhere. Ticket emails (new ticket, new reply, status change, assignment) now render through the Email Designer transactional templates. The right audience gets them — owner, assignee, ticket admins, subscribers — never the person who made the update, and internal techs-only notes are never emailed to clients. Per-user notification preferences, quiet hours, and rate limits are respected.
• Reply to the email, update the ticket. With inbound email enabled, notifications carry a Reply-To onto your inbound address and real threading headers — clients answer from their mail app and the reply lands on the ticket conversation. Subjects carry the [Ticket #N] key so replies thread reliably.
• New-ticket emails notify the staff side from every creation path (portal, intake, email, MCP, AI), with a new New Ticket Created template type in the Email Designer.
• AI replies join the thread. Ticket replies made through the AI assistant now appear in the portal conversation like any typed reply, support techs-only internal notes, and trigger the same notifications.

Client access fixes

• Fixed client users hitting 404 on single resource pages — including resources assigned to their own client and ones they created. Client keys now self-heal, with a one-time automatic backfill.
• Clients can only delete their own resources — deleting a teammate's resource shows a clear message naming who added it.
• Fixed the magic-link rate limiter locking users out with "Try again in 0 minutes."

v4.0.0 — July 5, 2026

Folder-tree uploads

• Drop a folder, keep its structure. Dragging a folder onto Resources now asks: Recreate folders, Flatten, or Cancel. Recreate builds matching portal folders — nested subfolders included, up to 4 levels — and uploads each file into its folder. Same-named existing folders are reused, client folders pass their client scoping down to new subfolders, and the option appears only for users who can create folders.
• No more broken image previews. TIFF, HEIC, Photoshop, Illustrator, and camera-raw files show their type icon instead of a broken image on cards, list rows, and in Quick View — and any preview that fails to load (expired link, missing file) falls back to the icon too.

v3.9.0 — July 5, 2026

Resources, redesigned

• New resource cards. Every resource type gets a consistent card: a preview area (thumbnail, file-type icon, video play button, color swatches, or gallery tiles), an always-visible type chip, hover quick-actions, colored tag dots (hover for the name), and a meta row with file count, size chip, date, and the client-access indicator. The list view becomes a proper table with sortable-feeling columns and horizontal scroll on narrow screens.
• Quick View is now a drawer. Click the eye and a panel slides in from the right — the library stays visible behind it. Browse with the ‹ › buttons or your ← → arrow keys through the current folder/filter ("4 of 30"), press Esc to close. Videos play inline, color palettes show a swatch wall, files get secure download rows with Download All, and articles/FAQs open with the first few sentences of the document.
• Drop folders to upload. Drag a folder from Finder or File Explorer onto the Resources page and every file inside — including nested subfolders — uploads into the current folder (structure is flattened; OS junk files are skipped). Empty or unreadable drops now explain themselves instead of failing silently.
• Light and dark mode are both first-class throughout, mapped to your install's palette.

v3.8.0 — July 5, 2026

Application Design

• Logos that follow the theme. Upload a dark logo/icon and the portal swaps it in automatically when the mode changes — in the App Designer preview and across the live portal.
• Live layout preview. Switching Standard Block ↔ Cove Dock in the designer now repositions the logo immediately, before saving.
• Dark mode readability (Beta). Headings, cards, panels, and status chips across the portal now adapt properly in dark mode. Both Modes and Dark Only are labeled Beta in Theme Mode Options; Light Only remains the default.
• Unified the header search and theme-toggle icon sizing/colors, and fixed a state bug that could hide the logo under a forced light/dark policy.

v3.7.0 — July 4, 2026

Admin Utilities

• One home for the admin toolkit. A new Admin Utilities page shows a launcher grid of 22 core-feature cards — each with a one-line description, grayed out when its feature is disabled in Core Features, hidden when your role can't access it. See Admin Utilities.
• A tidy account menu. The long admin link list in the account dropdown is replaced by a single Admin Utilities link (just above System Settings), and Knowledge Base — under whatever display name you've given it — moves up with your everyday items, below Transfers.

v3.6.0 – v3.6.2 — July 4, 2026

Knowledge Base, redesigned

• Navigation that stays with you. The topics rail and search toolbar now persist while reading an article — search from anywhere, jump topics without going back, and see the article's topic highlighted. Every KB view shares a consistent header, and you can rename the Knowledge Base (say, "Help Center") under Settings → Core Features — every heading and breadcrumb follows.
• Rich article editing. The article body is now a real rich-text editor with Visual and Code (HTML) tabs, in a cleaner two-column edit screen. The AI Draft with AI helper fills the editor directly.
• Article image & video. Give any article a main image (uploaded straight to cloud storage — no media library detour) and a video (YouTube, Vimeo, or a direct file). Media sits beside the article on wide screens and above it on smaller ones, with minimal player chrome.

Official ClientCove docs, inside your portal

• With the Official Product Docs source enabled, articles from docs.clientcove.io open inside your Knowledge Base — your branding, no external bounce — and links between docs articles stay in-portal.
• The AI assistant cites in-portal articles when it answers "how do I…" questions from the official docs. Which roles get docs-grounded answers is controlled by the new Product Docs column in AI data access.

AI assistant polish

• Replies now render clean paragraphs, bullet lists, and numbered steps reliably in both the floating chat and the dashboard widget.
• Actions that change data ask for confirmation exactly once, with tap-to-confirm Yes / Cancel buttons in both widgets.

v3.5.0 – v3.5.9 — July 3, 2026

Automation recipes

• Start from a recipe. A catalog of ready-made automation starters — pick one, fill in the blanks (client, threshold, schedule), and it builds the automation for you. Every automation also gets a plain-English description, and you can import / export automations as JSON.

AI assistant reliability

• Fixed the confirmation loop where saying "YES" re-asked instead of committing; destructive actions now commit server-side on your confirmation.
• "Create a task for client Smithsonian" now attaches the right client by name.
• Feature & data access by role settings now save reliably (previously they could silently revert), with role matrices that keep the Role column pinned while you scroll.
• New per-role Product Docs access controls which roles get answers grounded in the official documentation.

Polish

• Automations screens use the standard page container with consistent dialogs and toasts; fixed dead links on the Subscribed Services settings page.

v3.4.0 — July 3, 2026

Automations grow up — wait steps, digests, and enterprise-grade guardrails:

• Wait steps — "wait 3 days, then continue" (or wait until a date from the triggering record). Automations pause and resume on their own.
• Activity digests — a Generate Report step rolls up recent activity for a client or your team into a ready-to-send summary; pair with a weekly schedule for automatic client digests.
• Branching & variables — a Stop step ends a run early when conditions are met; Set variable names a value later steps reuse.
• Reliability & safety — failed steps land in a reviewable dead-letter queue instead of failing silently; runaway caps, per-automation rate limits, and secret redaction are built in.

v3.3.0 — July 2, 2026

• New trigger: "On a schedule, for matching records." Automations can watch your data over time — find every ticket, subscription item, project, or client that matches your conditions and run the steps once per record. Routine "find the ones like this and act on each" work now happens on its own.

v3.1.0 – v3.2.0 — July 2, 2026

• Bill your logged hours automatically. Mark tasks Billable, log time as usual, and an automation drafts the invoice when a client's un-invoiced hours hit your threshold — or on a set day each month.
• Nine new event triggers (messages received, inbound email, ticket updates, and more), plus automation steps that notify people and assign work — react to what happens in the portal and finish the job.

v3.0.0 — July 1, 2026

• The AI Ecosystem release. Every AI capability in ClientCove is now a single catalog of permission-scoped tools available identically to the in-portal assistant, Claude via MCP, and automations — one permission model, one audit trail. The assistant and MCP can do more (estimates, invoices, richer project and client actions), and documentation search gained semantic retrieval.

June 2026

v2.65.0 — June 30, 2026

Estimates

• Estimate status now follows actions (send, client response, conversion) instead of a manual dropdown — statuses always reflect reality.
• Estimate templates — save a line-item structure once and start new quotes from it.
• Convert-to-invoice improvements round out the quote → approval → invoice flow.

v2.64.0 — June 29, 2026

Estimates (new)

• Send quotes your clients can approve. The new Estimates feature lets you build a line-item quote, send it to a client, and let them Approve, Decline, or Request Changes right in the portal. Enable it under Settings → Core Features, then open Estimates in the sidebar. See the new Estimates docs.
• One-click convert to invoice — when a client accepts, turn the estimate into a draft invoice in a click. Line items, tax, discount, and currency carry over exactly, and the two records stay linked both ways.
• Branded PDF + email — every estimate generates a secure, branded PDF, and clients get an email with a link to view and respond. You're notified the moment they accept or request changes.
• Auto-expiry — set a valid-until date (30 days by default) and ClientCove expires unanswered estimates automatically.
• Full activity log — every send, view, response, and conversion is recorded with who and when.

v2.62.2 — June 28, 2026

Automations

• New Automations builder. Administrators can now create multi-step workflows that run inside ClientCove — on a schedule, on demand, or triggered by your AI assistant. Open Automations (/automations/) to build a workflow: name it, pick a trigger, add optional conditions, and chain action steps like Create Task, Reply Ticket, or Update Client. See the new Automations section in the docs.
• Scheduled triggers — run an automation hourly, daily, weekly, or monthly. A background sweep fires due automations every hour, with no backfill of missed runs.
• Template interpolation — build action values from dynamic data with {token} placeholders (for example, Fulfill {product.name} for {buyer}).
• Dry-run preview — test any automation safely. It runs the full logic and shows a plain-English preview of every step without creating or changing anything.
• Destructive-step safety gate — automations that change data only do so unattended when you explicitly opt in, so a new scheduled automation can't act until you're ready.

v2.60.0 — June 28, 2026

Connect Claude to your portal (MCP)

• ClientCove now ships a built-in Model Context Protocol (MCP) server, so you can connect Claude (and other MCP clients) directly to your portal. Once enabled under Settings → Integrations → MCP, your assistant can read and act on clients, projects, tickets, and automations — using permission-scoped tools that run as a real portal user.
• Per-user OAuth — each person connects under their own identity; tools respect their permissions, with no shared admin credentials.
• Built-in safety — actions that change data require an explicit confirmation step, and every tool call is written to an audit log.
• Full setup and the tool catalog are documented for paid-plan customers in MCP Server & AI Tools.

v2.59.0 — June 24, 2026

AI Assistant

• The AI assistant now answers staff and admin questions straight from the official documentation at docs.clientcove.io — it reads the relevant page and replies with the answer, not just a link. Client users continue to see only your portal's own knowledge base.
• White-label your assistant — set a custom Portal name under Settings → AI → Assistant Widget and the assistant (and the daily AI summary) refers to your portal by that name instead of "ClientCove" everywhere it speaks.
• The configured Portal name now also appears on the Settings → AI → AI Configuration tab, with a link to where it's set, so it's easy to find.

Marketplace

• Fixed the primary action button (such as Buy Now / Start Plan) losing its background color inside the product details popup on the dashboard marketplace widget.

May 2026

v2.9.14 — May 1, 2026

Resources

• Resources now land in View mode after creation instead of auto-opening the editor — confirm the public-facing result immediately, then click into edit if needed
• Fixed the drag-to-upload zone on file-resource edit pages — drop new files anywhere on the dropzone and they upload directly via async-upload.php

Settings

• Application Settings menu collapses behind a toggle on tablet and mobile, with auto-collapse when you pick a tab and a label that updates to reflect the active section
• Settings sub-menu labels are now visible on mobile (they were being hidden by a legacy CSS rule)

Dashboard

• Bento grid layout now responds correctly on tablet and mobile: 3 columns at ≤1024 px, full-width single column at ≤768 px, with multi-row spans collapsing to 1 row so widgets don't leave gaps
• Tightened widget padding and softened hover transforms on touch sizes

Documentation

• Expanded Resources Library section — now covers all seven resource types, folder/workbench mechanics, file versioning, sharing, tags, permissions, and cloud storage configuration
• Added complete Projects section — overview, creating, managing, board & list, files & transfers, templates, references, and permissions
• Added complete Tasks section — overview, creating & editing, creating from projects/tickets/messages/emails, time tracking, and filters/views/bulk actions
• Added Advanced Task Options page — recurring task carry-over rules, the Quarterly/Annual interval limitation, and a deep dive on the calendar week view (Sun–Sat boundaries, drag-to-reschedule, out-of-week task visibility)
• Added Create Tasks via Email page — full SendGrid Inbound Parse setup, route configuration, for: and client: tokens, the four-step client resolution chain, attachment handling, and sender security
• Added complete Contracts section (5 pages) — overview, creating contracts & templates with PDF field placement, sending with multi-recipient template flow, browser-based E-Signature with OTP and SHA-256 audit, plus permissions and management
• Added complete Client Management section (5 pages) — overview of why clients are the hub, creating & CSV importing, the tabbed workspace, contacts & billing-contact designation, and full management/permissions/cascade rules
• Added complete Locations & Assets section (6 pages) — overview, the Locations directory and workspace, the Assets directory and workspace, the encrypted Vault with PIN-gated access, automated maintenance reminders via daily cron, and the activity-log/audit infrastructure with full schema and capability matrix
• Added complete File Transfers section (5 pages) — overview with comparison to standalone services, sending files (outbound), requesting files (inbound) with limits and file-type restrictions, Inside Projects, Tickets & Resources covering the one-click project upload link feature with Transfers In section and bulk Create Transfer flow, and the public-facing page with all three image-panel branding options (Picsum default, Unsplash feed, Custom slideshow). Cloud storage requirement called out at the top of every page.
• Added complete Invoices section (5 pages) — overview with status lifecycle and feature integrations, creating invoices with full line-item / tax / discount / currency mechanics, sending with PDF generation (auto vs upload) and Email Designer template integration, Stripe Checkout & Payments covering the full setup (API keys, webhook endpoint, signing secret) and the client-facing payment drawer with Stripe Elements, recurring invoices and management (auto-send vs auto-draft, end dates, bulk actions, CSV export, full activity log)
• Added complete Email & Campaigns section (4 pages) — overview comparing transactional vs campaign worlds, the visual Email Designer with all 9 block types and global settings, Transactional Emails covering all 22 notification types and the three-tier template fallback chain plus full SMTP/SPF/DKIM/DMARC setup guidance, and Email Campaigns with audience segmentation, batch sending via cron, open/click tracking pixel and link rewriting, pause/resume/cancel, unsubscribe handling, and CAN-SPAM/CASL/GDPR compliance notes
• Added complete Crew Dashboard section (3 pages) — overview of the manager-only workload aggregation page, full walkthrough of the dashboard UI with crew picker / date filters / comparison vs detail modes / accordion drill-down / common workflow patterns, and setup & permissions covering page creation, the explicit-access (not role-based) model, the Crew Dashboard Managers Settings panel, feature-flag dependencies, and the two REST API endpoints
• Added complete Developer Guide section (4 pages) — the child-theme-first philosophy and parent/child architecture, full tech-stack reference (WordPress + Vue 3.4 + Alpine + Tailwind v4 + Stripe + Pusher + multi-cloud storage + SendGrid), the practical "Working in the Child Theme" walkthrough with copy-paste recipes for CSS overrides, custom JS, template overrides, shortcodes, page templates, custom fields, custom post types, and sidebar menu items, and Hooks/Filters/REST API covering the standard WordPress and ClientCove-specific hooks, custom REST endpoint registration, application passwords for external authentication, webhook patterns, and common customization recipes
• Reordered nav: Projects after Resources Library; Client Management after The Client Portal; Locations & Assets after Communication Tools; File Transfers after Tasks

---

February 2026

v2.4.0 — February 20, 2026

New Features

• Real-time collaboration indicators on ticket pages
• File preview support for additional document formats
• Custom dashboard widgets (drag-and-drop layout)

Improvements

• Faster file upload speeds (up to 3x improvement)
• Improved search accuracy across tickets and files
• Better mobile navigation with swipe gestures

Bug Fixes

• Fixed an issue where notifications were not clearing after being read
• Resolved a display issue with long file names in the sidebar
• Fixed timezone display for users in non-standard time zones

---

January 2026

v2.3.0 — January 15, 2026

New Features

• Email digest feature (daily or weekly notification summary)
• Bulk file upload with progress tracking
• Ticket templates for common request types

Improvements

• Redesigned notification center with grouped alerts
• Improved dark mode contrast and readability
• Faster page load times across all sections

Bug Fixes

• Fixed an issue with file version history not loading for some users
• Resolved a bug where ticket comments could appear in wrong order
• Fixed mobile keyboard overlay on message input fields

---

December 2025

v2.2.0 — December 10, 2025

New Features

• Two-factor authentication via authenticator apps
• File version history with one-click restore
• Announcement pinning for important updates

Improvements

• Enhanced security with TLS 1.3 support
• Improved file organization with nested folder support
• Better accessibility compliance (WCAG 2.1 AA)

Bug Fixes

• Fixed session timeout issues on mobile devices
• Resolved an issue with search not returning recent files
• Fixed password reset email delivery delays