BookYourPTO

Changelog

Stay up to date with the latest changes, improvements, and bug fixes in BookYourPTO.
Latest

v2.0.0

BookYourPTO Intelligence (Beta)

  • An assistant built into BookYourPTO. Ask about leave, expenses, schedules, documents and your team in plain words, from the Assistant link under Home in the sidebar, the panel at the top right of every page, or the full-page view at /assistant. It answers from your organization's own records and can show the answer as a table, a chart, or a CSV or PDF file to download.
  • It does the work, after you approve it. It can book leave, add an expense from a receipt you attach, log time, schedule a week of shifts, approve or reject requests you name, and more. Every change shows a card to confirm first. You can choose how much it may do on its own: Ask first (the default, every change asks), Accept edits (simple additions run, while approvals, sending and deleting still ask), Auto (everything except high-risk changes) or Plan (it only lays out the steps). Deleting, bulk changes and other high-risk actions always ask.
  • Your own permissions, nothing more. It acts as the person using it, so it can see and change only what that person could in the app. Employees see their own records; managers, department heads and administrators see what their role allows.
  • Questions on every plan, actions on Pro, Business and Enterprise. Free includes questions; paid plans can also make changes. Each person has a weekly usage allowance that resets every week, shared across shorter sessions, and higher plans include more.
  • Attachments, skills and memory. Attach images, PDFs, text or CSV files (up to 5 files, 5MB each). Ready-made skills guide common jobs such as turning a receipt into an expense, planning time off, team coverage and approvals triage. It remembers short facts about how you work only when you ask it to, and you can see and delete them under /memory.
  • Chats you can come back to. Chats get short titles, are listed under Recent, and can be searched by what was said. Type / for commands such as /new, /skills, /usage and /export.
  • In your control. Executives and administrators can switch it on or off for the organization, for departments or for individual people in Settings > Intelligence, and see the company's usage there. Each person sees their own usage on the Usage page. It only works with BookYourPTO: questions about anything else are politely refused, and likely misuse is recorded for administrators under Security violations. Conversations are never used to train AI models.
  • Approval cards say exactly what will change. A card for a change to an expense claim names the claim (report number, title, status and total) and, for a single purchase, per diem or mileage row, that row (description, date and amount). Projects and clients are named too. The details are read with your own access, so a card never shows a record you could not open.
  • Changes that cannot be undone always ask, even in Auto. Auto and Accept edits run most changes straight away; deleting, removing, deactivating and other changes that cannot be undone still show the card, and the card now says why.
  • The page behind the assistant updates itself. After the assistant changes something, the page you have open (Home, Expenses, a calendar…) loads its data again on its own, keeping your place, with a short "The page has been updated" note. If you have typed into the page or have a dialog open there, it is left alone and the assistant offers the refresh instead, so nothing you were doing is lost.
  • Documents look like yours. PDFs the assistant makes contain only what it wrote: no product name, no "made with" line, and no organization name or date added above the title (they appeared twice when the document already had them). The footer shows page numbers only, and the file's author is your organization.
  • Word documents. Ask for a Word or editable document and the assistant makes a real .docx (headings, lists, tables, signature blocks) that opens in Word, Google Docs, Pages and LibreOffice, kept on your Files page like PDFs. A conversation, or a single answer, can also be downloaded as Word as well as Markdown (the download menu, or /export word). Word files carry no product stamp either: page numbers only, with your organization as the author.
  • Documents and answers get names and totals right. A document about you now names you in its Employee or Name field (it sometimes used the organization's name), and counts and totals come from the records themselves, the same in the answer and in the file made from it (a summary once said 42 requests and its Word copy 43), with no rows invented for records that have no dates.
  • Send your next question while an answer is still being written. Questions you send mid-answer used to disappear. They now wait above the message box ("Queued — sends when this answer finishes") and are sent one after another, in order, as each answer ends, with any files you attached. Select one to edit it again, or remove it with the X; up to 5 can wait. The queue waits for you behind an approval card, a pause at your usage limit or an answer that did not finish, offering Send now on each question, and carries on by itself once the approval is answered. Queued questions belong to their chat and are kept only in the open page.
  • The usage-limit notice keeps itself current. After a plan upgrade, a reset, or returning to the tab, the assistant re-checks your allowance and clears "You've reached this session's limit" without a page reload (it used to stay until the page was refreshed).
  • Help improve Intelligence.
    • A thumbs-down can say what went wrong: Wrong answer, Wrong record, Didn't do it, Too slow or Other.
    • At moments that matter (a thumbs-down, an action that failed, a cancelled approval, or a question asked again), the assistant may ask whether you would like to share the whole conversation to help improve it. It asks at most once a week, never twice in a conversation, and "Don't ask again" stops it.
    • Settings > Intelligence > Help improve Intelligence controls this for the organization. It is on by default and only an Executive can change it (administrators see it read-only). With it on, a copy of conversations with names and personal details removed is kept to improve Intelligence, and a full conversation only when someone chooses to share it. With it off, nobody is asked and no conversation text is kept for this purpose.
    • Conversations are never used to train an AI model, never sold, and never shared with other organizations. See the updated Privacy Policy.

Bug fixes

  • Shifts accepted a department, project or task from outside the organization. Creating shifts, one at a time or in bulk, now checks each one.
  • Assigning training or choosing goal-setting people no longer skips names silently. Naming someone who is not an active member used to be ignored (and could empty the goal-setting list); the request is now refused with a clear message. A bulk training due date is now stored as the calendar day chosen.
  • Receipt scanning on the backup AI provider works again. It asked for a model the provider had retired, so every scan sent there failed (and the scan failed outright when the main provider was unavailable).
  • The assistant's mode menu is no longer cut off. On the assistant home page it opened upward under the page header and hid "Ask before acting"; it now opens wherever there is room and never grows past the window.
  • Names only link to a profile you can open. With Calendar View visible, opening a colleague's calendar showed their name as a link, and clicking it ended on a "Forbidden" page. The same happened in a profile's Direct Reports section, on the home page's My Team, Probation Reviews and Next 1:1 cards, and on the documents "View profile" button. Each now links only when you are allowed to open that profile (your own, anyone in your scope as a department head, or anyone as an administrator or executive). Otherwise the name is shown without a link. Next 1:1 opens your own 1:1s when you cannot open the other person's profile.
  • Performance review cycle reminders are sent again. Since review cycles gained reminders, the daily job that sends them failed on every run, so department heads, administrators and executives were never told a review cycle was opening or an employee's review anniversary was near. Reminders now go out, in the app and by email, on the milestones each cycle sets (14 and 3 days ahead by default), once per milestone.
  • The AI connector (MCP server) works again across the product. Many assistant actions had stopped matching the app and either failed or did nothing while reporting success. Signing in through the assistant failed straight after a correct password. Approving or rejecting time entries, adding expense line items, per diems and mileage, assigning or sending documents for signature, bulk sending, offboarding an employee, adding dependents, equity grants and commissions, creating project issues and calendar feeds were all refused. Many lists answered "0 found" when there were results. Every assistant action has been checked against the app and corrected, and each one now describes who may use it and why it may be refused.
  • Updating a Slack or Teams integration through the assistant no longer removes its webhook. Changing only which notifications are sent used to clear the saved webhook address.
  • Billing actions through the assistant. "Cancel immediately" cancelled at the end of the period instead, and choosing yearly billing at checkout billed monthly. Both now do what was asked.
  • Connector sessions no longer break when their sign-in expires. An expired sign-in was answered with a server error instead of "sign in again", so the AI client did not refresh it and the connector stopped working until it was reconnected. It now refreshes automatically.
  • Opting out of (or back into) data sharing no longer shows an error, and the choice is recorded.
  • Undoing a data import no longer reports "Rollback failed" after removing the records.
  • Profiles show work schedule history, which was always empty.
  • Historical rows in custom profile tables can be saved again, on the day chosen.
  • Creating a certification type or asset category with an existing name explains that, or restores the archived one, and archived ones are no longer offered for new records.
  • Saving only the notification types for Slack or Teams no longer disconnects the webhook.
  • Deleting a department no longer leaves its teams pointing at it.
  • Time entries inside a finalized or signed timesheet can no longer be approved or rejected, in the app or through the public API, so a signed timesheet always matches its entries. Any still pending there leave the time approvals queue and every pending count (sidebar badge, Home card, mobile app) as soon as the timesheet is finalized: the signed timesheet is the record.
  • Excel timesheet exports are recorded in the audit log, no longer fail when a name contains characters such as "/" or ":" or two people share a name, and open formula-like text as plain text. Holidays and leave always land on the right calendar day, an export with no dates covers the current month in the organization's timezone, and a range over a year is refused with a message. Names beginning with "=" or "+" appear exactly as typed.
  • A time entry's task must belong to its project; changing the project clears a task from the old one.
  • Bulk-deleting time entries respects finalized timesheets.
  • Clearing a schedule week uses the organization's timezone for which shifts it removes.
  • "Today", "this week", "this month" and "this year" in Time Tracking follow the person's timezone, and month and year totals include their last day.
  • Due dates, signature deadlines, expiry dates and training due dates are saved on the day chosen, in every timezone.
  • "Some employees" onboarding tasks are given only to the people chosen, and automatic onboarding falls back to the default assignee when the template's assignee has left.
  • Department heads can open the task list of an onboarding they manage.
  • A meeting can't be added to a paused 1:1, or to one with a deactivated participant.
  • Importing straight from a connected platform is hidden until it is finished: synced rows never reached the preview. Export a file from the platform and upload it instead.
  • Dates in custom profile tabs no longer show the previous day for viewers west of UTC.
  • Organizations at UTC+12 and beyond: employees see the first day of a published schedule week.
  • The schedule week's last day no longer slips across a daylight-saving change when emailing or copying a week.
  • Two-factor settings no longer offer Disable when the organization requires two-factor, and say why. Department heads see Rename, Move and Delete only on documents they sent, and 1:1 edit and delete controls appear only for people who can manage that 1:1.
  • Manual and edited time entries are saved at the time you enter, in the employee's own timezone. Entries added or edited on the timesheet were stored hours off in organizations outside UTC, and each save shifted them again; saving without changing the times now leaves them alone. The API refuses a time without a timezone (INVALID_INSTANT).
  • Booking a morning or afternoon off for a single day counts as half a day, matching the calendar. It was charged as a full day unless both halves were chosen; for a one-day request the ending now follows the start.
  • Project, task and issue dates no longer show a day early.
  • Clients can be deleted from the client page; a client with active projects asks you to archive or complete them first.
  • Travel (mileage) entries can be edited on an expense claim while it is editable.
  • Time Tracking updates right after you clock in or out (This Week, This Month, the activity log), without a reload.
  • 1:1 notifications and reminder emails show the correct meeting date.
  • "View Audit Trail" works on filed documents (those without a signature request); it showed an error. Signing certificates number signers from #1, the audit trail no longer says "created the document" twice, and the signing screen's two progress counters agree.
  • Report PDF exports show the logo again in production.
  • Export previews offer one honestly named "Download CSV (opens in Excel)" button.
  • Success messages appear after adding, editing or deleting leave types, departments and holiday locations, and after sending, assigning or declining a signature request; a failed send of signing emails says so.
  • New organizations no longer see a "not found" error on their first Home load, and the unlock dialog for a locked date says who the lock covers; the expenses status chart adds up.
  • Every delete and other irreversible action asks in the app's own dialog, naming what will be lost, instead of the browser's pop-up. Deleting a shift from the Schedules list view now works (it did nothing), and deleting from a list view asks once instead of twice.
  • Export menus say what they produce: "Export CSV (opens in Excel)" opens a preview, "Download CSV now" downloads at once, and the security log export no longer saves a CSV under an .xlsx name. CSV exports of users, expense claims and security logs keep formula-like values as plain text.
  • 1:1 reminders go out on the right day in every organization's timezone.
  • Adding a holiday location loads the organization's current year, and past holidays follow the organization's calendar.
  • The "Time entries require manager approval" note shows only to people whose entries need approval. Editing a time entry shows whose it is instead of a picker that could not change it.
  • Smaller fixes: meal allowance tiles show cents; the calendar's year arrows have names and are no longer cut off on phones; Home, Notifications, Support, Usage and Calendar have tab titles.
  • Mobile: manual time entries use your own timezone (or your organization's), so hours entered on a phone set to another zone land on the right day and time; booking a morning or afternoon off for one day counts as half a day.
  • Invalid filters, dates, page numbers and timezones across leave, reports, time, schedules, security logs, notifications, documents, training, 1:1s and profile edits now get a clear message instead of a server error.
  • Add and Edit Time Entry showed two forms at once (from an earlier change in this release). In Single day mode and when editing an entry, the Multiple days fields appeared under Clock In and Clock Out; for a person with their own timezone, Multiple days showed no fields at all. Entries were saved correctly; only the form was wrong.
  • The Expenses list showed totals in the Pre-tax column. Tax is part of a purchase's total, so adding the parts again counted it twice; the column, the page totals, sorting and "Download CSV now" now show the amount before tax, and every amount in that CSV is rounded to the cent.
  • "Resend email" on the verification page now says why it failed. When an email cannot be sent to the address, the page shows that message instead of a generic "Please try again" (which could not succeed anyway).

Security

  • HR records could be added to a person in another organization. Adding a compensation entry, bonus, equity grant, commission, education entry, language or visa to an employee checked only that the person doing it was an administrator, not that the employee belonged to their organization. All seven now refuse anyone outside the organization, and a guard test keeps every "add to a person" action checking it.
  • Education and languages are now private HR records. Any employee could read any colleague's education history and languages. They are now visible to the person, administrators and executives, and department heads for their departments, like certifications.
  • Emailing a schedule could reach the whole organization. Choosing a department that matched no one sent the schedule to every scheduled employee, and a department head could email any department. An unmatched department now sends nothing, and department heads can email only their own departments.

A whole-app review of every server endpoint, looking for the same kinds of mistake, found and fixed the following.

Organization boundaries

  • Notes can only be added about people in your own organization. An administrator could add a note about a person in another organization, and that person was emailed about it.
  • QuickBooks employee, vendor and department links accept only people and departments in your own organization; the mapping screens could otherwise show another organization's names.
  • A person's working schedule can be looked up only within your organization, and by department heads only for their departments.
  • Only the person who opened a support request, or their organization's administrators, can attach files to it.
  • Training courses, certifications and locked dates accept only categories, types, people and departments from your own organization.
  • Another organization's records are answered "not found". An expense claim, line item, per diem, mileage entry, receipt, leave decision, cancellation review or user edit naming another organization's record answered 403, which showed the identifier was real elsewhere. It now answers 404, exactly like an identifier that does not exist; a guard test keeps it that way.

Sign-in and sessions

  • Organizations that require single sign-on now refuse password sign-in on the server for the web sign-in page and connected AI clients, not only by hiding the form. The mobile app keeps signing in with email and password, so people can still set or reset a password for it. Nothing changes until SSO is fully set up.
  • SSO sign-in requires an email the identity provider has verified, and an allowed email domain. With SSO on and no domain configured, SSO sign-in is refused instead of accepting any domain.
  • Only executives can add, verify or remove SSO email domains. The Auth0 domain must be a public hostname, and the default department for new SSO users must belong to your organization.
  • A sign-in session can no longer renew itself indefinitely. Re-checking an already verified email returned a fresh session, which survived signing out, password changes and role changes. Verification links now work once and no longer sign you in.
  • If a sign-in session is used from two places at once, which can mean it was stolen, the person is signed out on every device. Two tabs refreshing together are still treated as normal.
  • Connected AI clients: a connector's sign-in can only be renewed by the client it was issued to, and reusing an old, already-replaced connector sign-in signs that person out everywhere, the same protection the web and mobile apps have. Renewing through the connector can no longer turn a short browser session into a longer one, and a brief cache outage no longer stops connectors renewing.
  • Single sign-on fails cleanly with a clear message when the identity provider answers with a redirect or an error, instead of an unexpected error.
  • Email verification can no longer be skipped. Signing up with an address that cannot receive mail (a made-up domain, for example) used to mark the account verified when the verification email failed to send. A failed send now leaves the account unverified, on the verify screen with Resend and "try a different email", and Resend reports a failed send instead of claiming it went out. Only an installation with no email settings at all skips verification.
  • Two-factor authentication can't be turned off in an organization that requires it.
  • Receipt files and downloads apply the same account checks as the rest of the app (deactivated accounts, role changes, outstanding security steps).
  • Slack, Teams and QuickBooks settings use a person's current role, so a demoted administrator loses access straight away.
  • A phone's notification registration belongs only to the person who signed in on it most recently, so a shared phone no longer receives the previous person's notifications.

Who sees what

  • Department heads and documents: they can open, download, view the audit trail of, rename or delete only documents they sent (plus their own), and can no longer add themselves as a signer. Attaching a document to an onboarding task needs permission to open it.
  • Signers on a document with several signers no longer receive another signer's signature image.
  • A person demoted to employee is no longer an approver. The approver flag stayed on after a demotion (usually an organization's founder who handed over the executive role), which kept their view of the whole organization's pending leave, reasons and private leave types included, and let them approve anyone's leave. Changing someone's role to Employee now clears it (audited), and employees left with it are cleared. Department heads, administrators and executives approve as before.
  • Colleagues' clock-in locations are shown only to department heads (for their people), administrators and executives. Everyone still sees who is clocked in.
  • Company Directory "Admins only" now applies in the app as well as the public API: employees see only themselves in the people list and profiles, and a department head sees full details only for people in their departments. Schedules and timesheets still show names and photos.
  • Calendar subscriptions for the whole organization, direct reports or approvals stop working when the owner's role no longer allows them.
  • On a colleague's onboarding checklist, an employee sees only the tasks assigned to them.
  • Peer and direct-report feedback stays anonymous whatever capitalisation was used.
  • Editing a 1:1 series needs the same rights as setting one up; participants still add meetings and notes.
  • Department heads can no longer edit or delete open shifts filed to other departments in bulk.
  • Custom-domain branding can be changed only by executives, and its privacy, terms and support links must be https addresses. Viewing a custom domain needs administrator access.
  • Organization settings sent to the browser no longer include internal feature switches.

Lists that could widen to everyone

  • Copying a schedule week with no employees selected no longer copies everyone, and its email goes only to the people who got new shifts.
  • A bulk-send row with no email address is rejected; it could reach an unintended employee.
  • An unknown "required for" value on a training course is refused instead of assigning the course to everyone.

Exports and records

  • Downloads of audit logs, sign-in logs, the platform user list, QuickBooks sync history, leave reports, timesheet PDFs, expense report spreadsheets and geofence violations are recorded in the audit log, and text in these files can no longer run as a spreadsheet formula.
  • Billing checkout and portal always return people to BookYourPTO or the organization's own domain.
  • Password setup emails are no longer sent to deactivated people.
  • Import errors no longer show internal details or another platform's raw responses.
  • Mileage distance lookups are rate limited per person.
  • Support tickets can be opened, and files added to them, only by administrators and executives of the organization. The support page shows "not found" to everyone else.
  • Password reset emails always link to your organization's own address, never to whatever address a request claimed to come from.
  • Sign-in through single sign-on never follows a redirect from the identity provider to another address.
  • The app's start-up data no longer includes internal organization switches (such as which people are blocked from the assistant); every member received them before.
  • The public demo no longer sends support tickets or schedule emails.
  • Protection against runaway assistant usage. Each person can have one answer running at a time and send at most 12 questions a minute and 60 an hour, so a burst of parallel requests can no longer slip past the allowance before it is counted.
  • Fewer false "session hijack" alerts. Two tabs (or a network retry) refreshing a sign-in at the same moment was recorded as a HIGH session-hijack violation, often several rows at once. A refresh that loses a race within 60 seconds is now treated as normal; real reuse of an older rotated token is still flagged, once per token.
  • Violation details never hold a token. "Unauthorized access" rows stored the full address, including receipt preview tokens. The address is now recorded without its query string, with secret path segments masked, like the access log. Existing rows are left as they were.
  • Erasing a person's data now includes the assistant. A privacy data-deletion request also deletes their assistant chats, memories and stored files.
  • The assistant flags misuse. Requests for system secrets, other organizations' data, instruction overrides and injection payloads are recorded as "AI Assistant Misuse" violations.
  • Asset categories and certification types could be deactivated across organizations. An administrator who knew the identifier of another organization's asset category or certification type could deactivate it. Both actions are now limited to the administrator's own organization, and an identifier from another organization is answered exactly like one that does not exist.
  • The connector no longer fetches receipt images from a web address. Receipt analysis and upload through the assistant take the file itself. Fetching an address from the server would have let a caller reach addresses inside the hosting network.

Privacy

  • Conversations from before this release are never used to improve Intelligence. Only conversations held after the update, while Help improve Intelligence is on, can be reviewed.
  • Assistant usage signals are kept for no longer than 24 months. A weekly job clears older ones; the conversations themselves are unaffected.
  • The assistant no longer receives the email address of a connected Google calendar account, or the calendar provider's own error text, when it checks calendar sync status.
  • Privacy Policy, Terms of Service and Subprocessors updated to describe BookYourPTO Intelligence in full and the Help improve Intelligence program, with retention limits (usage signals and de-identified or shared conversations: 24 months; analysis copies: deleted within 30 days).

Public API

  • Time entries: GET /api/v1/time-entries?approval_status=PENDING leaves out entries inside a finalized or signed timesheet, matching the approvals queue; approving or rejecting one returns CONFLICT.
  • Leave approvals follow the app's approver rule. POST /api/v1/leaves/{id}/approve and /reject run the same shared service as the app, so a token owned by an employee who only carries the approver flag can decide only leaves assigned to them (403 otherwise).
  • Expense line items include the extra tax. Expense report detail and expense_report.* webhook payloads now carry other_tax and other_tax_label on each line item (additive); total_tax includes it.

Improvements

  • Calendar days are cleaner. Days with leave, holidays, locks or celebrations show just their round coloured icon, as the dashboard does, instead of a bordered square around it.
  • Open shifts can be claimed only in a published week and before they start.
  • A department head filtering a report or violations list by a department they don't manage is told so, rather than shown all their departments under that label.
  • Purchases can carry a named extra tax. Alongside GST, PST, HST, QST and gratuity, a purchase can include one more tax such as a liquor tax, city tax or tourism levy: choose Liquor tax, City tax or Tourism levy, or type your own name. It is included in the purchase total, the report's tax total, Excel exports and QuickBooks. Receipt scanning now reads a separately printed liquor, city or tourism tax into it instead of folding it into sales tax.
  • Expense report numbers work with BookYourPTO Intelligence. Asking about "EXP-2026-0001" now finds that report directly instead of failing and searching for it.
  • Business includes 500 documents a month. The Business plan's document allowance (files and signing requests together) goes from 100 to 500 a month. Existing Business organizations move to the new allowance automatically; an organization with a custom allowance keeps it.
  • BookYourPTO Intelligence suggests what your role can do. The assistant page and panel no longer offer approvals to people who cannot approve, or company-wide reports, sent-document reminders and onboarding status to employees. Suggestions follow the same rules as the sidebar.
  • Assistant sits under Home in the sidebar. Home is now a group like Documents: the chevron folds it, and Assistant is indented below it with an icon the same size as its neighbours.
  • A reached usage limit shows before you type. The assistant page now checks your usage when it opens and when you come back to the tab, so the limit notice appears above the message box straight away instead of only after you ask something. The notice also lines up with the box.
  • A question asked at your usage limit is paused, not lost. If you ask BookYourPTO Intelligence a question after reaching your usage limit, your question is now saved and shown as paused, with when your usage resets. Once it does, press Continue to get your answer. A change waiting for your approval is kept too, and you can still cancel it at any time.
  • Announcements come in three designs, with their own colours. Besides the centred card with a picture, an announcement can be a split panel (a coloured panel beside the text, with the short lines shown as a checked feature list and an optional second button such as "Learn more"), or a small card in the corner that leaves the page usable and needs no dimmed background. Each announcement can set its accent colour and, for the centred card and split panel, its gradient; without them it uses the organization's theme colour as before. The picture's small card now names the feature rather than repeating the full title.
  • Assistant chats get short, clear names. A new chat used to be named after the first 64 characters of the first message, so a question that included a link showed the link in the chat list. A new chat is now named straight away from the message with links, record ids and email addresses taken out ("delete my claim"), and once the first answer is written it gets a short title that says what the chat is about ("Delete draft expense report"), in the language the question was asked in. The new name appears in the header and the chat list without a reload. A chat you renamed keeps your name. Naming a chat counts toward your assistant allowance like any other answer, and is skipped when the allowance is used up.
  • Search your past chats by what was said. The Search box on the assistant page, and a new search box under Recent in the assistant panel, now look through what you and the assistant wrote in your chats, not only their titles, and match your words wherever they appear rather than the exact phrase ("compared leave by department" finds "Compare leave taken by department"). Results show a short excerpt with the words you searched for highlighted, newest first, up to 20. Only your own chats are searched.
  • Ask the assistant to find an earlier chat. "Find my chat about my leave balance" or "where did we talk about my expense claim?" now finds the conversation and answers with a link that opens it. This works in every mode, including Plan, and on every plan, and only ever looks at your own chats.
  • Faster, cheaper, more reliable receipt scanning. Receipts are read by a main AI provider, and a second provider takes over when the first fails, including when its balance runs out. Both use newer models that read every field correctly in our tests at a fraction of the previous cost.
  • The assistant has its own place in the sidebar. "Assistant" sits under Home and opens the full assistant page with your earlier chats. It appears only while you can use it: it is hidden when the assistant is switched off for you, your department or your organization, or paused.
  • Schedule a whole team in one request. Ask the assistant to schedule several people across several days and it does it in one step. It first checks the week, says whether it is a draft or already published and what is scheduled, and always asks before changing a published week.
  • The assistant follows your organization's modules. When Time Tracking & Projects or Expenses is switched off, the assistant no longer offers anything from that module, the same way the sidebar hides it.
  • Attach files to a question. Add images, PDFs or CSV files to a message (up to five, 5 MB each and 10 MB in all) and the assistant reads them, for example a receipt it turns into an expense line.
  • No more double confirmation in the assistant. When a request is clear, the assistant acts according to the mode instead of asking "shall I go ahead?" first: in Ask mode it shows the approval card straight away, in Accept edits and Auto it makes the change (high-risk actions still show a card). It still asks a short question when something is missing, such as which dates.
  • Settings > Intelligence. Executives and administrators choose who can use BookYourPTO Intelligence: on for everyone by default, switched off by department or by person, with people switched back on inside a switched-off department. A Company usage tab shows each person's tokens today, this week and in total.
  • Announcements. Product news can appear once as a window after sign-in, always after the welcome steps and tours. Only the newest is shown, and closing it means it does not come back.
  • Charts can be downloaded as PNG or SVG. Charts keep up to eight series and use round axis steps. Tables in the assistant keep readable columns and scroll sideways only when they need to.
  • Clearer assistant outages. If the assistant is paused or its AI provider is unavailable, people see that it is temporarily unavailable, and that everything else works as usual.
  • Assistant plans. Pro can now take actions with the assistant, not only Business and Enterprise. Each person gets a weekly allowance (Free 600,000 tokens, Pro 1,900,000, Business 3,100,000, Enterprise 9,400,000) and a share of it per session (a seventh), so it lasts the whole week. A session starts with your first question and lasts five hours. Enterprise allowances can be set per organization. Usage shows Current session and This week.
  • Settings → API and the API reference load in their own shape. Instead of a few grey bars, the page shows its tabs, token rows and side cards (and the reference its navigation and endpoint blocks) while it loads.
  • The assistant can do more. New actions include asking to cancel approved leave and reviewing those requests, submitting, approving and finalizing timesheets, uploading receipts, editing per diems and mileage, viewing a document template's versions and archiving or restoring templates, reminding signers, reviewing expiring documents, editing and deleting performance cycles and recording assessments, reading and setting custom profile fields, correcting compensation, job history and other employment records, per-person holiday overrides, and test sends for email, Slack and Teams settings. Two actions that could never work were removed.
  • Connect an AI assistant in one command. npx @bookyourpto/wizard mcp add finds the supported AI coding tools and editors on your computer and adds the BookYourPTO connector to the ones you pick, and shows the in-app steps for desktop AI apps. It stores no password or key: your browser opens to sign in the first time the assistant connects. mcp status and mcp remove show and undo it.
  • BookYourPTO Intelligence, the in-app assistant (beta). Ask HR questions and take actions from a panel on every page, or full page at /assistant. It works only inside BookYourPTO, with your own permissions. Choose how it acts: ask before every change, accept edits, auto (high-risk changes still ask) or plan (read-only). Type / for commands (/new, /compact, /memory, /remember, /mode, /export, /usage and more). It remembers facts you ask it to, which you can see and delete, and keeps long chats short automatically. Attach, paste or drag in a receipt, a note or a screenshot and it reads it — a receipt is attached to the expense it creates; everything you attach is kept on a Files page. It draws charts and makes CSV and PDF files from your data. Reloading the page mid-answer picks the answer back up (or offers Retry if it was cut off), and a change waiting for your confirmation comes back. Skills (/skills) walk through common jobs: a receipt into an expense, planning time off, approvals, timesheets, a self-review, an HR letter. Settings it cannot change, such as passwords or two-factor, get a link to the right page.

v1.1.6

Bug fixes

  • Public holidays, leave and locked dates appeared a day late on the Dashboard. For anyone whose computer is ahead of UTC (India, Europe, Australia and beyond), the Dashboard drew every public holiday, leave day and locked date one day later than the Calendar page did, so Remembrance Day on Wednesday 11 November appeared on Thursday the 12th. Leave on the last day of the visible range sometimes did not appear at all. The Dashboard now shows each of them on the day it falls, in every timezone, matching the Calendar page.
  • Schedules and timesheets showed public holidays a day early. For organizations west of UTC, which covers every organization in Canada and the United States, the Schedules grid, the timesheet grid and the timesheet export placed each public holiday on the day before it. A half-day leave at the start or end of a longer leave also showed as a full day. Both now appear on the right day.
  • Due dates and trip dates shown a day early. Document signature due dates (in the documents list, the document page, the signing page and Action Required), expense report trip dates, per diem dates, and the dates in the leave, project and expense report exports showed the day before the stored date for anyone west of UTC. They now show the date that was entered. Action Required's "Due today", "Due tomorrow" and "Overdue" now count whole days on your own calendar, so a document due tomorrow no longer reads "Overdue" in the evening.
  • Training marked overdue on the evening before it was due. A course was marked Overdue, and the employee and their manager were notified, as soon as its due date began in UTC — the previous evening anywhere in the Americas. A course is now overdue once its due day has ended where the employee is, and the profile's Training and Onboarding tabs use the same rule.
  • Daylight saving changes. Around a clock change (1 November in Canada and the United States, 25 October in Europe):
    • An automatically generated shift on the day of the change is no longer deleted and recreated each time the schedule is opened.
    • The mobile app's schedule week no longer shifts by a day after stepping across the change.
    • Leave ranges, the leave request day count and the earliest date offered for a new request no longer drop or repeat a day across the change, and the same applies to per diem days in the web and mobile expense forms.
  • "Today" in forms and reports. Date fields that start on today (receipts, documents, training records, benefits) and the expense and leave report presets now use today in your timezone, not in UTC, which was tomorrow's date in the evening in North America.
  • Leave over New Year. For someone whose holidays follow a different country than their organization's, a leave from late December into January now counts that country's New Year's Day as a holiday.
  • Locked dates across the year boundary. A lock starting on 31 December was not shown on the Calendar for anyone ahead of UTC; it now is.

Security

  • Dependency updates. Nuxt 4.6.3, Nodemailer 10.3 and patched versions of DOMPurify, Vite, undici, follow-redirects, fast-uri and launch-editor close 31 of the 33 open Dependabot alerts, including the three rated critical. simple-git, which carried five of them, is no longer installed at all. The two that remain have no release their dependents accept and are not reachable from a request: node-forge's signature-verification advisory (the app only creates keys and certificates with it) and zod 3, used by the docs content module at build time.

Improvements

  • Dashboard performance. The Dashboard matches holidays, leave and locked dates against each day once per change of data instead of re-reading every record for every day of every row on each redraw, which keeps large teams responsive.
  • Safer timesheet and schedule CSV exports. Both exports now go through the shared CSV writer, so a value containing a quote or starting with = can no longer break a row or run as a spreadsheet formula.

v1.1.5

Bug fixes

  • Deactivated employees were offered as people to send work to. A person who had left stayed on the Users page marked Inactive, as intended, but also kept appearing in the Documents Bulk Send recipient list and in fourteen other pickers: template signers, document assignment, training assignment and bulk assignment, new shifts, new time entries, lock dates, a department's manager, the timesheet approver, onboarding contacts and task assignees, and geofence assignments. They are no longer offered anywhere work is given to someone, and every request that names one anyway is refused, in the app and through the public API. Their history is untouched: past records, reports and exports still show them. A setting that already names someone who has left shows them labelled "(inactive)" so it can be changed, and filing a leaver's final paperwork into their folder still works.
  • Saved defaults that pointed at a leaver. An onboarding task list whose saved assignee has left now gives that task to the default assignee; an expense whose submitter's manager has left goes to the active administrators for approval; a timesheet whose named approver has left is signed by the employee alone instead of waiting on someone who cannot sign. Copying a week of shifts no longer copies shifts for people who have left.
  • Templates could not be deleted after a bulk send. Deleting any template that had ever been used in a Bulk Send failed with "Failed to delete template". It now deletes, and the bulk send's history, the documents it created and their signatures are all kept.
  • Leave types could not be deleted when they had balances but no requests. The delete failed with "Failed to delete leave type"; the unused balances are now removed with the type.
  • Template cards said "0 sends" for templates sent through Bulk Send. Bulk sends now count each document they create, and existing templates were brought up to date.
  • Bulk Send listed only the first 20 templates. It now lists up to 100.

Security

  • Three places accepted a person from another organization. Adding a certification to an employee, setting a project issue's assignee or reporter, and an administrator assigning shifts (single or bulk) did not check that the person belonged to the caller's organization. A certification's type, and a geofence assignment's department or project, were not checked either. All of them now refuse an id from outside the organization.

Public API

  • Assigning training (POST /users/{id}/training, unless recording it as completed), issuing an asset (POST /users/{id}/assets), setting manager_id (PATCH /users/{id}) and creating a time entry for another person (POST /time-entries, for work after their last day) now answer VALIDATION_FAILED when the person is deactivated, as booking leave already did. Re-sending a manager who has since left, unchanged, is still accepted.

Improvements

  • Upload a new version of a template. A document that needs a change after it was sent is updated in place: open the template, choose Upload new version, and the amended file becomes the next version under the same name, keeping its settings, departments, signer roles and signing fields. Documents already sent keep the version they were sent with. Onboarding checklists move to the new version for anyone not yet issued the document. Every version stays viewable, with who uploaded it and how many documents were sent from it.
  • Template names are unique. Creating or renaming a template to a name another active template already has is refused, and the create page offers to upload the file as a new version of that template instead. Archived templates and older versions do not hold a name.
  • Old versions and archived templates are never offered for sending. Bulk Send, Send and onboarding task lists offer only the current version; a page left open on an old version is told to refresh.
  • Redesigned Templates page. Templates are listed in a table with search, category and type filters, sortable columns, version and upload date on every row, and one actions menu (send, edit fields, rename, upload new version, archive, restore, delete). The template page now shows its name with a rename button, its version history, and runs full width. Bulk Send's template list shows each template's version and upload date.
  • Birthday greetings arrive at 9:30. Each person's birthday greeting is now sent at 9:30 in the morning, local time — the timezone on their profile, or the organization's timezone when they have not set one. It used to arrive at about 9:40. In the few regions whose clocks are offset by a half or quarter hour from UTC (such as India, Newfoundland or Nepal), it arrives at 10:00 or 10:15 instead.

v1.1.4

Mobile app

  • BookYourPTO is now on Android. The mobile app, already available for iPhone, can now be installed from Google Play (com.anhourtec.bookyourpto). Android users sign in with their existing BookYourPTO account. Download links for both platforms are on bookyourpto.com/mobile-app.

Public API

  • A REST API and webhooks. Organizations can now connect their own systems, scripts and integration tools (Zapier, Make, Workato and the like) to BookYourPTO. The REST API reads and writes people, departments, teams, leave, leave balances, public holidays and locked dates, time entries and timesheets, projects and clients, shifts, expense reports, documents, onboarding, and each person's training, certifications, assets, benefits, compensation, custom fields and goals. Webhooks send an event to your own HTTPS address when something happens, so an integration does not have to keep asking. In all, the API has 67 operations across 17 resource groups, 39 scopes and 24 webhook event types.
  • Who can use it. The API comes with every paid plan — Pro, Business and Enterprise — and not the Free plan. It is off by default: an executive turns it on under Settings → API, and a new organization starts with no tokens and no webhook endpoints. Downgrading to Free, turning the API off, or a subscription falling past due stops every token and every webhook at once.
  • Tokens act as the person who owns them. A token can never do more than its owner could do in the app. It sees the same people, departments and records, through the same rules the app uses: a department head's token sees their departments, an employee's token sees what that employee sees, private leave is redacted the same way, and the time tracking, expenses and one-on-ones switches apply. The owner's role and status are checked again on every request, so a token stops working the moment its owner is deactivated, offboarded or moved to a role that may not hold tokens.
  • Managing tokens. Settings → API lists every token, with who owns it, when it expires and when it was last used. Each token has a required expiry (the organization sets the maximum, 90 days unless changed, up to a year), an optional list of IP addresses or ranges it may be used from, and is shown once when it is created. Rotating a token can keep the old one working for 0, 1, 24 or 72 hours while your systems switch over. Owners are emailed 7 days before a token expires. Revoking is immediate, and every change is recorded in the audit log. Administrators and executives can create tokens for people ranked below them and transfer ownership; by default only administrators and executives may create tokens, and the organization can allow other roles, who then see a Personal API Tokens page with their own tokens only.
  • Scopes and API roles. Each token is limited to the scopes it is given, such as leaves:read or time_entries:approve, and never beyond what its owner's role allows. Personal details, government ids, compensation and document files are separate scopes that only administrators or executives can hold, and every read of them is recorded. An API role is a named set of scopes — start from a template such as Leave sync, Time and payroll export or Read-only directory — and editing the role updates every token that uses it.
  • Writes follow the app's rules. Booking, cancelling, approving and rejecting leave, editing and approving time entries, deciding expense reports, and adding or updating people, departments, teams, training and assets all go through the same steps as the app: the same checks, notifications, calendar sync and audit entries. Every change made through the API is marked in the audit log as made through the API, with the token that made it. Through the API no one approves their own leave, time entry or expense report, whatever their role.
  • Rate limits. Each token may make 120 requests a minute (with short bursts of up to 20 a second), each organization 600 a minute, and every response says how much of the allowance is left. Downloading a document's file counts as 10 requests.
  • An interactive reference. /developers/api documents every endpoint, scope, error and webhook event, with example requests and responses, and lets you send a test request to your own organization. The OpenAPI document and a Postman collection can be downloaded from it. Organizations with the White-Label add-on see their own brand throughout the reference, the console and the downloads.
  • Webhooks. Administrators and executives add endpoints on the Webhooks tab of Settings → API, or through the API. Choose the events to receive — leave requested, approved, rejected, cancelled, updated or with a cancellation requested; people added, updated, deactivated or reactivated; departments created, updated or deleted; time entries submitted, approved or rejected; timesheets finalized; expense reports submitted, approved, rejected or paid; documents signed or declined — or every event the endpoint's owner may receive.
    • An endpoint receives only what its owner could read through the API. An event about a record the owner cannot see is not sent, and a webhook never carries personal details, government ids, compensation, locations or document contents.
    • Every delivery is signed with the endpoint's secret using the open Standard Webhooks scheme, which has verification libraries for most languages. The secret is shown once; rotating it keeps the old one valid for 24 hours, and deliveries in that window carry both signatures.
    • A delivery that fails is retried over about 45 hours, up to 8 attempts. An endpoint that has failed for 72 hours is switched off and its owner and the organization's executives are emailed. Send test event, a delivery log for each endpoint and Redeliver are on the same tab.
    • Each organization can have up to 10 endpoints. Webhook addresses must be public https:// addresses.
  • Existing document webhooks move to the new system. Organizations that had a document signing webhook set up by our team will find it on the Webhooks tab, paused until an administrator confirms it. It now uses the signing scheme above, with retries and a delivery log. The signature format has changed, so update the receiving system to verify the new webhook-signature header before resuming the endpoint; the old X-Webhook-Signature header is no longer sent.
  • The public demo shows the API console but refuses every change made through the API.
  • A webhook's signing secret is shown once. Repeating POST /webhooks with the same Idempotency-Key returns the endpoint with signing_secret: null and a note in meta; the secret is never kept for replays.
  • user.updated is sent only when a field in the User object changes. A change to employment or personal details alone no longer sends an event.

Security

These fixes come from a security review of the whole server carried out before the API was built.

  • The two-factor step could be skipped. A sign-in waiting at the two-factor step could be used as a full session. A session is now issued only once sign-in is complete, and the two-factor step has a credential of its own that nothing else accepts. Existing sessions carry on.
  • Leave status could be changed without going through approval. Editing a leave request could also change its status, which let some users approve requests — including their own — outside the approval flow. Status now changes only through approve, reject and cancel, with their usual checks.
  • Time entries and timesheets could be approved by the person who submitted them. Nobody now approves their own time entries or timesheets — one at a time, in bulk, or from the approval queue — and the approval queue and its badge no longer count your own.
  • Refund requests were visible beyond the organization's administrators. They are now listed only to administrators and executives, and only for their own organization.
  • Custom profile fields and tables were readable by colleagues. An employee now sees only their own values, and only on tabs shown to their role. Administrators and executives still see everyone's. Values can no longer be saved against a person in another organization.
  • Data deletion could reach outside the organization. Erasing a person's data now finds them only inside the organization of whoever asked.
  • Employee notes marked for managers are now shown to a department head only for people in the departments they manage.
  • Organization backups and user updates returned more than they should. The backup no longer includes the outgoing mail password or anyone's sign-in secrets, and saving a person's profile no longer sends back sign-in related fields.
  • Expense claims and projects accepted references from elsewhere. A claim's department, payee, project and receipts must now belong to your organization and your claim, and a project's details, board, tasks, issues and comments follow the same department rule as the projects list.
  • Connecting a calendar is tied to the person who started it. The Google Calendar and Outlook connection now checks that it finishes for the same person who began it.
  • An account that has to finish setting up — verify its email, change its password or set up two-factor — can reach only the pages needed to do that.
  • Outgoing mail servers and Teams webhooks must be public. An organization's own SMTP server must be on a public address, checked when saved and again before each connection; if it later points somewhere internal, mail goes out through our own mail server instead, and the stored password is not sent. Teams webhook addresses must be on Microsoft's own domains.
  • AI assistant connections. The consent screen for connecting an AI assistant now names the site you will be returned to and warns that the application is not verified by us.
  • Schedules are generated at most a year either side of today, whatever range is asked for.

Bug fixes

  • Two people deciding the same request at once. Approving or rejecting a leave request, a cancellation request or a time entry, cancelling a leave, and signing or declining a document now refuse a second, simultaneous decision (409) instead of recording it twice, with a second notification and webhook event. Approving a time entry that is already approved is refused too.
  • Leave could be booked for a deactivated or offboarded person. It is now refused, in the app and through the API.
  • A webhook delivery cancelled while it was being sent (endpoint paused or removed) could be marked delivered or queued again afterwards. It now stays cancelled.
  • Document signing events were emitted by two paths. The retired document webhook dispatcher has been removed; each signature or decline sends exactly one event.
  • A department head could learn whether another department's leave was already decided. Approving or rejecting a request from outside their departments answered "already approved" rather than refusing. The department is now checked first, so they learn nothing about the request.
  • An address with an unusual # part could break navigation. Following a link whose part after # was not a valid page anchor raised an error instead of opening the page. It now opens the page and simply does not scroll.

Improvements

  • API access ends when a person leaves. Offboarding or erasing a person revokes every API token they own or hold, in the same step that deactivates them, and switches off webhook endpoints they own. Reactivating them later does not bring any of it back; new tokens must be issued. Moving someone to a role that may not hold tokens revokes any token secrets they hold for other people.
  • Editing an approved time entry sends it back for approval. When someone other than an administrator or executive changes the hours, break, project, task or billing of an approved or rejected entry, it returns to pending for an approver to look at again. Description, notes and tags can still be edited freely.
  • Only administrators and executives set an hourly rate on a time entry.
  • Time entries in a finalized timesheet are frozen. Once a period's timesheet is finalized or signed, nobody — whatever their role — changes its entries' hours, rate or billing, or moves an entry into that period.
  • SSO settings are executive-only. Administrators can no longer change the identity provider or the role new SSO users receive, and SSO sign-up never creates anyone above Department Head.
  • Public holidays and holiday overrides are managed by administrators. Adding or removing the organization's holiday locations, and setting a person's holiday overrides, is now limited to administrators and executives.
  • A colleague's personal holidays stay with the people allowed to see them. Someone's holiday overrides and personal holiday calendar are shown to them, to administrators and executives, and to a department head whose departments include them. Everyone else, on the calendar and the Dashboard, sees the organization's holidays for that person.
  • Profile edits in the audit log name the fields, not personal values. The audit entry for a profile change lists every field submitted, and records the value only for organizational settings such as role, department and manager — not addresses, phone numbers, dates of birth or identification numbers.

v1.1.3

Bug fixes

  • The audit log recorded the wrong IP address. Depending on which part of the product wrote the entry, the IP column held one of three things. Every document action — viewing, signing, downloading, sending — recorded 172.18.0.6, an internal address belonging to our own infrastructure. Sign-ins, leave changes and settings changes recorded two addresses joined by a comma: the device and the network edge it passed through. Only a handful of entries recorded the device alone. Every entry now records one address: the public address of the device that made the request. This includes the IP on the e-signature audit trail and signing certificate.
  • The recorded IP could be set by the person using the app. Where two addresses were stored, the first was taken from a header the browser sends, so anyone could put any address into the audit entries for their own actions, including two-factor and password-policy changes. The address is now read only from hops we operate or trust, and a header from anywhere else is ignored.
  • Security violations could be written into another organization. The endpoint the browser calls when it detects a tampered session took the organization and the user from the request itself, so any signed-in user could add violation records — naming anyone — to any organization's security log. They now come from the signed-in session only, and a browser can report only the kinds of tampering a browser can actually see.
  • Connection errors could show any text. When connecting QuickBooks, Google Calendar or Outlook failed, the settings page displayed whatever the link said, so a crafted link could show an administrator any sentence as if it came from the product. These pages now show only their own messages, and the provider's error text is no longer put in the address bar.
  • Personal data in the server log. Each load of the Dashboard wrote every employee's name and leave balance to the application log, along with step-by-step detail of leave calculations. The log now records identifiers and counts, never names, balances, emails or document details.
  • The Time report opened empty from May onwards. It defaulted to "this year", and the time entry list serves at most 120 days at a time, so once the year was past 120 days old every visit showed "No time entries found". It now opens on the last 30 days, offers All time, 30 days and This quarter, and a longer custom range says so instead of showing an empty table.
  • "View Project" in the Projects report led to a page that does not exist. It now opens the project.
  • Report dates were a day early west of UTC. Leave start and end dates, expense dates and the date range shown on PDF exports were printed in the browser's timezone, so a leave starting 17 August read 16 August in Vancouver. They now show the stored day, as the calendar and approvals do.
  • Quick date ranges picked the wrong day. "30 days", "This year", "This quarter", each report's default range and the Leave Distribution card worked from the UTC day, or from local midnight read back in UTC, so in the evening west of UTC — or any time east of it — they could start or end a day out, and "This year" could start on 31 December. They now follow the viewer's own timezone, or the organization's when they have not set one.
  • Confirmations and error messages were never shown. Hundreds of places in the app raise a message — "Leave request approved", "Could not save", "You can only create leave requests for yourself" — but nothing drew them, so every one was silent. They now appear in the corner of the screen, errors stay a little longer, and hovering a message keeps it open.
  • Report CSV files could break or run formulas. A reason or note containing a double quote split its row, and a value starting with =, +, - or @ was run as a formula when the file was opened in a spreadsheet. Every report CSV, including the export preview grids, now keeps such values as plain text.
  • An employee opening a report address briefly loaded it. The page sent its report requests (which the server refused) before redirecting. It now redirects without loading anything.
  • "Export in Excel" on Projects led to a page that does not exist. It now opens the projects export preview, whose Back link returns to Projects.
  • Export preview filters did nothing. The column filters on the leave, time, expense, project and scheduling export previews asked for a filter only the paid edition of the grid provides, so the grid dropped them. They now filter.
  • The export preview kept working after you left it. It went on resizing a grid that no longer existed, filling the console with warnings.
  • Employees could open the report export previews by address. The leave, time, expense and scheduling previews now send an employee to the dashboard before loading anything, as the reports themselves do. What the server returned was always limited to their own records.
  • Trip dates on an expense claim were a day early west of UTC. A claim's date range was read in the browser's timezone, so a trip from 6 to 9 April read 5 to 8 April in Vancouver. It now shows the stored days.
  • A receipt dropped onto the scan area was ignored if it was a PDF. Picking the same PDF with the file browser worked. Dropping now accepts every format the file browser does: JPEG, PNG, GIF, WebP and PDF.
  • "View all" on a claim's Overview left you looking at blank space. The links sit below the fold, and the shorter tab they opened kept the old scroll position. The tab bar is now brought back into view, and a press on the tab bar itself still keeps the page still.
  • Opening a claim at a particular tab showed the Overview first. A link to a claim's Purchases, Per Diem, Travel or Receipts tab drew the Overview for a moment before switching. It now opens straight on the tab asked for.
  • The approver had no photo. The approver on a claim was shown with initials even when they had a profile photo. Their photo now appears, as the submitter's does.
  • "You" marked the wrong recipient on a document. On a document's page, the badge went to whoever's copy was open rather than the person viewing it, so an administrator opening Noah's copy saw "Noah Brown · You". It now marks the signed-in person.
  • People still showed as initials in several places. A profile's Manager card and Direct Reports (both in the side panel and on the Job tab), its 1:1s and goal comments, department managers on the Departments settings page, project task assignees and the Billing breakdown, document recipients in the list and on the document page, and the recipient search when adding a document all drew initials even for people with a photo. They now show the photo. Where the circle's colour meant something (a recipient's signed, declined or pending state), it is kept as a ring around the photo.
  • Document names showed "&" and "'". Document titles and descriptions, template names, signing messages and decline reasons were saved with symbols turned into HTML codes, so "Smith & Co - O'Brien Offer" read as "Smith & Co - O'Brien Offer" in email subjects and plain-text emails, notifications in the app and on phones, Slack, the signing certificate and audit-trail PDFs, and the document lists on the web and in the mobile app. Renaming a document added another layer each time. Text is now saved as typed, and existing documents and notifications are corrected.
  • The account-deletion email's plain-text version showed HTML codes for names or organization names containing an ampersand or quotes. It now reads as written.
  • A "$&" in a title or message could break an email. Text containing it was read as a replacement instruction when the email was assembled. Every email now inserts its content exactly.
  • Names and titles in some emails were read as page markup. Onboarding and offboarding, training, certification, visa, carry-over, domain-expiry, one-on-one and review-cycle emails put names, course and task titles, task descriptions, agenda items and cycle names into the email without escaping them, so text containing markup — a link, say — became live markup in a message sent from our domain. Those values are now shown exactly as typed.
  • Document list exports kept spreadsheet formulas live. A title beginning with "=" was run as a formula when the CSV was opened. The Documents list, Action Required and the document export preview now keep such values as plain text, as the report exports do.
  • Overdue signing reminders showed raw code. The due date in an overdue document reminder email read <span style="color:#dc2626;font-weight:600;">Thursday, October 8, 2026 (OVERDUE)</span> instead of the date in red. It now shows the date, marked overdue, in red. Due-soon and follow-up reminders were not affected.
  • A document could be seen before it reached you. When a document was sent for signature in order — management signing a bonus notice or salary letter first, then the person it is about — that person's home page listed it under "Waiting on someone else", with a link, before anyone ahead of them had signed. The document's file and its signing layout could also be opened by that link, because being the person a document is about let them through. A signer whose turn has not come now sees nothing of the document — not on the home page, not in their documents or the expiring list, not in the download-everything archive, not by link — until it reaches them. Administrators and executives, who can see every document, still see it.
  • A department head could tick off a colleague's onboarding task. On a new hire's checklist, the department head could mark complete a task assigned to someone else — "Alarm Code", say, assigned to HR — recording the work as done by somebody who never did it. A task assigned to a person is now theirs to complete (administrators and executives can still complete any task); the department head completes only the unassigned tasks and their own, whatever else the request changes at the same time. The button no longer appears for anyone else, who instead sees who the task belongs to.
  • A new joiner with no Reports To sat at the top of the org chart. They now appear under the head of their department until Reports To is filled in — the Department Head set for the department in Settings, or, when none is set there, the one person in the department with the Department Head role. Every Reports To line is still drawn first, so the head of the organization stays at the top even when they belong to a department run by one of their own reports.
  • Anyone could read anyone's equipment list by address. The assets on a profile were returned to any signed-in member of the organization who asked for them. They are now visible to the person themselves, their department head, and administrators and executives.
  • A department head by role was not the department's manager. The Department Head role (on a person) and the department's Manager (Settings → Departments) were set in different places and never linked, so a department could have a head by role and no manager — and every email and reminder addressed to "the department head" (leave, expenses, time entries, onboarding, probation) went to nobody. The first Department Head added to a department with no manager now becomes its manager, and a one-off update fills existing departments that have no manager and exactly one Department Head. An existing manager is never replaced automatically.
  • Department heads could add users through the API. The Add User button was only ever shown to administrators and executives, but the API also accepted department heads — at any non-admin role, in any department. Only administrators and executives can add users now.
  • A user could be filed under another organization's department. The department sent with Add User or Edit User, and the manager sent with Edit User, were not checked; both must now belong to your organization.
  • Every department head was told about every time entry. Time-entry notifications went to all department heads in the organization, whoever the employee was. They now go to the heads of the employee's own department, plus administrators and executives.
  • Department heads could reach people outside their departments in a few places. Each is now limited to the departments they act for:
    • the clock-in status of any employee (/time-tracking);
    • re-sending the signing emails of any document;
    • schedules: copying a hand-picked list of anyone's shifts, reassigning a shift to someone outside their departments, editing or deleting another department's open shifts, and — for a head with no department — reading or editing anyone's schedule;
    • the monthly birthday email, which sent a head with no department the whole organization's birthdays;
    • the Dashboard under the "department only" privacy setting, which showed such a head everyone.
  • Pending approvals could show an approver their own request. The cached list was shared between approvers who see the same departments, although each list leaves out the viewer's own requests; it is now cached per viewer.
  • A leave balance or booking could name another organization's employee. The person was looked up by id alone; it must now be in your organization.
  • Leftover department managers. Under the old rule a manager was always a member of the department they managed, and nothing cleared the Manager field when they later moved. Because a Manager now extends a department head's access, every leftover — a manager who is no longer a member of that department — is cleared once on upgrade, and the department falls to its single Department Head if it has one. Check Settings → Departments afterwards and set any manager you want. A department's manager must now be an administrator, executive or department head.

Improvements

  • A birthday greeting. On their birthday, each person receives a short greeting — in the app and, on the mobile app, as a push notification — once their own local time reaches 9:00, so everyone is greeted on their own morning. It uses the timezone on their profile, or the organization's when they have not set one, is sent once a year, and is signed by BookYourPTO or by the organization's own name under white-label branding. It can be turned off under Settings → Notifications.
  • One structured server log. Every line is a single JSON record with a level, a request id, the route, and the signed-in user and organization ids, so one request's activity can be found and followed. Each response returns its request id in an X-Request-Id header, so a support conversation can quote it. A mistyped password is no longer logged as a crash with a stack trace, health checks no longer fill the log, and the level and format are set with LOG_LEVEL and LOG_FORMAT without a redeploy.
  • Tokens never reach the access log. Query strings are not logged, and the public signing, verification and calendar-feed links are masked.
  • nginx records the real visitor. Behind Cloudflare, nginx now resolves the visitor's address from Cloudflare's own header, accepted only from Cloudflare's published ranges.
  • The public demo explains itself. Settings pages whose changes the demo refuses now carry a "Disabled in demo mode" label. Receipt scanning stays available on the demo, limited to five scans per visitor per day. Connecting a personal calendar to the shared demo login is refused.
  • Provider errors stay out of the log. QuickBooks explains a failed sync in words that can name employees and vendors. Administrators still see that explanation in the sync history; the server log records only the error code and status.
  • Details at a glance in Reports. Clicking a row in the Leave, Time or Scheduling report — or choosing View Details — opens a read-only panel on the right with everything about that leave request, time entry or shift, and a link to where it is reviewed or edited. Previously "View Details" left the report for the calendar, and "View Entry" / "View Schedule" opened the general timesheets or schedule page with no trace of the row clicked.
  • Pages no longer jump. Switching tabs or views (an expense's tabs, a profile's tabs, the documents sections, report views) keeps the page where it is instead of jumping to the top or shaking as content loads. Pages that loaded in stages — Reports, Expenses, Home, Calendar, Documents, Add a document — now draw in place instead of shifting down as each part arrives.
  • Paging returns you to the list. Pressing Next or Previous at the bottom of a list (People, approvals queues, reports, expenses, documents, settings logs and more) brings the new page into view instead of leaving you at the bottom of it. Page buttons are now labelled for screen readers.
  • Phone layouts. Report filters sit in tidy equal-width cells on a phone, and the Documents section buttons scroll sideways rather than wrapping onto a second line.
  • A redesigned expense claim page. The claim opens on a single header card: the title and claim number, a large status stamp with one line saying where the claim stands ("Awaiting ...", "Approved by ... · date", "Paid on date by payment method"), the claim's details (submitter, dates, purpose, departure and return times, duration, currency) in one panel, and the balance due — or total paid — beside the actions. Less common actions (Edit Details, Export Excel, Cancel Claim, Delete Claim) sit under More, and the buttons match the size used in toolbars across the app.
    • Tabs. Overview, Purchases, Per Diem, Travel and Receipts are shown as a sliding pill bar, the same control used on Security & compliance and Add a document, with the number of items on each tab.
    • Overview. A strip of section totals (purchases, per diem, travel), each opening its tab; the claim's details beside its activity; and the most recent items, with View all.
    • Purchases, Per Diem and Travel are tables laid out like the expense claims list, with a totals row. Per Diem shows one row per day with breakfast, lunch, dinner and incidentals in their own columns. Each row's actions are in the same ... menu as the claims list.
    • Item details open in a panel on the right instead of a dialog in the middle of the screen, with an Edit button for anyone who may change the item.
    • Receipts (administrators and executives) open as a table by default, with a preview of each receipt on hover or keyboard focus. The thumbnail grid is one click away, and the choice is remembered.
    • Loading. While a claim loads, the page shows a placeholder shaped like the claim and the tab being opened — a table for Purchases, Per Diem and Travel, a grid for Receipts — so nothing jumps when it arrives.
    • The page now uses the full width of the window.
  • Choose the columns on the expense claims list. A Columns menu beside Date Range shows or hides any column in the table. Expense No. is hidden by default; every other column is shown. The choice is remembered in the browser across refreshes, Reset to default restores it, and the last visible column cannot be hidden. A search still finds a claim by its number while the column is hidden.
  • Choose exactly who holds a company card. Company card claims used to be open either to administrators and executives only, or to everyone. With Allow All Roles off, Settings → Expenses now has a Card Holders list: add the specific people who carry a card, and they — alongside administrators and executives — can create company card claims while everyone else sees only reimbursement claims. Only active people in the organization can be added, removing someone stops new company card claims without touching ones already filed, and every change to the list is recorded in the audit log. The mobile app follows the same list.
  • Company Card as a payment method. Recording a company card claim used to offer only payout methods (Direct Deposit, Cheque, Added to Payroll), so there was nothing true to choose. Company Card is now an option, and it is selected for you on a company card claim — in the claim's Mark as Recorded dialog, in Process Claims when every selected claim is on the card, and from the mobile app. The reference is optional and suggests a statement date or the card's last four digits. A recorded claim is stamped Recorded rather than Paid, its total reads Total Recorded, and payment methods read as words ("by Direct Deposit") instead of codes ("by DIRECT_DEPOSIT").
  • Add a document: the help button sits beside the wording. The (?) explaining each mode now follows the last word of the description rather than the end of the longest one.
  • Health checks you can rely on. The status URL monitors use, https://app.bookyourpto.com/api/health, is unchanged, but it now answers only {"status":"ok"} or {"status":"unavailable"} with a matching 200 or 503, is never cached, and no longer names the services behind it. It is served from a cached check, so calling it cannot put load on the database, and it reports unavailable while the server is restarting during a release rather than claiming to be healthy.
  • Releases are traceable and reversible. Every release runs an image tagged with the exact commit it was built from, the release confirms the server is running that commit before it finishes, and any earlier release can be restored in one step from GitHub Actions (Rollback production).
  • Scheduled reminders are watched. A reminder or digest job that fails is now recorded as a failure, marks its container unhealthy, and can alert through a Better Stack heartbeat — previously a job could fail every hour for weeks unnoticed.
  • Department heads manage their team's equipment and training. On the profile of someone in their own department, a department head can now add, edit and remove assets, and record, complete, remove or dismiss training — before, both tabs showed them nothing they could act on. Their own record stays with an administrator, and defining training courses for the organization remains an administrator setting. Recording a training under a new name adds it as an optional one-time course, so it appears only for the people who hold it.
  • More than one Department Head per department. Adding a Department Head to a department that already has a manager is allowed, and the Add User and Edit User forms say who the manager is before you save: the new person gets department-head access, and the manager keeps the department's emails and reminders.
  • One person can manage several departments. A department's Manager (Settings → Departments) can now be someone who already manages another department — a director over Software and IT Operations, or a CEO who also runs a small team. Choosing them no longer removes them from the department they already managed or moves them out of their own department; the Manager list shows what each person already manages. A Department Head's access — approvals, people, onboarding, assets, training, documents, schedules, reports — now covers their own department and every department they manage. Each request still reaches each person once, however many departments or roles connect them to it.
  • Administrators and executives choose which requests reach them. Leave, expense and time-entry requests have always gone to every administrator and executive. Each can now choose in Settings → Notifications between every request in the organization (the default) and only requests routed to them — from people or departments they manage, or anything nobody else would be told about. The organization can set the default. Every request still appears in the approval queues.

v1.1.2

Highlights

Home — the page you land on after signing in

Signing in used to drop you on the Dashboard, a calendar grid built for planning team coverage. It answers "who is off when" well and almost nothing else, so anything waiting on you personally lived behind a sidebar entry you had to think to visit.

Home is now the landing page. It gathers what needs you, your own records, and — for people who manage or administer — their team and the organization. The Dashboard is unchanged and still in the sidebar; nothing was taken out of it.

What appears depends on your role, on whether anyone reports to you, and on which modules the organization has switched on:

CardWho sees it
Action Required — documents awaiting your signature, assessments you owe somebody, onboarding tasks and training past their date, expired certificationsEveryone. Cannot be switched off
Waiting on You — leave, expense and time requests routed to youAnyone requests are routed to
Time Off — your balances and your next booked leaveEveryone
Today's Hours — hours logged today and whether you are clocked inWhen time tracking is on
Next 1:1 — who you next speak to, and whenEveryone
My Stuff — goals, training, certifications, benefits and equipmentEveryone
Who's Out — who is away today, plus upcoming public holidays on your own calendarEveryone
Celebrations — birthdays and work anniversaries over the next two weeksEveryone
What's Happening — recent updates about your requests and documentsEveryone
Probation Reviews — reviews falling in the next two weeksThe employee, their manager, their department head, administrators and executives
My Team — your people, who is away, and when you next speak to eachAnyone with reports, by org chart rather than by role
Onboarding — onboarding and offboarding still runningAdministrators, executives, and department heads for their own department
Headcount, Review Cycles, Needs AttentionAdministrators and executives

Every row links to the page that shows exactly what it counts, so a count and the page behind it cannot disagree.

Arrange the board yourself

Customise turns the board into the editor. Each card gains a grip and a × on its corners, and an Add cards tray appears along the bottom. Drag a card to move it and the rest close up around it; arrow keys move the focused card too, so the board can be arranged without a mouse. Nothing is saved until you select Save, and Cancel puts it back.

The tray is not only the cards you have removed. There is a library of optional cards that start switched off, so Home does not open with twenty at once:

  • Company Holidays — the next public holidays on your own calendar.
  • Workforce Mix — headcount by division, work location or employment type.
  • Length of Service — how long people have been with the organization.
  • Profile Completeness — records missing a start date, department, job title, date of birth or mobile number, the fields leave accrual, approval routing and reminders depend on.

The last three are for administrators and executives. Each tile shows the card's own icon, so the tray says what you are about to add. Your layout is stored on your account rather than in the browser, so it follows you to another device, and a card added to the product later appears next to the cards it belongs with rather than at the bottom of a board you already arranged.

Switching a card off changes only what you see. It grants no access, and every endpoint behind a card still checks permission for itself.

Nothing on the Dashboard is missing from Home

Everything the Dashboard surfaces now has a home on the new page: upcoming absences for the next fortnight, upcoming public holidays resolved per person rather than per organization, and probation reviews. Probation visibility follows the same rule the Dashboard uses — self, their manager, their department head, administrators and executives — and that rule now lives in one place both pages read rather than being written out twice.

The org chart follows Reports To

The org chart was drawn from roles, not from the reporting structure. Department heads were handed to administrators round-robin and administrators to executives the same way, so the lines it drew were invented: the third person in a list reported to the first administrator purely because of their index. Anyone reading it as a reporting structure was being misled, and the Reports To field people had carefully filled in was ignored.

It is now built from Reports To and from nothing else:

  • An executive is no longer automatically at the top. If an executive reports to somebody — a founder, a board, a parent company — they appear beneath them. Role now affects only the order the top-level people are listed in.
  • Anyone who reports to nobody is a top-level person, so a chart can have several.
  • Somebody whose manager is deactivated, somebody recorded as their own manager, and a reporting loop each surface at the top rather than vanishing, so the record that needs fixing is visible.

Export on the chart offers a PNG of the chart as drawn, the same image as a PDF, and a .csv shaped for Visio, for Lucidchart, or unformatted for a spreadsheet. The files are built from the same Reports To field, so a download and the chart always agree.

Who can download is set separately from who can browse, under Download Access in Company Directory settings. It defaults to all employees. Somebody who cannot view the chart can never download it, whichever option is chosen — export can be narrower than viewing but never wider.


Improvements

  • The New menu — starts the things you can start: a time off request, an expense report, a time entry, an employee, a signature request, a report. Entries appear only for actions you have permission to complete, and each opens the form rather than merely landing you on the page.
  • "Other departments: Hidden" is honoured — with that setting on, Who's Out and Celebrations are limited to a non-administrator's own department, matching the Dashboard. Administrators and executives are exempt, as the setting says.
  • Private leave types read as "Private" to anyone not entitled to the detail, through the same helper the calendar and the digest emails use.
  • Who's Out sends only what it draws — a name, a date range and a leave type. The reason somebody gave for being off, their notes and any approver comment stay on the server.
  • Onboarding and offboarding runs follow the existing rule — administrators, executives, and a department head for their own department. Having somebody report to you is not enough: that a colleague is being offboarded is not something their reporting line should learn from a card.
  • Compensation and demographic breakdowns were considered and left out. Pay figures do not belong on a landing page, and a demographic split over a small team identifies individuals.
  • Balance visibility follows the organization setting — the Time Off card respects the calendar balance-display choice in General settings, so an organization that hides the sick bucket does not have it reappear on Home.
  • Deep links into create forms — ?new=1 on the calendar, expenses and users pages opens the create form on arrival and then clears itself from the URL, so a refresh or a shared link does not reopen it.
  • One landing route — where a signed-in session begins is now a single constant rather than a literal repeated across eight files, so a password sign-in, a Google sign-in, email verification and the end of first-run setup cannot land people in different places. Permission-denied redirects deliberately still go to the Dashboard: where a session starts and where somebody is bounced to are different decisions.
  • A guided tour for Home, replayable from Settings → Guided Tours.
  • Expenses and Documents cards. My Expenses shows your own claims by where they have got to — drafts, awaiting approval, approved but unpaid, sent back — with what the organization still owes you, and appears only when the expenses module is switched on. My Documents shows what is waiting on your signature, what is expiring, and what is waiting on somebody ahead of you in a signing order. Both link straight to the filtered list.
  • The first-run setup checklist has moved to Home. It was on the Dashboard, which is no longer where a signed-in session lands, so an administrator who had just created an organization had to navigate away from their landing page to find the one thing asking them to finish setting it up. It still shows only to administrators and executives, and still disappears once dismissed or completed.
  • Four more cards for the Home tray. Leave Balance gives the full picture the calendar sidebar shows — allowance, carry-over, used and remaining per bucket, with a bar for each. Deductible Leave and Non-deductible Leave split the per-type breakdown into two cards, because "what has my allowance gone on" and "what have I taken that costs me nothing" are different questions. Leave Balance follows the organization's Calendar Balance Display setting, so a bucket hidden on the calendar stays hidden here; the two breakdown cards list exactly what the calendar's Deductible and Non-deductible lists show.
  • Organization Time, for anyone whose own timezone differs from the organization's: both clocks side by side with how far apart they are right now, computed from the actual instant so it stays right across daylight saving. It is not offered at all when the two match — a second clock showing the same time is noise.
  • Home respects the Time Tracking & Projects switch. With the module off, Today's Hours no longer appears and cannot be added from the tray, and the approvals card drops its Time entries row and leaves those requests out of its total. The page now reads the organization's switch directly rather than inferring it from whether a clock request happened to succeed.
  • Download Access — a new Company Directory setting controlling who can export the org chart, independent of who can browse it. An export is a roster in a file: it leaves the product, outlives the session, and forwards like any other attachment.
  • Employee # is now an optional column on the People list, switched off by default and offered to administrators and executives. It used to be on for everyone and blank for everyone: the page reads the directory view of each person, which carried the employee number for nobody, so the column took width from the name and job title beside it and showed a dash. The directory view now carries the number for those two roles, which is what makes the column work at all. Employee numbers remain searchable for everyone, and still appear on the profile.
  • Home names what it counts. The My Expenses and My Documents cards used to give a status and a number — "Awaiting approval: 1" — and leave you to open the list to find out which. Each row now names the most recent reports or documents under it, each opening the record itself, with "and N more" when there are others. A document waiting on your signature opens straight into signing.
  • Who's Out says who. The Coming up list read "1 person away" against each day. It now lists the people whose time off begins that day, with their photo and the type of leave, drawn the same way as the people out today. Private leave types still read as "Private" to anyone not entitled to the detail, and nothing beyond a name, a date and a leave type leaves the server.
  • Work anniversaries name the organization. Celebrations read "2 years with the team"; it now reads "2 years with" followed by the organization's name, falling back to "the team" only when the organization has no name set.

Bug fixes

  • A failed load printed the server's error. When a database query failed, that meant the full column list of the User table — every field name, including the sensitive ones — rendered on the landing page in place of an explanation. Home now shows one neutral line and writes the real failure to the console, and the three endpoints behind it replace any unexpected error with a clean refusal before it leaves the server. Deliberate refusals (not signed in, not permitted) still say what they mean.
  • A department head with no department could see probation data for every employee who also had no department, because the two empty values matched each other. Both sides must now be set for the department rule to apply.
  • Celebrations could never show a photo. Birthdays and work anniversaries drew a cake or a medal where the person's face belongs, and the query behind the card fetched neither the photo nor the person's id, so no amount of styling could have fixed it. The card now shows profile photos, keeping the colour that distinguishes a birthday from an anniversary as a ring and moving the glyph to a corner badge. People without a photo still show their initials.
  • Cards were invisible in dark mode — they were painted with the page background. They now use the same card surface and border treatment as the calendar and profile pages.
  • The board collapsed into a single column while editing. The corner controls were positioned to overhang each card, and a control that overflows its column makes the browser abandon column balancing for the whole board. Cards now keep an identical layout whether or not you are editing.
  • A heading repeated the card beneath it. The board was split by section headings, one reading My Team directly above a card whose own header also read My Team, and one announcing the organization's name to the only person who already knew it. The board is now one continuous run of cards, flowing in columns so a short card sits under a tall one instead of leaving a gap.
  • Three cards could render as an empty box — a header and a border with nothing in them — when the section they summarised had no entries. They are now left out until they have something to say. Action Required still says so when you are clear, which is the point of that card.
  • The org chart invented reporting lines — see the highlight above. It is now built from the Reports To field rather than from roles.
  • The org chart could not be exported at all. It now downloads as a PNG, a PDF or one of three CSV shapes.
  • Everyone could see everyone's work anniversary. The dashboard sent each colleague's hire date to every viewer, so the whole organization saw the whole organization's anniversaries — and a department head saw into departments they have no part in. The daily and weekly digests mailed them just as widely. A work anniversary is derived from the hire date, which is employment information: it reveals tenure, relative seniority and who is new.
    It is now limited to the employee themselves, their manager, their department head and administrators and executives, on the dashboard, on Home and in both digests. Birthdays are unchanged — they carry no employment information and the year is never sent.
  • Security advisories cleared in axios, @grpc/grpc-js, devalue and dompurify. npm audit reports no vulnerabilities.
  • The greeting and the date came from different clocks. "Good afternoon" was read from the browser while the date beside it was resolved in the viewer's own timezone, so somebody whose profile says Asia/Calcutta reading from Vancouver could be greeted for an afternoon that, by the date in the same sentence, had already ended. Both now use the viewer's timezone.
  • The monthly anniversary email ignored its own rule. It narrowed to a department only when the recipient was a department head with a department assigned; a head who had not been given one yet fell through the condition and was mailed every anniversary in the organization. It now uses the same rule as the dashboard, Home and the digests, and so also reaches a head's direct reports outside their department, which it previously missed.
  • An onboarding task assigned to you opened your own profile. Action Required linked every onboarding task to your own Onboarding tab, but a task assigned to you is usually part of somebody else's onboarding and lives on their profile — so the link opened an empty tab. The card now lists one row per person, named, opening the Onboarding or Offboarding tab on their profile, which is where the onboarding notifications already pointed.
  • Time Off disagreed with the calendar. The card read each leave type's default allowance and ignored the person's own allowance and anything carried over, so somebody with 15 days plus 5 carried and 20 used saw "-10, 10 over allowance" on Home and 0 remaining on their calendar. It now shows the Annual and Sick balances the calendar shows, from the same figures.
  • My Documents counted a different set from the page it links to. "N in total" counted every signature request ever sent to you, while All documents opens your folder, which lists the documents filed to you. The two now share one definition of what a folder holds, so the number in the header is the number of documents you find when you follow the link.
  • Non-deductible Leave on Home was always empty. The card looked for non-deductible types among the deductible ones, where by definition there are none, so it said "No non-deductible leave yet" to everybody. It now lists the same types and days as the calendar's Non-deductible leave panel.
  • Deductible Leave on Home left out some leave. A type that draws down a balance without an allowance of its own — Sick Leave - Paid, typically — was dropped, so the card could read 20 days where the calendar read 22. It was also narrowed by the Calendar Balance Display setting, which the calendar's own list does not apply, so an organization showing only the annual balance lost its sick leave from the card. It now lists every deductible type with days taken, in the calendar's order, with each type's own icon, and shows a capped non-deductible type as "6 / 5 days" as the calendar does.

v1.1.1

Review cycles that actually run, 1:1s with a time and a calendar entry, and a clear answer to who sets performance up

Performance has been rebuilt around a simple split: a review cycle says when reviews fall due and who they cover, a 1:1 is the conversation itself, and the two can be linked so a review is something worked towards rather than an event that arrives.

The largest change is that review cycles now do something. A cycle was a name and a pair of dates: the scope section on the form was never saved, so a department-wide cycle came out covering everyone, and every cycle ever created was stuck in Draft because nothing in the product could open it. Cycles now run on either a shared window or each employee's own hire anniversary, cover everyone or one department or a chosen list, and send reminders to the people responsible for holding the review.

1:1s gained a time, a duration and a place in the participants' real calendars, and a 1:1 arranged by an administrator now pairs the right two people — previously it paired the administrator with whoever's profile they were standing on.

Alongside those: performance is now something an organization runs for its people rather than something people set up for themselves, destructive actions ask before they act, and several dates that shifted a day west of UTC have been fixed.

Review cycles

  • A cycle can follow each employee's hire date — Annual meant two different things depending on who set it up: a company-wide window, or a review on each person's own anniversary. One pair of date columns could not express the second at all. A cycle now chooses between specific dates — one window for everyone in scope — and employee hire date, measured from each person's own start date with no shared window.
  • A hire-date cycle is not only the one-year mark — It says how far after the start date the review falls and whether it recurs: every year on the anniversary, once N months in, or every N months. Without that, a cycle named "3 Months Probation" would have reminded on the employee's first anniversary. A 29 February start is reviewed on 28 February in years that have no 29th, and a 31st is held to the last day of a shorter month rather than spilling into the next one.
    This does not replace the probation review on a profile, which keeps its own period, its extension date and its own reminders.
  • The Type field is gone — Annual, Semi-annual, Quarterly, Probation and Custom were a label no code ever read. It implied a schedule it did not set: "Probation" connected to none of the probation machinery, and "Custom" offered nothing to customise. The schedule now says what the cycle is, and the name says what to call it.
  • The scope you choose is the scope that is saved — The form had department and employee pickers and the endpoint discarded every one of those fields, so an administrator could configure a department-wide cycle, watch it save, and get a row covering the whole company. There was no column to record a department in. Scope is now stored, the department is checked against the caller's own organization, and the list shows how many people each cycle currently covers, so a department that has been emptied does not read the same as one with thirty people in it.
  • A new cycle is running, not stuck in Draft — The create endpoint ignored the status entirely, so every cycle fell through to Draft, and no control anywhere could move it out. A cycle is now created Active, and Status is a switch on the form: Active sends reminders, Draft sends nothing.
  • "Completed" is gone, and "Ended" is worked out from the dates — Completed was a third state that no code ever set and no administrator remembered to. Whether a review is finished is a fact about one person's assessment, not about the cycle. A cycle whose end date has passed now reads as Ended without anyone marking it, and sends nothing further.
  • The question-set picker has been removed — It stored a preference that nothing ever read.

Reminders

  • Reviews are now chased at all — A cycle creates no forms and assigns no assessors, so without a reminder it was a row nobody ever heard about. A daily job now sends them, and it is scheduled in both deployment files in the same change — every reminder endpoint in this product had previously been written, tested and merged while no scheduler ever invoked it.
  • Two reminders by default, and as many as you want — 14 days ahead, when there is still time to arrange something, and 3 days ahead, when it has to be done. One reminder is either too early to act on or too late to prepare for. Administrators can choose 30 days, a week, a day, the day itself, or any other number, up to six per cycle.
  • Setting a cycle up late still produces one timely reminder — Configuring a hire-date cycle two days before somebody's anniversary means both the 14-day and 3-day marks have already passed. Sending nothing would lose the reminder entirely, and sending both would deliver two emails at once, one of them claiming the review is a fortnight away. Only the most recent milestone that has come due is sent, and it counts the days from the real dates.
  • Reminders reach the people who have to act — The employee's department head, plus executives and administrators. Where a department has no head, the employee's manager is reminded instead, so two people are not each left assuming the other owns it. The employee is not reminded about their own review; anyone matching several of these receives one email rather than one per role.
  • 1:1 reminders go out a week ahead, the day before, and on the day — A single reminder the evening before is too late to prepare for and too late to move.

1:1 meetings

  • A 1:1 has a time and a duration — Previously only a date, which meant nothing could be put in a calendar. The time is a wall-clock time in the organization's timezone, so a recurring 1:1 stays at the same hour across a daylight-saving change. Thirty minutes by default, changeable.
  • The meeting appears in Google Calendar and Outlook — One event with both people invited as attendees, so it can be accepted or declined like any other invitation, rather than two disconnected copies that cannot be declined at all. Cancelling a meeting, or deleting the series, removes the invitation from the calendars it reached — the cancellation email already said it had.
  • A 1:1 arranged for somebody pairs the right two people — The series was always built as "whoever is signed in" and the person selected. An administrator standing on an employee's profile is arranging a 1:1 for that employee, not with them, so every 1:1 set up on somebody's behalf paired the administrator with the employee and left out the manager who was meant to hold it. Left on the default, the other participant is now the employee's department head, or their manager if the department has no head.
  • Everyone with a stake is told — Both attendees, whoever arranged it, and the employee's manager. It previously notified only "the other participant", so one attendee received nothing and the arranger received nothing either.
  • A 1:1 can say which review it is preparing for — Choosing a running cycle marks the conversation as preparation for that review, and the list shows which one. A review conversation happens once, so choosing a cycle makes the meeting a single occurrence rather than a series.
  • The list says when the next one is — Rows named a person and a cadence and left the obvious question unanswered. They now read as a date and a time, with the end time too, since a calendar entry without a finish cannot be checked for clashes.
  • A 1:1 is visible to the people with a reason to see it — Its two participants, administrators and executives, the employee's manager, and the head of their department. Private notes stay visible only to whoever wrote them.

Seeing your own schedule

  • A profile now says when the next review is due — A review cycle records no assessment until one is written, so nothing about it reached the person it covered: an administrator could set up a cycle across the whole company and every profile still read "Not in a review cycle". The schedule existed only in Settings and in the reminder emails leadership received.
    The Reviews tab now opens with Coming up — the cycles covering that person and the date each one falls due, worked out from their own start date for a hire-date cycle or from the window for a fixed one. Recorded assessments follow underneath.
    Only running cycles appear, and only where the scope covers the person. A closed window, a one-off milestone that has passed, and anyone with no start date on file are left out rather than shown as overdue.

Recording a review

  • A review can be marked complete — The Coming up list said when a review was due and offered nothing to do about it. Opening one now records that it happened, who recorded it and when. Reopening clears that stamp, so the record never claims a completion that was undone.
  • Notes, with three levels of visibility — A note on a review says who may read it, named by the roles the product actually has: Employee and above, Department Head and above, or Administrator and Executive only. Each level is readable by everyone above it, and the author always sees their own. Hovering a level spells the roles out in full.
    Administrator and Executive only is how something is kept from a department head as well as from the employee. A department head writes at the first two levels for their own department, and cannot write a note their own leadership could not read.
    Visibility is stored as a level rather than a list of people, so it stays correct when somebody changes department or is promoted — a note written for "managers" is readable by whoever heads that person's department today.
  • A Review mode on the upload page — A third way to send, beside Upload to folder and Send for signature. It asks in the order the work happens: the review cycle, the document, the people who sign, and then which of them is being reviewed. The document is then openable from that person's Performance tab instead of being hunted for in the documents list.
    The first attempt put a single picker inside the Recipients panel listing every recipient crossed with every review they had — "Aiden Ramirez — FY26 Annual Review — Aug 24, 2026" and five more lines like it. That list grows multiplicatively, it put the review after the people it depends on, and the part that identifies the document, the cycle, was the part repeated rather than the part chosen. A review is a cycle plus a person, so those are now two separate questions and there is no combined list at all.
    Only cycles that are running are offered, and every review the person is scheduled for counts — a cycle's dates are derived, so an active cycle covering somebody is a real review with nothing stored against it yet. Offering only already-recorded ones left the list empty for almost everybody. The record is created as the document is sent. A cycle that does not cover the chosen person says so in words rather than going blank.
  • The employee owns the review document, whoever signs first — A review form is routinely countersigned by the department head and then the employee. The document used to belong to whoever was added as the first recipient, so listing the manager first put the form on the manager's profile and then refused the upload outright, because the review belongs to the employee. Whose review it is and who signs in what order are now separate questions: the employee owns it either way, and the signing order is yours to set as on any other document.
    With a single recipient there is nothing to decide and the answer fills itself in. Adding a second clears it rather than leaving the first person marked — which is precisely how a manager would otherwise end up recorded as the subject of their own report's review.
  • A review exists only once somebody acts on it — Dates are derived from the cycle, so there is nothing to store until a review is completed, noted or has a document attached. Creating that record is idempotent on the cycle, the person and the date, so two people acting at once get one review rather than two.

What an employee can see of their own performance

  • The Performance tab is on your own profile — Your goals, the 1:1s you attend and the reviews you are the subject of were all gated to administrators, executives and department heads, so an employee could not see a goal set for them or when their own review falls due. The tab is now on your own profile, read-only: every control that writes stays gated, and notes and comments are still filtered to what was shared with you.
    Nothing was unlocked on the server to do this. Every read already allowed your own record — only the tab was in the way.
  • An unfinished assessment is no longer readable by its subject — An assessment is created before anybody writes in it, and the assessor fills in the rating and comments before submitting. The endpoint applied no status filter, so the person being assessed could read a half-written candid rating of themselves while its author was still drafting it. Only completed assessments are returned to their subject now; the assessor still sees their own work in progress.
  • Peer and upward feedback is no longer attributed to its author — A PEER or DIRECT_REPORT assessment came back to its subject with the assessor's name and id attached, which defeats the confidentiality those two kinds of review are collected under. The content is still shown; the author is not. A manager assessment keeps its attribution, which is the point of one.
    Both were pre-existing, and both became reachable through ordinary use the moment the Performance tab opened to employees — so they are fixed in the same change rather than left for the next one to find.
  • Goal comments carry a visibility level — The same three levels as review notes, so a manager can note something about a goal without it being readable by the person the goal belongs to. The control, the wording and the levels are identical to the ones on a review, on the principle that a comment about somebody is the same kind of writing wherever it is written.
    The default is Employee and above, where a review note defaults to Department Head and above. A review note is written about somebody; a goal comment is a conversation with them on a goal whose progress they own. Existing comments are all Employee and above, so no thread that was readable yesterday stopped being readable.
  • A department head can read the discussion on their own department's goals — They could already read the goals themselves, but the comments on them were restricted to administrators and executives, which is the same inconsistency the write side had.

Documents

  • Word documents and images preview instead of refusing — Filing accepts PDF, DOC, DOCX, PNG, JPG and JPEG, and the preview handled only the first of those. Everything else got "Only PDF documents are supported for preview", which reads as a fault rather than a limitation, above a Try Again button that could never succeed. A .docx now renders as pages in the browser, and an image renders as an image.
    The rendering happens in the browser, so the file never goes to a conversion service. The older binary .doc format has no browser renderer, so it says so by name and offers the download, rather than being lumped in with everything else.
  • The same click behaves the same everywhere — Opening a document from an employee's folder used to fetch the bytes and hand them to the browser, which downloaded a Word file instead of showing it, while the same document opened from the documents list previewed. Both now use the preview.
  • A damaged file says so in our own words — A truncated upload kept its PDF header, so it reached the browser's viewer and drew that viewer's black "Failed to load PDF document" panel inside the preview, with a Reload that could not help. The file is checked for both its header and its closing marker first, and a file that fails gets a plain explanation and the download button, which is the thing that actually works.

Rescheduling a 1:1

  • The date of the next 1:1 can be changed — Editing a 1:1 offered the cadence, the time and the duration, but no date, so moving one to another day meant deleting it and setting it up again — losing the agenda, the notes and the calendar entry with it. Changing the time still moves every upcoming meeting that follows the series; changing the date moves only the next one.

Who sets performance up

  • Performance is run for people, not by them — Creating a 1:1 or a goal was allowed for "you, or an administrator", which put a New 1:1 and an Add Goal button on every profile for everyone, including people arranging their own reviews. Now an executive may act for anyone including themselves; an administrator for anyone except themselves; a department head for their own department, but not for themselves; and nobody else at all.
  • A department head can finally set one up for their own people — The previous rule gave them no way to, despite being the person who actually holds those conversations.
  • The same rule now covers goal comments — Commenting on a goal was gated separately on "an administrator, or your own goal", which disagreed with that rule in three directions at once: an employee could annotate their own goal, an administrator could annotate their own, and a department head could create a goal for one of their people and then not comment on it. The Add Comment button is gated to match, as are the delete controls on 1:1s, reviews and goals. Whoever wrote a comment may always remove it.
  • A link to a person's reviews now opens their reviews — The Reviews tab is stored internally under an older name, so a link ending ?perfTab=reviews quietly opened the 1:1s tab instead. It looked like the reviews having vanished rather than like a mistyped address.
  • The employee still owns their progress — They move the percentage and the status on a goal set for them. The goal's definition — its category and weight — stays with whoever may set it, which now includes the department head.
  • Removing follows the same rule as creating — Deleting a goal, or a whole 1:1 series, is done by whoever runs the conversation. Both previously allowed the subject: an employee could delete a goal their manager had set, or a 1:1 series their department head had arranged, along with every agenda item and note on it. The buttons are gone for people who may not use them, and the endpoints refuse regardless of the buttons.

Dates and timezones

  • A 1:1 books the day the form showed — The meeting date is a calendar day, with the time of day held separately, and it was being parsed as an instant. Every 1:1 booked from a browser west of UTC landed on the day before the one displayed. With no date given, "a week from today" was also counted on the server's clock rather than the organization's.
  • Anniversaries are counted in the employee's own timezone — It is their anniversary, so the day is resolved for them rather than for the server or whoever is looking.

Everywhere else

  • Destructive actions ask first — Deleting a 1:1 series, a goal, a goal comment or an agenda item now says what is about to be lost and names it. Several of these were a single unguarded click, and the ones that did ask used the browser's own dialog, which cannot describe what is being removed and which Chrome suppresses after a few uses.
  • Lists show what is loading — Goals, reviews and 1:1s rendered their empty state while the request was still in flight, so a profile read as "this person has no goals" rather than "not loaded yet".
  • The profile page uses the full width — Matching the people and expenses pages.
  • Vendor names removed from customer-facing copy — Guided tour text named the specific AI models behind a feature. That is an implementation detail, and it dates.

Under the hood

  • Review cycle scope, anniversary dates and "is this cycle running" each have one implementation shared by the screens and the job that sends reminders, after a second copy of the last one let the settings list call a cycle Ended while the 1:1 picker still offered it.
  • The reminder job de-duplicates on a stored marker keyed by the cycle, the person, the anniversary and the milestone, so a retry, restart or overlapping run sends nothing twice.
  • The Google and Outlook adapters had each declared their own copy of the same calendar event type, and the build was silently discarding one of them.
  • The demo lockdown guard is now documented as needing to be run the way CI runs it — scoped to the branch's own changes rather than against the whole API, where new handlers were being lost in a pre-existing backlog.

v1.0.21

Invitations that lead somewhere, profile photos that actually work, and documents that close their own onboarding tasks

This release fixes two ways a person could be left stuck at the front door. Someone invited by an administrator was chased with an email asking them to verify their address, when what they needed was to set a password — and following it stranded them for good. Separately, signing a document sent by hand left the matching onboarding task open, so employees were asked to sign the same thing twice.

Profile photos also work properly for the first time: there is a way to choose and frame one, a photo appears everywhere that person is shown rather than in a handful of places, and it updates the moment it changes instead of after a page refresh or a sign-out.

Alongside those: new organizations now start with a full set of leave types and departments rather than a blank structure, an import can invite the people it creates, departments and data import are restricted to administrators, and a signature that fails validation no longer leaves the signer unable to retry.

Invitations

  • An invited employee is now chased with the right email — Two kinds of account sit in the "email not yet verified" set and they need opposite things. Someone who registered themselves chose their own password, so what is unproven is their address. Someone an administrator invited is the other way round: the address was vouched for by the person who typed it, and the password is one the system generated and never showed them.
    Invitees were being sent "Please verify your email address". It does not unblock them, and following it made things worse: verifying marked the address proven, dropped them out of the follow-up schedule for good, and still left them with no password. The real invitation expired quietly in the background. They now receive their setup link again instead, with a fresh fourteen-day token.
  • Follow-ups are timed to when someone actually needs access — Reminders counted from the day the record was created, but administrators routinely set people up weeks before they start. That meant every reminder fired, and the invitation lapsed, before the new starter's first day. Invitations are now chased on day 3, 7 and 13 counted from a week before the start date, or from the day the account was created if that is later. The last nudge lands the day before the first link expires, so it arrives while the original is still usable.
  • Former employees are never chased — Anyone whose employment end date has passed is skipped entirely, so a roster containing leavers cannot produce an email inviting them to activate an account.

Data import

  • An import can invite the people it creates — Imported employees were created with no usable password and nothing to tell them the account existed. The preview step now offers Invite these employees to set up their accounts: ticked, each person is emailed a link to choose a password and is followed up on the same schedule as any other invitation.
    It is off by default. An import is as often a historical roster — leavers, closed leave — as it is a live workforce moving across, and emailing a former employee a link to activate an account is the one outcome nobody wants. Anyone whose employment has already ended is skipped even when the box is ticked, so the file decides rather than anyone's memory of what is in it.
  • Imports no longer report failure after succeeding — Every import finished by writing an audit entry with an action the database does not recognise. The records were created, then the write was rejected, so the job was marked failed and the administrator was told the import had not worked and invited to run it again.

Documents

  • A document sent by hand now closes the onboarding task it satisfies — An administrator can send a template straight from Documents → Templates, and the same document can also be attached to an onboarding or offboarding task. Signing the one sent by hand left the task open, so the employee was asked to sign a document they had already signed.
    The machinery to close the task already existed; what was missing was the link. Only documents created by an onboarding task recorded which template they came from, so a hand-sent document was an orphan with nothing to match on. Both the one-off send and the bulk send now record it, which closes the loop in both directions: signing a hand-sent document completes the task, and a task that later needs that document reuses the one already sent instead of issuing a second copy.
    A task is only ever closed by the employee it belongs to signing their own copy. Where a document carries more than one signer — an agreement counter-signed by a manager, say — the counter-signature closes nothing for the manager, who still has their own copy to sign.
  • A signature that fails validation can now be corrected — Submitting a signature with a required field still empty marked the assignment as signed and then rejected the submission. The document was never actually signed, the onboarding task never closed, and every retry was refused with "This document has already been signed" — leaving the signer with no way forward at all. The signature is now recorded only after the submission passes validation, so a rejected attempt leaves everything as it was and can simply be retried.
  • Templates and bulk send are reachable from the upload page — "Add a document" only ever uploaded a fresh file, and the links to saved templates and bulk send existed on the documents list alone. Administrators who started from the upload page had no route onward and no sign that either feature existed, and were re-uploading files they already had as templates.

Onboarding for new organizations

  • Ten leave types instead of eight, with the right icons — A new organization was missing Sick Leave (Unpaid) and Special Event Leave, and Annual Leave carried the umbrella icon that belongs to Unpaid Leave — the two had been swapped. The full set is now Annual Leave (Vacation Time), Sick Leave (Paid and Unpaid), Working from home, Special Event Leave, Maternity, Paternity, Meeting, Compassionate and Unpaid Leave. Each requires manager approval, deducts from the correct balance, and carries the privacy setting its category calls for.
  • Six departments to start from — Sign-up left an organization with a single department named after the company itself, created only so the founding user had somewhere to belong; everything else had to be built by hand before anyone could be invited into a department. New organizations now start with Executive, Software Development, IT Operations, Finance & Accounting, Sales and Operations, each with its own colour. The placeholder becomes the Executive Department rather than sitting alongside the new ones, so the founder keeps their membership.
    Seeding only ever runs on an organization's first trip through setup, and the rewrite only touches a department still untouched since sign-up — an administrator who renames it first keeps their name, code and colour.

Profile photos

  • Choosing and framing a photo — There was no way to set a profile picture after the first-run wizard, and no way to say which part of an image to use: whatever was uploaded was centre-cropped by the browser, so a photo that was not already square was cropped by luck. Picking a photo now opens a framing step — drag to reposition, scroll or use the slider to zoom, and what sits inside the circle is what is saved.
    Framing on a canvas also drops the orientation data that makes phone photos appear sideways, and normalises every upload to one size and format regardless of what was chosen.
  • Photo actions live on the profile, next to Edit Profile — Clicking the picture opens the actions directly: see the picture, choose a new one, or remove it. The same entries are in the Edit Profile menu, which is where someone looks when they want to change a colleague's photo rather than their own. An employee with no other editing rights sees only the photo entries there; the information sections stay with administrators.
  • Photos open in a viewer with zoom — Opening a picture used to give a flat, fixed-size image, which is not much use for the one thing people open a photo to do. It now opens in a viewer with zoom in, zoom out, a percentage that returns to fit when clicked, drag to pan, scroll and keyboard shortcuts, and Escape to close.
  • A new photo appears everywhere at once — Uploading a photo changed it on the profile page while the sidebar beside it carried on showing initials until the page was reloaded — and for anyone whose photo was set after they signed in, not even a reload helped, only signing out and back in. Each part of the app kept its own private copy of the image and none of them could tell the others that it had changed; the sidebar, separately, read the photo from a snapshot written once at sign-in and never updated. There is now one shared copy, and a photo changed anywhere is picked up in place by everything showing that person.
  • Photos now show where only initials did — Around thirty places drew their own initials circle and could never show a photo at all: the people directory and org chart, approvals, timesheets, schedules, projects and issues, time tracking, the team map, reports and client activity. They now all render the same component.
    Four of those could not show a photo even when asked to, because the data behind them left the photo out; those queries now include it. Two more were worse than empty: the Time and Leave report tabs passed a storage path straight to the browser as an image address, so every person with a photo rendered as a broken image, and the initials fallback never ran because the path looked like a valid value.

Permissions

  • Departments are administrator-only — Creating a department and running organization setup had no role check at all, so any employee could add departments or re-run setup and rewrite the leave year, default allowance and timezone. Both now require an administrator or executive. Reading the department list is unchanged, since everyone needs it for filters.
  • A department head can rename the department they lead — Previously they could not correct even the name of their own team. They can now change its name, description and colour. The code, the active state and the head assignment stay with administrators, because those decide the department's identity and who controls it rather than how it reads.
  • Data import is administrator-only, and hidden from everyone else — Creating an import job already required an administrator, but nothing else in the pipeline did. With a job left part-finished, any employee could run it, roll it back or delete it — and running one writes employee and department records. The row-level error report was readable too, which quotes the uploaded file and therefore colleagues' details. Every import endpoint now requires an administrator or executive. The settings entry was already hidden, but the page itself had no guard, so a typed URL rendered the whole import interface.

Security

  • Values are escaped before they reach an email — Email bodies are assembled as text, and names were being placed into them without escaping. A name containing a link would have rendered as a working link inside a message carrying our branding and sent from our domain, sitting above the genuine button. Every value interpolated into an email is now escaped; ordinary names are unaffected.
  • Invitations sent by an import are held to the plan's user allowance — Inviting turns one upload into one email per row from our own sending domain, so the number that can be sent is bounded rather than left to the size of the file.

Fixes

  • Calendar tooltips are no longer cut off — Hovering a day near the right-hand edge of the dashboard calendar showed a tooltip clipped by the card, so the leave type and status were unreadable exactly where the grid is busiest. Tooltips now stay within the window wherever the day sits, and still point at the day they describe.

v1.0.20

Data import and migration from 48 HR platforms, plus a security and stability pass

This release adds Data Import & Migration, a guided way to bring an existing HR system's people, departments, and time-off history into BookYourPTO. It ships with built-in column mappings for 48 platforms, direct API connections for four of them, and a preview step that writes nothing to the database until it is approved. Alongside it: the framework and its dependencies were moved onto patched releases, and three regressions that came with that upgrade were found and fixed before release.

Data Import & Migration

  • A four-step wizard — Upload a file, confirm how its columns map onto BookYourPTO fields, review a preview of exactly what will be created, then import. The wizard is at Settings → Data Import and is available to administrators and executives.
  • Nothing is written until you approve it — The preview validates the first 100 rows and shows what each one would create, so problems with the mapping surface before anything reaches the database. Rows that cannot be imported are reported with the reason and skipped, so a single malformed date does not fail the whole file.
  • Imports can be rolled back for 72 hours — A completed import can be reversed from its detail page within three days, which matters when a mapping turns out to have been wrong on the second look rather than the first.
  • 48 platforms recognized automatically — Built-in templates cover 63 column layouts across 48 platforms. The uploaded file's headers are matched against them, so in most cases the mapping is already filled in when the step opens. Any column can still be remapped by hand, and unmatched columns are skipped rather than guessed at.
  • Employees, leave history, and departments — Each is imported separately, so a migration can be done in stages: people first, then their historical time off. Leave rows are matched back to employees by email within the organization.
  • CSV and Excel — Both .csv and Excel workbooks (.xlsx, .xls) are accepted, since most HR systems export one or the other and few offer a choice. Files can be up to 25MB and 10,000 rows; larger migrations can be split across several imports.
  • Sample files — A sample CSV for each of the three data types can be downloaded from the import page, for teams building a file by hand rather than exporting one.
  • Save your own column mappings — An organization can save a custom mapping as a reusable template. Custom templates take priority over the built-in ones, which covers systems that export a bespoke report layout.
  • Canadian coverage — 12 of the supported platforms are Canada-first: Collage HR, Employment Hero (formerly Humi), Folks HR, Payworks, Rise People, Wagepoint, Payment Evolution, Avanti Software, Nethris, PurelyHR, Wave Payroll, and Knit People. Folks HR serves Quebec employers and exports in the account language, so its templates recognize both English and French column headers rather than requiring every column to be remapped by hand.

Direct platform connections

  • Import without exporting a file — BambooHR, Timetastic, Employment Hero (formerly Humi), and Zoho People can be connected directly. Once connected, employees and leave history are pulled straight from the account and can be re-imported at any time without producing a new export.
  • BambooHR, Timetastic, and Employment Hero connect with an API key. BambooHR also needs the account subdomain.
  • Zoho People connects by signing in to Zoho, so no key needs to be copied between systems. The connection uses the Canadian Zoho region.
  • Connections are tested before they are saved — Credentials are verified against the provider when the connection is created, so a mistyped key is reported immediately rather than at the first import.

Security

  • Framework and dependency updates — The application framework and its build toolchain were moved onto patched releases, closing every advisory raised by automated security scanning. These covered remote code execution and cross-user data disclosure in server-side rendering, an authentication bypass on mixed-case route paths, a cross-site-scripting issue in HTML sanitization, and a development-tools issue that could allow command execution on a developer's own machine. Automated scanning reports no remaining advisories.
  • The full test suite and a production build were verified on the new versions, and the three regressions the upgrade introduced were found and fixed rather than shipped. They are listed below.

Fixes

  • Authenticated requests could be sent without their credentials — A framework change altered when the shared request helper is bound, with the effect that the authorization header stopped being attached. The application would load and then every request to the API would be rejected. Requests now resolve the helper at call time, and a regression test pins that behavior so a future upgrade fails the build instead of the login.
  • The production server would not start — The build stopped emitting part of a required runtime dependency, so every page request returned an error while the API kept answering normally. That combination would have reported a deployment as healthy. The dependency is now bundled directly, with a test that fails if the incomplete form reappears.
  • Leave records on the edge of a time zone were skipped on import — The API connectors ended their fetch window on the server's UTC day. An organization running ahead of UTC had already moved into a day UTC had not reached, so time off booked on their current day fell outside the window and was never imported, with the job still reporting success. The window now extends past every real time zone offset.
  • Hours could be imported as days — The Payworks leave template mapped an hours column onto the day-count field, which would have recorded 7.5 hours as 7.5 days. The row would have validated and imported cleanly while overstating the employee's usage. The mapping was removed and a check now scans every leave template for the same class of mistake.
  • Platform logos were missing from the templates list — The built-in templates page showed a generic icon for all 63 entries. Logos are now served from a single shared list used by every screen that shows them.
  • Searching the platform picker returned an error — Typing in the platform search field raised an error instead of filtering the list.

v1.0.19

Probation review tracking, accurate leave carry-over, and a stricter browser security policy

This release adds Probation Milestone Tracking — a new employee event that sits alongside birthdays and work anniversaries on the dashboard and calendar, with automated reminder emails so a probation review never quietly slips past its date. It also lands a substantial correctness pass on leave carry-over, where the balance shown on the calendar and the balance the booking form enforced could disagree. Rounding it out: leave allowance becomes a proper administrator control, the browser-side security policy is now enforced rather than advisory, and product analytics is added under the existing consent flow.

Probation Milestone Tracking

  • Probation period on every employee — When creating or editing an employee you can now set a probation period of None, 3 Months, or 6 Months. The Add User form also gained a Hire Date field, so a new starter can be set up with their probation in one pass.
  • The review date calculates itself — The probation review date is derived from the hire date plus the probation period (hired Jan 15 on a 3-month probation → review due Apr 15). Both the employee form and the Add User form show a live preview of the resulting date as you choose, and month-end dates are handled sensibly — a Nov 30 hire on a 3-month probation reviews on Feb 28 (or Feb 29 in a leap year), never spilling into March.
  • Extend probation when you need to — Administrators can override the calculated date with a custom Probation Review Date. When set, it takes precedence everywhere the milestone appears and is labelled as extended, so it is obvious the date was moved by hand rather than calculated.
  • On the dashboard and the calendar — Probation reviews now render as their own employee event, using a dedicated icon and colour distinct from birthdays and work anniversaries, with a tooltip naming the employee, the probation length, and whether it was extended. Managers can spot an upcoming or overdue review at a glance without working the date out by hand.
  • On the employee profile — The Job tab now shows Hire Date, Probation Period, and the calculated (or overridden) Probation Review Date together, giving HR a single reference point when reviewing someone's record.
  • Automated reminder emails — A reminder now goes out 14 days before, 7 days before, and on the probation review date. Each email carries the employee's name, position, department, hire date, probation length, and review date, plus a direct link to their profile so the reviewer can start immediately. A matching in-app notification is raised at the same time.
  • Choose who gets reminded — Reminder recipients are configurable per organization from the notification settings: the employee's direct manager, their department head, all administrators, all executives, or any combination. Reminders can also be switched off organization-wide. Manager and department head are resolved per employee, so each reminder reaches the people who actually run that person's review.
  • Reminders follow the employee's calendar — The countdown to a review is evaluated in the employee's own timezone (falling back to the organization's), so a review due "today" means today where that person works, not where the server happens to run.
  • Probation status stays confidential — Unlike a birthday, whether someone is on probation is only visible to the employee themselves, their direct manager, their department head, and administrators or executives. Other colleagues simply do not see the milestone.

Leave carry-over accuracy

  • The calendar and the booking form now agree — A user with a custom allowance plus a manual carry-over adjustment could see one figure on their calendar balance card and be told a different, smaller number when they tried to book. Every place that computes a leave balance — the balance card, the dashboard people list, the booking check, and the leave edit check — now runs through one shared calculation, so the number you are shown is the number that is enforced.
  • Carry-over no longer repeats every year — A manual carry-over adjustment is now anchored to the fiscal year it was granted for. Previously an adjustment had no year of its own, so every subsequent fiscal year kept counting it — days granted for one year still appeared in the next.
  • No more double-counted carried days — The allowance tile on the balance card was adding carried days on top of a total that already included them, so someone with 15 base days plus 5 carried read "16 / 25 days" instead of "16 / 20". The tile now shows the entitlement before carry-over, so the row reads base + carried − used = remaining.
  • Bookings check the right year — A leave request is now balanced against the fiscal year the leave actually falls in, rather than the year the request happens to be filed in. Booking next January's holiday in December is checked against next year's allowance.
  • Expired adjustments clear themselves — Once a carry-over adjustment's expiry date passes, the days stop counting toward the balance and the figure is now cleared from the profile automatically. Previously it lingered on the record and an administrator had to zero it by hand.
  • A week's warning before days lapse — A new daily reminder notifies the employee's department head — falling back to administrators and executives when they have no manager — seven days before a carry-over adjustment expires, in-app and by email, so someone can extend the expiry or top the days up before they are lost. Day counting runs in the employee's own timezone, and the reminder cannot fire twice for the same adjustment.
  • Clearer allowance wording — The Leave Allowance tab now names the fiscal year an adjustment applies to and states that the days are cleared automatically afterwards, instead of implying they are permanent.

Permissions

  • Leave allowance is an administrator control — The fields that decide how many paid days someone can book — custom allowance, carry-forward settings, and carry-over days — are now restricted to administrators and executives organization-wide, and to department heads for members of their own department. Nobody can change their own.
  • Probation is an administrator control — Probation period and the probation review date override are restricted the same way, so the date that drives the reminder emails cannot be moved by the person being reviewed.

Privacy & Security

  • Stricter browser security policy, now enforced — The application's content security policy moved from advisory to actively enforced, so the browser blocks anything outside the vetted allowlist. Additional cross-origin isolation protections were added at the same time, and the server no longer advertises its underlying framework in responses.
  • Security disclosure contact published — The application now publishes a standard machine-readable security contact so researchers have a clear route to report an issue.
  • Dependency security updates — Third-party dependencies flagged by automated security scanning were updated to patched releases across the tree, with the full test suite and a production build verified on the new versions.
  • Product analytics added under the analytics consent category — A product-analytics tool was added to help us understand how features are actually used. It loads only after a visitor grants analytics consent, only on our own canonical web domains, and never inside the mobile app's web session or on white-label customer domains. Withdrawing analytics consent switches it off immediately.
  • Everyone is asked to consent again — Because a new vendor joined the analytics category, the consent banner reappears once for every visitor, with no pre-ticked toggles and nothing loading until a fresh choice is made. The new vendor is disclosed by name in the cookie Customize panel and the category description was updated to match.

Fixes

  • Icons render across the app again — Icons are now bundled with the application rather than fetched at runtime, restoring them everywhere under the enforced security policy and removing a network round trip on every page.
  • Document and PDF previews render again — Document previews, template detail views, expense receipt viewing, and the personal data-drive preview all display correctly under the enforced policy.
  • Location maps render again — The map pane on the document and timesheet location views displays again, including for organizations without their own maps key configured.

Behind the scenes

  • Probation review dates resolve through a single shared implementation used by the server, the dashboard, the calendar, the profile, and the reminder job — so a date shown in the UI can never disagree with the date a reminder fires on. Leave carry-over math was consolidated the same way, replacing four drifting copies with one.
  • All calendar-day handling in the new code follows the project's date-only convention, with regression tests exercising non-UTC organization timezones on both sides of UTC, month-end clamping, and leap years.
  • Demo data now includes probation periods, extended reviews, and reminder recipients, so the demo environment reflects the new feature.

Full Changelog: https://github.com/anhourtec/BookYourPTO-SaaS/compare/v1.0.18...v1.0.19