SLAtech Vantage changelog

Between August and October 2026 SLAtech Vantage gained organizations and a separate money permission, connections to more tools, a task card and quotes in the client portal, an access journal, and month handover and acceptance. This page lists only changes that are live and that a user notices, newest first. Internal improvements, tests and documentation are left out.

October 2026

• Month handover and acceptance. The provider hands over a month of work, the client accepts it, and both sides are recorded by name. Hours in a handed-over month no longer change. It is switched on per project.
• The client connects sources to their own project and sees only their own connections.
• A quote prepared outside the system can be uploaded and sent through it.
• The report sent to the client is entirely in the client's language, statuses included.
• The monthly report carries the mark of whoever did the work.
• In the chat: a switch for whether the client sees a conversation, effective at once. A conversation is no longer lost when the page is refreshed.
• In error monitoring severity reflects what is happening this week.
• The trial sends three letters along the way.
• iCount: creating a document in iCount is built and switched on per agreement.
• An email marked as junk is not downloaded again. The site is served with HSTS for a year.

September 2026

• A task card in the client portal, without the internal half. The client can reply, and someone on the provider side is notified. The client can also sign off completed work.
• A separate "what was done" for the client, alongside the internal summary.
• Quotes: sent by email, answered by the client from the portal, and the first answer is the one that counts. A quote priced in hours shows no amounts.
• Specifications: the client describes the request in their own words, and the provider gets a specification with the gaps marked. An hours estimate can be produced from a specification.
• A monthly ceiling on a task, visible to the client in the list.
• Access journal: what was done to the client's data and what left the system, readable by the client in the portal.
• Tasks: one responsible person per task, a due date and lateness in days, attachments on the card, change history, and search across all tabs.
• What is stuck: a list of what is waiting, and a morning email summary for those who opted in.
• Branding: an organization has its own logo and colour, and all letters go out in one layout with the sender's mark.
• Self-service signup from the site, and a pricing page.
• Alerts: each alert address has its own language, and the provider hears about an error once, and again only if it comes back.

August 2026

• Organizations, projects and participations: customer and provider are separate organizations, people can be invited into an organization, and access is derived from participation.
• A money permission per person. An employee sees their own hours, and the rate is stored with each time entry, so a rate change does not rewrite work already done.
• Keys to connected systems are stored encrypted and belong to the person who connected them.
• One connections screen, and new connections: Jira, Azure DevOps, Trello, Asana, ClickUp, monday.com, Linear, GitLab, Bitbucket, Sentry, Rollbar, Bugsnag, Application Insights, failed runs in GitHub Actions and GitLab CI, and time trackers.
• More than one mailbox per project.
• A screen for hours that matched no task, with the name of who logged them.
• A 14-day trial.
• A home screen with a forecast, monthly and yearly, and a comparison with the previous month.
• A maintenance page instead of a bare error during an update, and sign-in returns you to where you were.
• The chat follows task visibility and does not answer from a task the user cannot see.