Skip to content
Orbitify
Changelog

Release 2026.11.09

Every change we make that people can see, newest first. Each release is named by the day it went out.

November 9, 2026Release 2026.11.09

Changed

One work order for several requests

One work order can now answer several requests, and by default it closes by itself once every request on it is closed (Closes with its requests, on each work order type under Settings, Types and custom fields). A request's urgency sets its work order's priority: Critical to Emergency, Major to Urgent, Moderate to Normal, Minor to Routine. Change or switch this off under Settings, Company profile, Priority from urgency. This took effect with this update, without the usual notice.

What to do, by November 23, 2026

  1. Open Settings, Company profile, and check Priority from urgency; on each work order type under Settings, Types and custom fields, check Closes with its requests.
In plans with OperationsLink
New

See who handles each request

Requests and work orders have a new card, Who handles this. It says who the work waits for now and since when, then every step in order with who does it and why: the team and the rule that chose it, who it was given to, each approval with its people in turn, and who confirms the fix. Below, the team from the top team down.

In plans with OperationsLink
New

My team for supervisors and dispatchers

Supervisors and dispatchers have a new page under Work, My team. For each team they run it shows every person's day, hours planned this week, open work orders, certificates ended or ending soon, and what their job profile still needs. Needs you lists work orders nobody has with the best match, approvals waiting for your yes, and requests about to miss their SLA.

In plans with OperationsLink
Changed

Requests have a title and urgency

A request now has a short title and a description, so lists stay easy to read while the details sit below. What was called severity on a request is now called Urgency on the request screens. The levels and your company's own words for them are unchanged.

In plans with OperationsLink
Changed

A request needs a location

Before, a request could be raised without saying where. Now every request raised in the app needs a location, or an asset that has one, so it reaches the right team and the right files. Systems connected through the connector API are not affected. Raising a request for someone who called or wrote is now its own permission, Raise requests for someone else, given to every role that could already change requests. This took effect with this update, without the usual notice: please tell the people who raise requests, including your clients' people.

What to do, by November 23, 2026

  1. Tell the people who raise requests, including your clients' people, that a request now needs a location.
In plans with OperationsLink
New

Merged requests keep everyone informed

When a duplicate request is merged into another, the people who raised it follow the one you keep: each is told how it goes and sees it in their own list. A request shows who else is following it.

In plans with OperationsLink
New

Choose who confirms a fix

Each request type now says who confirms that a fix worked: whoever raised it (the default), your client's people, the team's supervisors, people with a role, named people, or nobody, in which case the request closes once its work is done. Set it on a request type under Settings, Types and custom fields. The Inbox asks exactly those people.

In plans with OperationsLink
New

Teams hear of new requests

A new request now tells its team's supervisors and dispatchers, or, with no team yet, whoever may change requests. Every company has this as a notification rule, New requests, which you can change or switch off under Settings, Notifications.

In plans with OperationsLink
Changed

Files show for their own location

Before, a request or work order listed every file of the places above it as well, such as the whole site's drawings. Now it shows the files of its own location and of its assets. Whoever raised a request, and whoever follows it, can add their own files to it and remove those they added.

In plans with OperationsLink
Changed

Default step names change; approval step added

Request workflows that still used the platform's own step names now say Closed instead of Resolved, and work order workflows Done instead of Completed; names your company chose are unchanged. Every work order workflow without one also gets a Waiting for approval step after its first planned step, where work waits while an approval rule holds it. This took effect with this update, without the usual notice: check your workflows under Settings, Workflows.

What to do, by November 23, 2026

  1. Open Settings, Workflows, and check the step names and the new Waiting for approval step suit your company.
In plans with OperationsLink
Changed

Assign, schedule and finish in one place

Giving a work order to someone and choosing its day is now one form, Assign and schedule, in place of the separate dialogs. Mark done asks what was done in one sheet. Each work order shows a timeline of when it was made, given to someone, started, paused and done. When a fix is not confirmed, the same work order is taken up again, or a follow-up is made if your company chose that under Settings, Company profile, When the fix is not confirmed.

In plans with OperationsLink
Improved

Approvals name who they wait for

A pending approval now names the people whose yes it waits for, such as Waits for Lan Nguyen (the supervisor of its team), not only the kind of approver. The work order page no longer repeats an approval in its Waiting for box.

In plans with OperationsLink
Changed

Team leads are now called supervisors

A team's Lead is now called Supervisor everywhere. A supervisor now manages the people of the teams they supervise, without a company-wide permission: they add and take out people, move them between member and dispatcher, set their skills and record their certificates. Only someone who manages teams makes or changes a supervisor.

Improved

Roles and teams are easier to read

People now says Company role for what someone may do, and shows when a person runs teams instead of warning that they have no role. A person's page explains company role, job profile and team role in one line. Teams lists your own teams, contractors and client users apart.

Changed

Menus show only what you may use

The menu, Settings and your profile now show only pages you may see or change. Someone without the right to see assets no longer finds Assets or Warranties and contracts; someone in no team of your own no longer sees Skills, Work preferences and certificates on their profile; Settings shows each person only what they may change. This took effect with this update, without the usual notice: if someone misses a page, give their role the permission it needs.

What to do, by November 23, 2026

  1. If someone misses a page they need, open People, Roles, and give their role the permission it needs, such as See asset details.
Fixed

Rules screens say what they do

The Approvals list now calls each work order a work order. The rules pages under Settings name the page you are on, Assignment rules, Service levels (SLAs) or Approval rules, instead of Automation rules. The approval rules help now says that work waits in its Waiting for approval step, and a new assignment rule says its priority is for work orders.

In plans with OperationsLink

How we change Orbitify

New things and fixes go out as soon as they are ready. A change to how you already work, or one that asks something of you, is announced ahead, by this much:

Kind of changeNoticeHow you hear
A new feature, an improvement or a fixNone: announced on the dayWhat's new and this page
A change to how existing work is done: a moved screen, a renamed step, a new required field, a default switched onAt least 14 daysA notice to your administrators, and a coming change in What's new
An administrator must act; a feature is removed; where data is kept, or which AI model or region answers, changesAt least 30 days, with a date to act byA notice to your administrators by email and in the Inbox until one of them acknowledges it, and a reminder 7 days before
A change that breaks what a connected system does through the API or webhooksAt least 6 months, under a new API versionThe API changelog on the developers page, an email to whoever answers for each connection, and Deprecation and Sunset headers
A security fixNone: explained afterwardsThis page

Building on the API? See the developers page for its version and its own changelog. Developers