Payroll and HRIS
Balt works inside Lucca.
You change nothing about Lucca. Balt connects to it, reads what it needs and hands back finished work.
What you can ask it
What Balt does in Lucca
Reads availability
Reads who's on the bench or rolling off from Lucca.
Flags the dates
Surfaces contract ends and start dates before they catch you out.
Keeps it current
Keeps availability and end dates current from what it reads.
Keeps you in control
Reads what it needs and writes nothing sensitive without your approval.
How it works
- Step 1
Connect once
You connect your Lucca account once, with the permissions you choose.
- Step 2
Write your request
You write your request in Slack or Teams, in plain language, as you would to a colleague.
- Step 3
Balt does the work
Balt does the work in Lucca and shows you anything outbound before it leaves.
Security and permissions
Balt reaches only what you open to it, and access is withdrawn in one move. None of your data trains a model, ours or a supplier’s. Every action is logged: you can say who did what, when, and on whose request.
Frequently asked questions
Does Balt replace Lucca?
No. Balt works inside Lucca with your existing account: nothing to migrate, nothing to relearn, and your teams keep using the tool as before.
What permissions does Balt need on Lucca?
Only the ones you grant. Read and write are set separately, and an access is withdrawn in one move without going through our support.
Does Balt act on its own in Lucca?
It acts alone on what stays internal and reversible. Anything leaving the company is shown to you before it goes, and a decision that closes a door stays human.
Is my Lucca data used to train a model?
No, contractually, including at downstream model providers. Your data stays yours and is hosted in the European Union.
Balt also connects to
More Payroll and HRIS integrations
Your tool is not on the list?
Tell us which one. The most requested integrations come first, and we can wire up a new one quickly.