Release notes
Updated November 17, 2026 · Applies to Platform ONE 1.59
ONEConsult.NET Ltd. updates Platform ONE for you. Your current version is shown on the Modules page, under Administration, and when you point to the product name at the bottom of the menu.
1.59.0
Platform ONE
- Records follow product access. Inside a product someone uses, the parts of a product they haven't been given are hidden.
Rolodex ONE
- Without BookIt ONE, a contact shows no bookings. The Book button and the contact's bookings are hidden from people who don't use BookIt ONE.
PTO ONE
- Without BookIt ONE, time off counts bookings only. A request or approved time off says how many bookings fall in the period; people who don't use BookIt ONE don't see or open the bookings.
1.58.0
Platform ONE
- Notifications follow product access. People get no notifications from a product they haven't been given, and their Notifications page lists only the kinds from their products.
- API keys follow product access. A key that acts for a person uses only that person's products; a key that acts for a team uses the products for everyone and those given to the team.
1.57.1
Platform ONE
- Product access is easier to scan. Each product is a card showing who uses it, side by side, with Save at the top of the page.
1.57.0
Platform ONE
- Choose who uses each product. Under Administration, Product access gives each of your products to everyone, or only to the teams and people you choose. A product someone doesn't have is left out of their menu, and its pages tell them they don't have access. Administrators always have every product. Until an administrator saves Product access once, only administrators can use your products. See Choose who uses each product.
1.56.0
Platform ONE
- One product at a time in the menu. When your organization has two or more products, the menu shows one of them at a time. Choose which in the Showing list at the bottom of the menu; Administration there holds your organization's settings, people and Studio. Everyone's choice is remembered on their account, and opening a page of another product switches to it. See Find your way around.
1.55.0
Platform ONE
- Staff and resources are part of the platform. Staff, rooms, equipment and bays, their kinds and working hours are now kept with your organization's other core data. Nothing changes in how you use them, and nothing was lost; the Modules page no longer lists Resources on its own.
1.54.0
Platform ONE
- Every unexpected error has a code. When something unexpected goes wrong, people see
Something went wrong over the page with an error code, such as
7F3K-2Q9A, and can go back to the page. Administrators find the error by its code on the new Errors page, under Administration, for 30 days. See Look up an error. - API: unexpected errors carry their code. A call that fails with status
500answers anerrorIdand atraceIdin its body.
1.53.28
Platform ONE
- See how large a Studio package is. A release's page shows its package size against the 5 MB limit, with a bar that turns yellow from half the limit and red from three quarters, and a notice to split the release. Under Releases, large releases show their size next to their name. See Move changes between environments.
1.53.25
BookIt ONE
- Customers connect a sign-in themselves. Where you've set up a sign-in provider for customers (default role Customer), customers see it under Sign-in options on My profile and can connect it to their account. They're emailed each time one is connected. Providers for staff aren't offered to them. See Manage your appointments.
1.53.24
BookIt ONE
- Merge two records of one customer. Administrators can select Merge on a customer and choose the other record. Appointments, notes, documents, emails and history move to the record kept, sign-ins with Google or other providers are connected to its account, and the customer is told by email. See Manage customers.
1.53.23
BookIt ONE
- Send a customer a password reset. When a customer can't sign in, administrators can select Send password reset on the customer, and reception and managers on one of the customer's appointments. The customer gets the same link as Forgot password?; nobody else sees or sets the password. Each one is recorded in the audit log.
- Through the API too:
POST /customers/{id}/password-reset. With a key that needs approval, it waits for a person under API approvals.
1.53.18
Platform ONE
- An API key that acts for someone gets all their events on the first page.
GET /eventsleaves out other people's records before it cuts the page, so a page is no longer short or empty when there are more to come. - Webhooks of a change made through the API are sent at once. Since 1.53.6 they could wait up to a minute, and so could a workflow the change starts.
Rolodex ONE
- Large documents through the API.
GET /documents/{id}/contentgives a document's file as it is, andPOST /documents/contenttakes one sent as it is, up to 25 MB. Use these for large files;contentBase64stays for small ones.
1.53.17
Platform ONE
- An API key's single calls are kept for 7 days. Its activity page still shows the last 30 days, counted per day, with its most frequent errors; Latest calls lists the last 7 days. For a write that failed, the first 2,000 characters of what it sent are kept.
- What an API change sent is removed 30 days after it was decided or lapsed. The change stays listed.
1.53.15
Platform ONE
- The nightly demo reset runs on its own. Other background jobs wait while a demo is restored to fresh data, so a reminder or mailbox sync no longer fails on records the reset has just removed.
1.53.6
Platform ONE
- A change through the API is made in full or not at all. When a call that changes records fails part way, nothing it did is kept, as its error message says. Before, part of the change could stay.
- Trying a change no longer adds to the audit log. A call sent with
dryRun=true, or held for approval, could add entries to the audit log for a change that was never made. - The holidays year is your organization's. The Holidays page opens on the current year where your organization is, not where the server is.
Rolodex ONE
- Due dates count from your organization's today. A new follow-up is due in a week, and a new deal is expected to close in 30 days, counted from today where your organization is. Before, late in the day they could be a day off.
PTO ONE
- "Export this year" exports your organization's year. Around New Year, the time-off export took the year where the server is.
1.51.22
Platform ONE
- Trying a change through the API no longer shows it. A call sent with
dryRun=true, or held for approval, that changed teams, departments, people, holidays or your organization's settings (such as the words used for customers) could briefly show that change on screens and in other calls, though it was never saved. Only saved changes now show.
1.51.8
Platform ONE
- Full pages for API keys that act for someone. A key that acts for a member of staff or a team now gets full
pages of their records, and
nextis empty on the last page. Before, pages could be short or even empty while more records were still to come.
1.51.6
BookIt ONE
- A reminder is sent only once. A customer could get the same reminder twice when reminders were sent automatically at the same moment someone selected Send due reminders now.
1.51.5
Platform ONE
- Busy networks no longer see "Too many attempts". Many people can open your public pages from the same network at once, such as phones on one mobile carrier or an office, before anyone is refused.
BookIt ONE
- A limit on online bookings. A customer can make up to 10 bookings in an hour themselves. After that, they're asked to wait or contact you. Bookings your staff make for them don't count.
1.51.4
Platform ONE
- Microsoft Entra ID roles need your directory ID. Role mappings for a Microsoft Entra ID provider apply only when its Directory (tenant) ID is set. Without it, the roles are ignored and the provider's form warns you. See Set up sign-in and single sign-on.
- Customers can connect only customer sign-in providers. Your staff sign-in providers are no longer available to customers.
1.51.3
Platform ONE
- Emails go out straight away again. An email queued while the previous ones were still being sent, such as a booking confirmation, could wait for the next scheduled run of the email queue. It's now sent as soon as the previous batch finishes.
1.51.0
Platform ONE
- A new webhook secret no longer breaks the receiving side. After you select New secret, each call is signed with both the new and the old secret for 24 hours, so you have a day to give the receiving side the new one. See Connect other systems with API keys and webhooks.
- More addresses refused for webhooks. Addresses reserved for documentation, and IPv6 addresses that lead into IPv4 networks, can't be used for a webhook.
1.50.2
Platform ONE
- Brand colors are checked wherever they're saved. A brand color is always saved as
#and six hexadecimal digits, for example#1E5AA8, including from a Studio release. Emails and pages always use a valid color.
1.50.1
Platform ONE
- Required two-factor sign-in holds everywhere. When your organization requires two-factor sign-in, someone who hasn't set it up stays on My profile until they do, including when they select another page in the menu.
1.50.0
Platform ONE
- The first administrator chooses their own password. The first time they sign in with the password they were given, Platform ONE asks them to change it on My profile before anything else opens. See Quickstart: Set up your organization.
1.49.3
Platform ONE
- API: an address that doesn't exist answers 404. For example,
/api/v1/bookingson a tenant without bookings answers404 not_foundagain, instead of sending the caller to the sign-in page.
1.49.2
Platform ONE
- Signing in is required by default. Every page and address now needs someone signed in, unless it's meant to be public, such as the sign-in pages, the booking pages and the API description. Only an administrator can save the organization's settings, wherever the change comes from. Nothing changes in how you use Platform ONE.
1.49.1
Platform ONE
- Safer links between your environments. When Studio sends a package to another of your environments, or refreshes one from production or test, each request can be received only once, and a package can be up to 5 MB, both sent and imported as a file (up from 1 MB for files). An environment that isn't linked to others no longer answers these requests at all. Nothing changes in how you move changes. See Move changes between environments.
1.49
BayCheck ONE
- Bay recommendations are easier to see. When every bay is busy, the gate says how many waiting trucks can go to a bay sooner, with Show them to list only those; the dock board shows the same recommendation under In the yard; and the site's managers and front desk get a notification in the app. Each person can switch that notification off from their profile, under Choose your notifications. See When every bay is busy.
1.48
BayCheck ONE
- When every bay is busy, the gate recommends the bay that frees up first. For a truck waiting for a busy bay, the gate works out which bay at the site can take it soonest, from how long trucks have spent at a bay today, and recommends it when it's sooner than the truck's own. The dispatcher moves the truck there or keeps it waiting; both are recorded. A moved driver is emailed and their booking page shows the new bay. The booking keeps its time. Each site sets how much sooner a bay must be, and when a declined recommendation comes back. See When every bay is busy and Set up bay recommendations.
1.47
Platform ONE
- Two-factor sign-in. Anyone who signs in with a password can add a code from an authenticator app on My profile, with recovery codes for when they don't have their phone. Administrators can require it for administrators or for all staff under Sign-in & SSO. Every edition includes it. See Set up two-factor sign-in.
- API: retries are safe even when they overlap. A
POSTwith anIdempotency-Keyis now claimed before it runs. The same request sent again while the first is still running gets409 idempotency_in_progresswithRetry-After: 1, and the same key sent with a different body gets409 idempotency_key_reused. A request that fails frees its key, so a retry can run. See the API documentation under Administration → API & webhooks. - Exports protect against spreadsheet formulas. In the CSV exports (audit log, contacts, booking reports,
time off and leave balances, usage), a value that a spreadsheet would run as a formula, such as a name starting
with
=,+,-or@, now starts with an apostrophe, so Excel and Sheets show it as text. Numbers are unchanged, and importing an exported contacts file gives back the original values. The full data export is unchanged: it is a copy for importing into another system. - Exchange and single sign-on addresses must use https. The Exchange Web Services address for calendar and
email sync, and a sign-in provider's authority, must start with
https://, and Exchange must be reachable from the internet. Test connection on Sign-in & SSO now shows a short message instead of the provider's answer. If your Exchange server is only on your own network, contact ONEConsult.NET Ltd. - Roles from single sign-on now follow your identity provider. A role that came from a mapped group or role is removed at the next sign-in once your provider no longer grants it, and the change is in the audit log. Roles granted on the Users page stay, and the last administrator always keeps the Admin role.
BayCheck ONE
- Move to … offers only bays that can really take the truck. When a truck's bay is still occupied, the gate now offers only bays at the same site that are free for the truck's whole slot. Before, a bay that was empty but booked later in the slot could be offered and then refused. A truck can't be moved to another site, on screen or through the API. See Use the gate.
1.46
Platform ONE
- Safer single sign-on. Someone signing in with an identity provider is linked to an existing account only when the provider marks their email address as verified, or when you trust the provider's email addresses with the new Trust this provider's email addresses setting. It's on for Microsoft Entra ID and Google, and off for other providers. Allowed email domains now also applies to existing accounts, and Microsoft Entra ID refuses sign-ins from other directories. See Set up sign-in and single sign-on.
- Guessing and flooding are slowed down. Sign-in, sign-up and password-reset attempts from one network are limited each minute, and at most three password-reset or confirmation emails go to one address an hour. See Set up sign-in and single sign-on.
- An account's address must be proved before it can be shared. When someone signs in with an identity provider to an account whose address was never confirmed, such as a sign-up made while email verification was off, the account's password is removed. Nobody can sign up with another person's address and keep using the account after its owner arrives.
- Single sign-on trusts fewer email addresses. An address the identity provider marks as unverified is never trusted, even for a provider you trust. With Microsoft Entra ID and no directory ID, no account is created for an address Microsoft hasn't confirmed, and the provider form warns about it. See Set up sign-in and single sign-on.
- Small fixes. In Studio, long message and workflow texts make their fields grow again, record tabs have their spacing back, and Connect under Organization sign-in on My profile always opens your organization's sign-in page.
- API keys keep to their limits everywhere. A key limited to some kinds of record is refused any operation its limits don't name. A key for one team or person also sees only their records inside other records, and the API's description says what each operation needs. See Connect other systems with API keys and webhooks.
- Connect your organization account from My profile. People who can't be linked automatically sign in with their password once and select Connect under Organization sign-in. See Manage your profile.
1.45
Platform ONE
- Test and development environments. Enterprise now includes one test and one development environment. With Standard you can add a test environment, and with Professional a test or a development environment. On Professional, a development environment comes with Studio releases, so your changes can move to test and production. Scheduled publishing and several approvers stay in Enterprise. See Plans and features.
1.44
Rolodex ONE
- Your own words everywhere. Contacts, companies, leads and opportunities are called by your words in every page, dialog and message, including the pipeline, qualifying a lead, importing, duplicates and documents.
Projects and shifts
- Your own words everywhere. Projects and shifts are called by your words on the planner, the capacity view, My schedule, shift swaps and rotations, and in their messages.
BayCheck ONE
- Your own words for bookings at the gate, for walk-ins and on the dock board's messages.
1.43
Platform ONE
- Your own words in more places. The words you set in Studio under Labels, such as "patient" for customer or "appointment" for booking, now also appear in the shared pages: the account menu, your profile, calendar and email sync, holidays, locations, branding, staff roles and Studio's email templates, and in messages such as "Customer not found".
BookIt ONE
- Your own words in more places. Bookings, the booking page, My bookings, reports and the messages staff and customers see now use your words for bookings and customers.
1.42
BookIt ONE, Reserve ONE and BayCheck ONE
- Booking rules and resource types in Studio. Notice and limits, approval and reminders, and the kinds of things you book, are now changed in Studio: in a draft, reviewed and published, and moved between your environments in releases. The Business rules page shows them as they are in use, with Change in Studio. A resource type you remove is hidden where it's in use. See Set booking rules.
PTO ONE
- Time off types in Studio. Types of time off, which need approval, and their allowances are now changed in Studio, under Time off rules. A type you remove is hidden where it has been used, so its history stays. See Set up time off types.
1.41
Rolodex ONE
- Sales rules in Studio. Pipelines and their stages, how long disqualified leads are kept and the reasons for disqualifying are now changed in Studio, under Sales rules: in a draft, reviewed and published, and moved between your environments in releases. The Business rules page shows them as they are in use, with Change in Studio. A pipeline removed in a release is switched off, so its opportunities stay where they are. See Set up sales pipelines.
1.40
Platform ONE
- Environment values. Give each environment its own values, such as the address of the system
a workflow calls or the person it tells, under Administration, Environment values.
Workflows use them as
{env.name}. A release carries the name, never the value, so a workflow promoted to production uses production's values. A release that needs a value an environment doesn't have waits there until it's set. See Set environment values.
1.39
Platform ONE
- Choose what happens to a clash. When you send or import a package and the receiving environment changed the same thing, you see each clash with both changes. For each one, keep the environment's change or use the package's. See Move changes between environments.
- Email templates are part of Studio. They're changed in a draft, reviewed and published, and they can go into a release and move between environments. See Write email templates.
- Approving your own change. An administrator can always approve and publish their own Studio change. A designer's change is always approved by an administrator. The setting Whoever submitted a change may approve it is gone.
1.38
Platform ONE
- Promote, share and refresh. Send a Studio package straight to another of your environments: from development to a test environment you choose, from test to production, or to another development environment. Refresh development or test from production or test. Production takes only what passed test. See Move changes between environments.
- Approve a whole release in one decision, with Submit release for review and Approve release on the release's page.
- When the receiving environment changed different things since, both sets of changes are kept; when it changed the same thing, the package goes back to development.
- Production can take its changes only from test, with flagged emergency changes for administrators.
1.37
Platform ONE
- Environments. If your organization has development or test environments as well as production, each one shows a coloured band with its name. Outside production, every email goes to your test address and only agreed test systems are called, so nobody real is contacted.
- Packages. A Studio release has a name, a description and a version that goes up by itself each time it's exported with changes. Exported packages are signed, so another environment can tell they weren't changed on the way, and Studio shows where each live change came from, and when something was changed directly since. See Move changes between environments.
- Package files now end in
.platformone. Files from earlier versions can still be imported. - A record opened from inside another, such as a booking from a time off request, opens on top of it again, instead of closing it.
1.36
Platform ONE
- Labels in Studio: use your organization's own words for what Platform ONE names, such as patients instead of customers, appointments instead of bookings or jobs instead of projects, and give menu items their own names. A word changes everywhere: the menu, page headings, table columns, buttons and messages. Only the words of your products are offered, and changes are reviewed and published like other Studio changes. See Rename words and menu items.
- What you call your customers has moved from the Organization page into Labels in Studio, with the other words.
- Adding a contact, company, lead or project opens it straight away again.
- On the sign-in page, Forgot password? is under the Sign in button.
- On a staff user, the role choices line up.
1.35
Platform ONE
- Records now open full screen, beside the menu and under the top bar, with the menu and top bar still available. Use the view button beside Close to choose a side panel (the list stays in view) or a window instead; Platform ONE remembers each person's choice. On a wide screen, full-screen records set out their fields in two columns. On a phone, records always fill the screen. See Choose how records open.
- Records opened from a list have their own web address: share it, reload the page, or use the browser's Back button to close the record. Previous and next arrows step through the list.
- Long records, such as customers, show their parts as tabs in full screen and in the side panel.
- Platform ONE asks before you leave a record with changes you haven't saved.
- Administrators can choose what Platform ONE calls their customers, for example patients or colleagues, on the Organization page. See Rename words and menu items.
- In lists of people, users, locations, services, and staff and resources, select a name to open it; the Edit and Remove buttons are no longer in the list. Remove is inside the record, and asks "Are you sure you want to remove record" followed by its name before removing it.
- On Staff & resources, time-off notes on a card wrap instead of running into the next card.
- On Projects, the hours still to plan no longer overlap the planned hours.
1.34
Platform ONE
- Published the Platform ONE documentation: the user guide and the administrator guide.
- The Modules page and the menu show the exact version and build you're on.
- Platform updates for security and performance.
BookIt ONE and BayCheck ONE
- On the sign-up page, First name and Last name are now one under the other, like the other fields.