[{"data":1,"prerenderedAt":242},["ShallowReactive",2],{"$f1jq4xycipvu26":3,"mdc--z032wl-key":14},{"release":4,"newer":9,"older":11,"page":13},{"tag":5,"name":5,"publishedAt":6,"prerelease":7,"markdown":8},"v1.1.5","2026-10-21T03:27:49Z",false,"## Bug fixes\r\n\r\n- **Deactivated employees were offered as people to send work to.** A person who had left stayed\r\n  on the Users page marked Inactive, as intended, but also kept appearing in the Documents Bulk\r\n  Send recipient list and in fourteen other pickers: template signers, document assignment,\r\n  training assignment and bulk assignment, new shifts, new time entries, lock dates, a\r\n  department's manager, the timesheet approver, onboarding contacts and task assignees, and\r\n  geofence assignments. They are no longer offered anywhere work is given to someone, and every\r\n  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.\r\n  A setting that already names someone who has left shows them labelled \"(inactive)\" so it can\r\n  be changed, and filing a leaver's final paperwork into their folder still works.\r\n- **Saved defaults that pointed at a leaver.** An onboarding task list whose saved assignee has\r\n  left now gives that task to the default assignee; an expense whose submitter's manager has\r\n  left goes to the active administrators for approval; a timesheet whose named approver has left\r\n  is signed by the employee alone instead of waiting on someone who cannot sign. Copying a week of\r\n  shifts no longer copies shifts for people who have left.\r\n\r\n- **Templates could not be deleted after a bulk send.** Deleting any template that had ever been\r\n  used in a Bulk Send failed with \"Failed to delete template\". It now deletes, and the bulk send's\r\n  history, the documents it created and their signatures are all kept.\r\n- **Leave types could not be deleted when they had balances but no requests.** The delete failed\r\n  with \"Failed to delete leave type\"; the unused balances are now removed with the type.\r\n- **Template cards said \"0 sends\" for templates sent through Bulk Send.** Bulk sends now count\r\n  each document they create, and existing templates were brought up to date.\r\n- **Bulk Send listed only the first 20 templates.** It now lists up to 100.\r\n\r\n## Security\r\n\r\n- **Three places accepted a person from another organization.** Adding a certification to an\r\n  employee, setting a project issue's assignee or reporter, and an administrator assigning shifts\r\n  (single or bulk) did not check that the person belonged to the caller's organization. A\r\n  certification's type, and a geofence assignment's department or project, were not checked\r\n  either. All of them now refuse an id from outside the organization.\r\n\r\n## Public API\r\n\r\n- Assigning training (`POST \u002Fusers\u002F{id}\u002Ftraining`, unless recording it as completed), issuing an\r\n  asset (`POST \u002Fusers\u002F{id}\u002Fassets`), setting `manager_id` (`PATCH \u002Fusers\u002F{id}`) and creating a time\r\n  entry for another person (`POST \u002Ftime-entries`, for work after their last day) now answer\r\n  `VALIDATION_FAILED` when the person is deactivated, as booking leave already did. Re-sending a\r\n  manager who has since left, unchanged, is still accepted.\r\n\r\n## Improvements\r\n\r\n- **Upload a new version of a template.** A document that needs a change after it was sent is\r\n  updated in place: open the template, choose **Upload new version**, and the amended file becomes\r\n  the next version under the same name, keeping its settings, departments, signer roles and\r\n  signing fields. Documents already sent keep the version they were sent with. Onboarding\r\n  checklists move to the new version for anyone not yet issued the document. Every version stays\r\n  viewable, with who uploaded it and how many documents were sent from it.\r\n- **Template names are unique.** Creating or renaming a template to a name another active template\r\n  already has is refused, and the create page offers to upload the file as a new version of that\r\n  template instead. Archived templates and older versions do not hold a name.\r\n- **Old versions and archived templates are never offered for sending.** Bulk Send, Send and\r\n  onboarding task lists offer only the current version; a page left open on an old version is\r\n  told to refresh.\r\n- **Redesigned Templates page.** Templates are listed in a table with search, category and type\r\n  filters, sortable columns, version and upload date on every row, and one actions menu (send,\r\n  edit fields, rename, upload new version, archive, restore, delete). The template page now shows\r\n  its name with a rename button, its version history, and runs full width. Bulk Send's template\r\n  list shows each template's version and upload date.\r\n\r\n- **Birthday greetings arrive at 9:30.** Each person's birthday greeting is now sent at 9:30 in\r\n  the morning, local time — the timezone on their profile, or the organization's timezone when\r\n  they have not set one. It used to arrive at about 9:40. In the few regions whose clocks are\r\n  offset by a half or quarter hour from UTC (such as India, Newfoundland or Nepal), it arrives at\r\n  10:00 or 10:15 instead.",{"tag":10,"name":10},"v1.1.6",{"tag":12,"name":12},"v1.1.4",1,{"data":15,"body":16},{},{"type":17,"children":18},"root",[19,28,94,100,113,119,176,182],{"type":20,"tag":21,"props":22,"children":24},"element","h2",{"id":23},"bug-fixes",[25],{"type":26,"value":27},"text","Bug fixes",{"type":20,"tag":29,"props":30,"children":31},"ul",{},[32,44,54,64,74,84],{"type":20,"tag":33,"props":34,"children":35},"li",{},[36,42],{"type":20,"tag":37,"props":38,"children":39},"strong",{},[40],{"type":26,"value":41},"Deactivated employees were offered as people to send work to.",{"type":26,"value":43}," A person who had left stayed\non the Users page marked Inactive, as intended, but also kept appearing in the Documents Bulk\nSend recipient list and in fourteen other pickers: template signers, document assignment,\ntraining assignment and bulk assignment, new shifts, new time entries, lock dates, a\ndepartment's manager, the timesheet approver, onboarding contacts and task assignees, and\ngeofence assignments. They are no longer offered anywhere work is given to someone, and every\nrequest 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.\nA setting that already names someone who has left shows them labelled \"(inactive)\" so it can\nbe changed, and filing a leaver's final paperwork into their folder still works.",{"type":20,"tag":33,"props":45,"children":46},{},[47,52],{"type":20,"tag":37,"props":48,"children":49},{},[50],{"type":26,"value":51},"Saved defaults that pointed at a leaver.",{"type":26,"value":53}," An onboarding task list whose saved assignee has\nleft now gives that task to the default assignee; an expense whose submitter's manager has\nleft goes to the active administrators for approval; a timesheet whose named approver has left\nis signed by the employee alone instead of waiting on someone who cannot sign. Copying a week of\nshifts no longer copies shifts for people who have left.",{"type":20,"tag":33,"props":55,"children":56},{},[57,62],{"type":20,"tag":37,"props":58,"children":59},{},[60],{"type":26,"value":61},"Templates could not be deleted after a bulk send.",{"type":26,"value":63}," Deleting any template that had ever been\nused in a Bulk Send failed with \"Failed to delete template\". It now deletes, and the bulk send's\nhistory, the documents it created and their signatures are all kept.",{"type":20,"tag":33,"props":65,"children":66},{},[67,72],{"type":20,"tag":37,"props":68,"children":69},{},[70],{"type":26,"value":71},"Leave types could not be deleted when they had balances but no requests.",{"type":26,"value":73}," The delete failed\nwith \"Failed to delete leave type\"; the unused balances are now removed with the type.",{"type":20,"tag":33,"props":75,"children":76},{},[77,82],{"type":20,"tag":37,"props":78,"children":79},{},[80],{"type":26,"value":81},"Template cards said \"0 sends\" for templates sent through Bulk Send.",{"type":26,"value":83}," Bulk sends now count\neach document they create, and existing templates were brought up to date.",{"type":20,"tag":33,"props":85,"children":86},{},[87,92],{"type":20,"tag":37,"props":88,"children":89},{},[90],{"type":26,"value":91},"Bulk Send listed only the first 20 templates.",{"type":26,"value":93}," It now lists up to 100.",{"type":20,"tag":21,"props":95,"children":97},{"id":96},"security",[98],{"type":26,"value":99},"Security",{"type":20,"tag":29,"props":101,"children":102},{},[103],{"type":20,"tag":33,"props":104,"children":105},{},[106,111],{"type":20,"tag":37,"props":107,"children":108},{},[109],{"type":26,"value":110},"Three places accepted a person from another organization.",{"type":26,"value":112}," Adding a certification to an\nemployee, setting a project issue's assignee or reporter, and an administrator assigning shifts\n(single or bulk) did not check that the person belonged to the caller's organization. A\ncertification's type, and a geofence assignment's department or project, were not checked\neither. All of them now refuse an id from outside the organization.",{"type":20,"tag":21,"props":114,"children":116},{"id":115},"public-api",[117],{"type":26,"value":118},"Public API",{"type":20,"tag":29,"props":120,"children":121},{},[122],{"type":20,"tag":33,"props":123,"children":124},{},[125,127,134,136,142,144,150,152,158,160,166,168,174],{"type":26,"value":126},"Assigning training (",{"type":20,"tag":128,"props":129,"children":131},"code",{"className":130},[],[132],{"type":26,"value":133},"POST \u002Fusers\u002F{id}\u002Ftraining",{"type":26,"value":135},", unless recording it as completed), issuing an\nasset (",{"type":20,"tag":128,"props":137,"children":139},{"className":138},[],[140],{"type":26,"value":141},"POST \u002Fusers\u002F{id}\u002Fassets",{"type":26,"value":143},"), setting ",{"type":20,"tag":128,"props":145,"children":147},{"className":146},[],[148],{"type":26,"value":149},"manager_id",{"type":26,"value":151}," (",{"type":20,"tag":128,"props":153,"children":155},{"className":154},[],[156],{"type":26,"value":157},"PATCH \u002Fusers\u002F{id}",{"type":26,"value":159},") and creating a time\nentry for another person (",{"type":20,"tag":128,"props":161,"children":163},{"className":162},[],[164],{"type":26,"value":165},"POST \u002Ftime-entries",{"type":26,"value":167},", for work after their last day) now answer\n",{"type":20,"tag":128,"props":169,"children":171},{"className":170},[],[172],{"type":26,"value":173},"VALIDATION_FAILED",{"type":26,"value":175}," when the person is deactivated, as booking leave already did. Re-sending a\nmanager who has since left, unchanged, is still accepted.",{"type":20,"tag":21,"props":177,"children":179},{"id":178},"improvements",[180],{"type":26,"value":181},"Improvements",{"type":20,"tag":29,"props":183,"children":184},{},[185,202,212,222,232],{"type":20,"tag":33,"props":186,"children":187},{},[188,193,195,200],{"type":20,"tag":37,"props":189,"children":190},{},[191],{"type":26,"value":192},"Upload a new version of a template.",{"type":26,"value":194}," A document that needs a change after it was sent is\nupdated in place: open the template, choose ",{"type":20,"tag":37,"props":196,"children":197},{},[198],{"type":26,"value":199},"Upload new version",{"type":26,"value":201},", and the amended file becomes\nthe next version under the same name, keeping its settings, departments, signer roles and\nsigning fields. Documents already sent keep the version they were sent with. Onboarding\nchecklists move to the new version for anyone not yet issued the document. Every version stays\nviewable, with who uploaded it and how many documents were sent from it.",{"type":20,"tag":33,"props":203,"children":204},{},[205,210],{"type":20,"tag":37,"props":206,"children":207},{},[208],{"type":26,"value":209},"Template names are unique.",{"type":26,"value":211}," Creating or renaming a template to a name another active template\nalready has is refused, and the create page offers to upload the file as a new version of that\ntemplate instead. Archived templates and older versions do not hold a name.",{"type":20,"tag":33,"props":213,"children":214},{},[215,220],{"type":20,"tag":37,"props":216,"children":217},{},[218],{"type":26,"value":219},"Old versions and archived templates are never offered for sending.",{"type":26,"value":221}," Bulk Send, Send and\nonboarding task lists offer only the current version; a page left open on an old version is\ntold to refresh.",{"type":20,"tag":33,"props":223,"children":224},{},[225,230],{"type":20,"tag":37,"props":226,"children":227},{},[228],{"type":26,"value":229},"Redesigned Templates page.",{"type":26,"value":231}," Templates are listed in a table with search, category and type\nfilters, sortable columns, version and upload date on every row, and one actions menu (send,\nedit fields, rename, upload new version, archive, restore, delete). The template page now shows\nits name with a rename button, its version history, and runs full width. Bulk Send's template\nlist shows each template's version and upload date.",{"type":20,"tag":33,"props":233,"children":234},{},[235,240],{"type":20,"tag":37,"props":236,"children":237},{},[238],{"type":26,"value":239},"Birthday greetings arrive at 9:30.",{"type":26,"value":241}," Each person's birthday greeting is now sent at 9:30 in\nthe morning, local time — the timezone on their profile, or the organization's timezone when\nthey have not set one. It used to arrive at about 9:40. In the few regions whose clocks are\noffset by a half or quarter hour from UTC (such as India, Newfoundland or Nepal), it arrives at\n10:00 or 10:15 instead.",1794681827123]