Changelog

New

• Custom objects filled from BigTime — Once BigTime is switched on for objects in your account, your custom objects can be filled and kept up to date from its projects, invoices, tasks, payments and staff, with a Logs tab showing every run and request.
• Tasks for several teammates — A task can now be assigned to several teammates, and each of them sees it in their Tasks panel, is notified when assigned and gets its reminder.
• Tasks without a record — You can now create a task from the header Tasks panel without attaching it to a deal, person, company or lead, and switch to see the tasks you've assigned to others.
• Portal sections at the bottom of the screen on phones — On phones, your knowledge base, support portal, status page and changelog now show their sections in a bar at the bottom of the screen that tucks away while visitors scroll.

Improved

• Your tasks — The header Tasks badge, the dashboard focus list and My Tasks now show only tasks assigned to you, rather than every task in your workspace.
• Adding and editing tasks — Adding a task opens a larger panel that assigns it to you by default and offers quick reminder options, and clicking a task on a deal, person or company opens it for editing.
• Deleting an object type — A deleted object type can now be restored with its fields and records from Recently deleted for 30 days.
• The object model board — The object model now shows which way data flows from an integration into your object types and onto your records, and a Tidy up button rearranges the board.

Fixed

• Task reminders — A reminder set on a task now notifies its assignees at the chosen time; before, it was saved but never sent.

Security

• Tasks kept within their account — Tasks can now only be seen, changed or added from within the account they belong to.

New

• Scheduled maintenance — You can now schedule maintenance ahead of time with its window, the services it affects and the disruption to expect; your status page lists it as upcoming, it starts and completes on its own at those times, and it can email your subscribers when it's scheduled, when it starts and when it's done.
• Third-party services on your status page — A service can now be marked as a provider you depend on, linked to one of your integrations and to that provider's own status page, and your public status page shows those services in their own group.

Improved

• Reporting an incident — Reporting an incident is now one form (what's happening, how bad it is, which services it affects, and the first update), those services' statuses change with it and go back when it's resolved, and updates and resolving happen right from the incident.
• Your public status page — Your status page now shows active incidents and upcoming maintenance above your services, names the services each one affects, shows times in the visitor's own time zone, and uses one label, Outage, where it used to say Partial or Major Outage.
• Status page services in one place — Your status page's services are now managed on the Status page, next to the incidents that set them, instead of in Portal Settings.
• Portal header — On your knowledge base, support portal, status page, changelog and project portal, the header now tucks into small floating islands as a visitor scrolls down and becomes a full bar again at the top, and on phones search and the assistant stay available as icons with the language switcher moved into the menu.

Fixed

• App restarting during a database interruption — A brief database interruption could make a background task restart the app for everyone using it; the error is now logged and the app keeps running.
• Status page services through the API — Creating or updating a status page service through the API now checks its fields and answers an invalid status or display order with a clear error.

Security

• Status page services moved into another account — Someone able to edit status page services could move one of their own services, with its status, onto another account's public status page; a service can no longer leave the account it belongs to.

Improved

• Video links in the customer portal — A step's link now gets a Play button only when the portal can actually play it, more YouTube, Vimeo and Loom links play — Shorts and live links among them — a link straight to an .mp4 or .webm file plays in the portal's own player, and the player offers Open in new tab for a video its provider won't show there.

• A lighter customer portal — The customer portal does less work while customers use it: a video in the project header loads when someone presses play rather than on every visit, and saving a change no longer reloads the whole project twice.

• Confirmation pop-ups — The confirmations at the top of the screen are now slightly see-through, always show a × to dismiss them, and leave in half the time, so they no longer sit over the navigation while you wait for them to go.

Fixed

• Unlisted Vimeo videos — An unlisted Vimeo link now plays instead of showing "Sorry, this video does not exist" — on a project step straight away, and in a knowledge base article or project header once the video is added again.

• Teammates recorded as "Customer" on a project's timeline — Verifying, rejecting or editing a step in the project editor was recorded on the project's timeline — and shown to the customer — as "Customer", and restoring a deleted step as "Admin"; the timeline now names the teammate who did it.

• Changes missing from an open customer portal — Adding, deleting or restoring a step, resetting or archiving a project, and changes made through the API now appear straight away in an open customer portal and in the project editor, where before some of them only showed up after a reload.

• Step field values in projects created from a template — A project created from a template in the create wizard now keeps the values filled in on the template's step fields, which the wizard was dropping.

Security

• Project portal requests that didn't check who was asking — A project's portal link could be used to look up its PIN, and a project's id alone was enough to read its full history — internal-only steps included — restore or change steps, and read, post or delete comments as anyone; each now needs the PIN or a signed-in customer or teammate, and comments no longer show teammates' email addresses to customers.

• Unlimited guesses at a portal PIN — Nothing limited wrong guesses at a customer portal's 6-digit PIN; ten wrong tries on the same project within 15 minutes now pause sign-in from that network until the 15 minutes are up, and the login screen says when it reopens.

• Integration connections finished from a forged link — A crafted link could finish connecting an integration such as Slack or Google Drive into another account — replacing a connection it already had — and the page shown after connecting could be made to run a script; a connection now completes only in the signed-in session that started it, and connecting a workspace-wide integration needs settings access.

• Webhooks and data sources pointed at our own network — Webhooks, automation and sequence webhook steps, Sherlock data sources, custom integrations and the PostHog connection could be aimed at addresses inside our own network, directly or through a redirect; each must now point at a public address (https for web addresses), checked when it is saved and again every time it connects, and redirects are no longer followed.

• Custom-field values readable from another account — Someone signed in to one account who had the id of a project, deal, ticket, contract, person or feedback item in another account could read — and usually wipe — its custom-field values; each is now checked against the account you are signed in to.

• AI assistant tools reaching other accounts — Eight of the tools a connected AI assistant uses — sending a chat message, editing a knowledge base article and updating a project step among them — could act on another account's records given their id; every tool now stays inside the account its connection belongs to, and a conversation can only be assigned to a member of your own account.

• Sherlock setup open to every teammate — Any teammate, whatever their role, could add, change or delete Sherlock's data sources and settings and see the connection strings and keys they hold; changing them now needs settings access, and teammates without it see those credentials masked.

New

• Sharing an update with chosen teams or teammates — The Everyone pill on the dashboard composer now opens a real picker, so an update can go to the whole workspace, to particular teams, or to named teammates in any mix, and every post shows who can see it.

• Customers completing a step without editing it — A project step now has its own "Customer can complete" switch, so a customer can tick it off, fill in its form and upload files without being able to change its title, dates or description — new steps start out that way, and steps you already have keep exactly the permissions they have today.

• Completion confetti in the customer portal — A project now has its own Completion Confetti switch in its settings rail, so the customer portal celebrates when the last step is done; until now it borrowed the embeddable checklist widget's switch, which almost no project had turned on.

Improved

• Editing a step in the customer portal — A step opened in the portal now has Close, Edit details and Mark complete along the bottom, and editing holds your changes until you press Save changes — one save instead of a write for every field you touch — with a prompt before anything unsaved is thrown away.

• Link / Video on a project step — A step's link field is now labelled "Link / Video" with an explainer beside it, because a YouTube, Vimeo or Loom link becomes a Play button in the customer portal while any other link opens in a new tab.

Fixed

• Pages that slowed the browser down — Eleven pages, the project editor, ticket detail and People among them, kept re-rendering without ever settling, which is what made Chrome warn that a tab was slowing the browser down.

• Opening a project counted as editing it — Opening a project or template no longer saves a draft a second later and stamps it with the name of whoever merely opened the page, and an edit made just before you navigate away is now saved rather than lost.

• The customer portal updating live — Customers in the project portal now see steps, comments and verifications change as your team makes them; until now that live connection only worked in a browser that happened to be signed in as staff as well.

• Webhooks always reporting "Never" delivered — A webhook now records every delivery attempt, so Developer settings shows when it was last tried and how many times in a row it has failed, with the history filled in for webhooks that had been receiving events all along.

• Testing and deleting a webhook — The Test button now sends to the webhook you pressed it on and tells you what came back, and a webhook that has ever delivered anything can be deleted instead of failing with an error.

• Clearing a step's due date — "Clear due date" in the customer portal's step panel now removes the date instead of quietly leaving it in place.

Security

• Managing webhooks needed only a login — Creating a webhook streaming your account's events to any address, deleting someone else's, and reading every webhook's signing secret and the full event payloads it had delivered all needed nothing more than an account; each now requires settings access.

• Anyone could create an API key — Creating an API key now requires settings access and at least one permission, a key stops working the moment its owner is removed, locked or loses that access, and using one no longer hands back a browser session with more access than the key itself.

• Live channels signed for the wrong account — A signed-in user of one account could listen in on another account's project, ticket and conversation channels — including the one carrying agents' names, avatars and reply text as it is typed — and each is now checked against the account you are actually signed in to.

• Projects reachable by guessing a 6-digit code — A retired embeddable-checklist address let anyone who guessed a project's 6-digit code read that project in any account, internal-only steps included, and tick its steps off; it has been removed.

• Deleting or changing a step from the customer portal — A crafted request from the customer portal could delete any step of a project, or change one hidden from the customer entirely; both are now refused unless the step's own switches allow it.

New

• Custom fields when creating a company — Creating a company — from the Companies list or the ⌘K menu — now includes the company custom fields you can edit, filled in with their defaults, and any required one has to be completed before the company is created.

Improved

• Creating records in a side panel — Logging feedback, creating a product, sequence, course or company, and creating or editing a coupon or changelog entry now happen in a panel over the page you were on rather than in a pop-up or on a separate page — and none of them throws away what you have typed without asking.
• Nothing saved until you finish — Creating a product, sequence or coupon no longer saves a half-finished copy as you go, so abandoning one partway leaves nothing behind on the list, and a new product now starts out active, with a switch to turn that off.
• Company reports without an automatic AI verdict — The AI-written health verdict at the top of a company's report has been removed, so viewing one no longer spends an AI call on your connected Claude account.

Fixed

• Changelog announcements sent again on every edit — Saving a change to a published changelog entry no longer emails every subscriber again or re-announces it in the chat widget — an entry is announced once, when it is first published, and publishing several at once keeps the original date of any that were already live.
• Links in emails to status subscribers — Emails telling your status-page subscribers about a new changelog entry or a status change now link to your own changelog or status page, on your custom domain if you have one, instead of a status page that was not yours.
• Sequences set to send any time — A sequence set to send at any time no longer becomes a weekday 9-to-5 one the first time its steps are saved, and a new Sending window switch in its settings turns the window off again for any sequence this already happened to.
• Live Activity reporting no activity while it loaded — The Live Activity report now shows placeholders while it loads and a Retry button when a section fails, instead of saying there was no activity in the last 24 hours, and its chart shows quiet hours as quiet rather than squeezing them out.
• Closing a create panel while it saves — A create panel now ignores Escape and clicks outside it while it is saving, rather than offering to discard work that was about to be saved anyway, and one opened from a link no longer loses what you typed when the page behind it finishes loading.
• Removing a coupon's redemption limit — Clearing a coupon's maximum number of redemptions now removes the limit; before, the field snapped back to the old number, so a limit could never be taken off once set.
• Read-only steps in the customer portal — A step your team has made read-only now shows its status in the customer portal's task list like any other step, instead of a "Team" label sitting where the status belongs.
• Changelog entries created through the API — A published entry created through the public API now appears on your changelog and in the chat widget straight away and, when it asks to, emails your subscribers — which now requires an API key belonging to a manager or above.

Security

• Changelog entries moved into another account — A manager in one account could use a specially crafted request to move a changelog entry, with any content they chose, into another account's public changelog; an entry now always stays in the account that owns it.

New

• Your object model on a canvas — A View model button on the Objects settings tab opens a board showing every object type you have defined, the fields on each one and which records they attach to — you can rearrange it, open a type to edit it in place, and attach a type to a record type by dragging a line onto it.
• Object fields that must be unique — An object field can now refuse a value that another record of the same type already holds, and a type can require the same of its record names — both ignoring capitalisation and surrounding spaces.
• Deal properties per pipeline — Each pipeline now has a tab choosing which deal properties it shows, honoured on the deal form, the deal record, the table view and the kanban card picker — everything shows everywhere until you hide something, so nothing changes until you use it.
• Publish an article in every language at once — When your knowledge base has more than one language, a chevron beside Publish opens a dialog that publishes each language of an article together and translates the ones that do not exist yet; a plain Publish now offers the same for whatever is still outstanding.
• File and image fields on project tasks — A task field can now ask the customer to upload a file or an image as its answer, and an information field gains a file button so staff can attach a document alongside the images and links it already supported.

Improved

• Wider articles in the knowledge base — The site navigation on an article page collapses to a slim strip and gives the width to the article, floating out over it when you hover and staying open if you pin it.
• Editing an object type — Fields reorder by dragging, adding one sits behind a button rather than always open, each setting explains what it does to records that already exist before you switch it on, and a single Save in the footer commits everything — with a prompt if you try to leave unsaved work behind.
• Notifications open in a panel — Creating or editing a notification now opens a panel over the list rather than replacing the whole page, matching the other create flows in the app, and the links straight to one still work.
• The project step editor — The step editor moves into the standard panel and confirms before discarding unsaved edits, a long-text field’s label is written in a box that grows and keeps your line breaks, a step opens from anywhere on its row, and a project’s progress and who else is viewing it move up beside the title.

Fixed

• Slack cards for ticket edits that changed nothing — Saving a ticket without actually changing anything posted a card to Slack while logging nothing and notifying nobody — clearest on bulk edits, which re-announced every ticket left selected from the previous one.
• What a bulk ticket edit skipped — Fields already holding the value you are applying are left alone, so an unchanged ticket no longer jumps to the top of the list, and the confirmation counts tickets that were already up to date apart from ones it could not edit.
• Translation runs finishing unnoticed — A bulk translation that had finished left the language pill reading Draft until you reloaded the page, and went on checking for the run indefinitely.
• Cut-off navigation titles on phones — Long category and article names were truncated in the knowledge base’s mobile menu even where there was room to wrap onto a second line.

New

• Step fields on the customer portal — A field on a step now appears on the customer's view of that task, either as text they can read or as something they can fill in — you choose per field.

Improved

• Custom fields live on each step — The fields you define for projects now belong to each individual step rather than to the project as a whole, on projects and project templates alike, so you can track something different on every step.
• Clicking anywhere on a step opens it — You no longer have to hit the step's name to open its editor — the whole row is clickable, and reachable from the keyboard.

New

• Objects — Admins can now define their own record types — a Quote, a Site Visit, an Asset — give them their own fields, and attach them to companies, people, deals, projects, tickets and help desk conversations from each record's side rail.
• Import contacts from your mailbox — With Gmail connected, you can now review the people you already exchange email with and add them to the CRM in bulk, each shown with how many messages you have traded and when you last spoke.
• Staff replies on project comments — Comments customers leave on project tasks in the portal now appear in a panel on the project itself, with an unread count and a reply box — until now there was no way to read them from the app at all.
• Attachments on project comments — Customers can attach images, video and documents to a comment on a project task, and the upload is recorded in the project's history so your team sees it.
• Information fields on project tasks — A task field can now show the customer a block of formatted text instead of asking them to fill something in, and it never stands in the way of completing the task.

Improved

• Finding and merging duplicate companies — The duplicate scanner is now a labelled button that appears only when there is something to resolve, each candidate shows its domain and how many people, deals, tickets and conversations it holds, and the dialog says plainly that nothing is deleted.
• Editing custom fields — Custom field rows are clickable on all five tabs and open an editor panel with Save and Delete pinned at the bottom, and the People tab gains the date-format picker the other tabs already had.
• Creating forms and documents — New web forms and new knowledge base documents open in a side panel instead of taking over the page, and abandoning one no longer leaves a half-finished draft on the list behind you.
• Scroll for more — A list or side panel with more content below the fold now says so, instead of looking exactly like a list that ends where it is cut off.

Fixed

• Slack notifications for conversations that are not yours — Being @mentioned once in a help desk conversation's Slack thread no longer signs you up for every message it receives afterwards — mentions are now used only where they are the sole way a person is told, and assignment notices go by direct message instead.
• Indented lists in help desk replies — An indented list typed into the reply box now reaches the customer indented — in the widget, in email and in Slack — and nests up to three levels instead of flattening.
• Side panels with their buttons out of reach — Side panels now pin to the window everywhere in the app, so the row of buttons along the bottom — the only way out of a panel with no close X — can no longer end up below the fold.

New

• Deals report — Reporting now has a Deals report covering pipeline health, win rates and time to close for one pipeline at a time — written in that pipeline's own words, so a hiring pipeline reports on candidates rather than deals, and a pipeline that tracks no money shows no money.

Fixed

• Meetings with long transcripts never imported — A Granola meeting whose transcript was too large to fetch in one piece now imports normally; previously it failed quietly and also held back every meeting recorded after it.

Security

• Analytics could include other customers' figures — Pipeline, help desk, onboarding, form and page-view analytics now count only your own account's data — some of these figures previously included totals from across all accounts.