Flexible time-off approvals, quieter closures and branded forms
Service Desk
Kin will no longer give a warning the request will close. Previously “your request will close in 30 minutes,” and another notification when it closes. Conversations will close (for reporting purposes), however the requester doesn't need to know. If they reply, it will 'reopen' the request. Below is what it was previously, now the conversation will hang at Kin's last response.

Integrations
- More control over booked time off (Workday) — Kin can now edit the amount of time on an already-booked Workday time-off entry, not just cancel and rebook it. Admins can also run any of Kin's PTO tools (check balances, book, edit, cancel) on behalf of a named employee, useful for HR teams managing time off for people who aren't self-serving through Kin yet.
Workflows
- Slack approvals for native UKG Pro WFM time-off — Managers on native UKG Pro WFM now get an Approve/Reject prompt in Slack when their report books time off through Kin, instead of the decision happening outside Kin entirely. Fewer clicks for managers!
- Workflow approvals can go to more than one person — A manual approval step used to lock you into a single approver. Now you can assign it to several people at once, and whichever one responds first decides the outcome. No more bottlenecking on one person's inbox!


Runbooks
Branding on public forms — Public-facing request forms now show your organization's logo for anonymous visitors (previously they'd see Kinfolk's default logo) for personalization.
Big things coming next week
Broadcasts — A new standalone way to send a one-off message to a specific group of employees, without repurposing Runbooks. You'll build a message (title + rich text), pick an audience (either a saved filter or a pasted/uploaded list of people), and send it then, or schedule it for later. These messages are delivered as a direct message from Kin.
Use this to send monthly reminders to a recurring group, or one-time announcements (to announce a new feature in Kin, perhaps).
Runbooks are for lifecycle events, tracking and completion rates. Broadcasts are flash-in-the-pan comms.
