SummitPSA 0.4.0 — Company lifecycle management and workflow improvements

SummitPSA 0.4.0 is a feature release. Its headline is a complete company lifecycle: you can now retire a client cleanly, restore one you retired by mistake, and — when you're finished with an account — close out its open work in a single, deliberate step. Agents also get a personal ticket layout, and we've smoothed several rough edges from day-to-day use.

Archive a company (and bring it back)

When you stop working with a client, you no longer have to choose between a stale record cluttering every list and deleting something you might need again. Archiving hides a company from your active lists and from every picker — new tickets, quotes, invoices, contracts, assets, contacts — so no new work is raised against it by accident. What it does not do is break anything: existing tickets, invoices and history keep showing the company's name exactly as before, and its open tickets stay visible in your queues until you finish them.

• Fully reversible. Restore an archived company any time and it — and its contacts — return to full availability, with no half-finished state to tidy up.
• Findable, not lost. An "Archived" view keeps retired accounts one click away, and archived companies and their contacts are clearly badged wherever they still appear, so a name you can't select is never a mystery.
• A clear review before you commit. Archiving opens a summary of what's attached — open tickets with assignees, unpaid invoices and the amount outstanding, active contracts and open quotes — so a forgotten receivable never slips by. The figures are re-checked the moment you confirm, so you're always deciding on current information.

Super admins can also permanently delete a company that has no records at all — useful for clearing up a duplicate created by mistake. Anything with history must be archived instead.

Close out an account's open tickets in one step

Retiring a client often leaves a pile of open tickets that no longer need working. From the archive review you can close every open ticket and archive the company together. Because you've just stopped serving this client, customer-facing messages are held back by default — no closure emails or satisfaction surveys go out unless you explicitly opt in with a single checkbox. Each ticket is stamped with a plain note that it was closed as part of archiving, so the history explains itself later.

Your ticket layout, your way

Each agent can now set how the ticket screen reads, saved to your own account:

• Conversation order — newest reply first, or oldest first.
• Reply box position — top of the conversation, or bottom.

It applies only to you — nothing changes for teammates or for clients in the portal.

Fixes and polish

• Knowledge base editing saves reliably again. Editing and saving a staff KB article works as expected.
• Settings stay put. Saving settings no longer resets numeric values (time rounding, minimum billable minutes, default tax rate, report scheduling) or quietly switches off satisfaction surveys — your configured values persist across saves.
• Smarter ticket contacts. Choosing a company on a new ticket now scopes the contact list to that company and selects its primary contact for you.
• Reliable status changes. Updating only a ticket's status — including on merged tickets — now applies instead of occasionally being discarded.
• Easier support conversations. The version you're running now appears in the footer of your staff pages.
• Knowledge base filtering. The staff knowledge base visibility filter now includes Public.
• Two-decimal tax rates are shown and stored precisely, and a legacy category label was tidied up.

Under the hood

Outbound integrations (such as chat notifications and webhooks) now validate their destinations before sending — a defense-in-depth improvement. As with our previous release, 0.4.0 ships with a clean dependency-security baseline: no known third-party advisories are outstanding as of this release.

Upgrading

0.4.0 includes database changes, which are applied automatically when the update runs. As always, we recommend taking a backup before upgrading and keeping your previous version available as a rollback.

Self-hosted operators: the update appears in your admin area — review it and apply it when you're ready. Nothing installs itself.