Skip to content

Kaleta 3.28.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 09:21
· 88 commits to main since this release

Customers: one record per person and company, built from your website's enquiries, bookings and newsletter – the core of the built-in CRM. And off-site backups are now encrypted. Update when convenient – and save your recovery key afterwards (see below).

Customers

  • Workspace → Customers lists everyone who has contacted you: search, filter by responsible person, company or last activity, and a Companies tab.
  • A customer's page shows their details, the responsible person and a timeline of everything with them – enquiries, your replies, bookings, the newsletter subscription, team comments, tasks, and calls, meetings, e-mails and notes you log.
  • New enquiries, bookings and confirmed sign-ups are linked to the customer by their e-mail address right after they are sent; older ones are linked gradually in the background. Two different addresses are never merged by themselves – administrators merge duplicates by hand.
  • A company is suggested from the e-mail domain (never for Gmail, Seznam and the like).
  • Every enquiry and booking shows a Customer box.
  • Administrators can export and import customers as CSV. Ctrl K finds customers.
  • Everyone who can open Enquiries can open Customers after the update; change it in Users → Roles.

Privacy

  • Customers with no activity for the enquiries' retention period (24 months unless you changed it) are anonymised; comments and tasks count as activity. An expired enquiry leaves "first contact on … through the form …" without the message.
  • Finding, exporting and erasing someone's personal data now include their customer record. The record of processing has a "Customer relations" part.
  • Claude's changes to customers cannot be undone; merging customers through Claude is for administrators only.

Encrypted off-site backups

  • Database copies sent to FTPS or S3 are encrypted before they leave your server, with a recovery key kept outside the database.
  • After updating, open Settings → Backups and updates → Show and save the recovery key, keep it somewhere safe and confirm. Until then, off-site database copies wait (backups on the server go on) and the site tells you so.
  • Without the recovery key an off-site backup cannot be restored.

For Claude

  • New tools list_contacts, get_contact, save_contact, log_activity and merge_contacts, also in the work tool set; comments and tasks can be about a customer or a company.

One database change. No setting, MCP tool or parameter renamed. Security and privacy review before release.

Full Changelog: v3.27.0...v3.28.0