Kenjo StrawberrySomeone still has to create leave request. It does not have to be you
Hand a companion the outcome. It reads the Kenjo attendance entries, does the 3-operation version of the job, and stops for your click on anything that changes a record.
Open the attendance entry. Check it against something else. Write the change. Move to the next one. That is the Kenjo afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a attendance entry until you approve it.
What it can do is exactly what Kenjo exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can create a leave request, create an employee and create an attendance entry, and work across the attendance entries, employees and leave requests.
The Kenjo API stops at Kenjo. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the attendance entries come from?
In the tab.
Kenjo exposes no read operation to a connected account, so a companion opens Kenjo in the session you are already signed into and reads the screens you would.
The attendance entries are what most of this inventory is about, alongside the employees. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Kenjo admin becomes a queue you review.
Which attendance entries wait for your approval?
All 3 write operations wait for you.
A companion can create a leave request, create an employee and create an attendance entry, and each one is staged on an approval card first: you see the attendance entry, the field and the new value before it lands in Kenjo.
Nothing in Kenjo is sent, changed or deleted on your behalf without that click, and a rejected card leaves the attendance entry exactly as it was. The gate is the same one on every surface, described at security.
- Create Leave Request
- Create Employee
- Create Attendance Entry
What does the recurring attendance entries pass look like?
Yes.
Saved as a routine, the Kenjo attendance entries pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The recruiting playbook catalogues the other recurring shapes of hiring admin, the Kenjo attendance entries sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents