Integrations
Your roster already knows who works for you.
You entered your workforce once, in the system that rosters them. CORA connects to ShiftCare and reads it, so the same names never get typed a second time. CORA Workforce integrates with ShiftCare, reading the staff list from a provider's own roster so the workforce is entered once and the training, credential and policy records attach to the same people.
ShiftCare, connected
An administrator pastes your own ShiftCare API key into Settings. CORA reads the staff on that account and matches them against the workers already in CORA. Anyone new comes through as a proposal for you to confirm, and once confirmed they inherit the right pathway for their role, their due dates, and the reminders that chase them.
Available now.
The key goes in and never comes out
Only an administrator can connect an account. Once your key is sealed it cannot be read back out of CORA, by the screen that submitted it, by support, or through any endpoint at all. If you ever lose track of a key you issue a fresh one in ShiftCare, which is the right answer anyway.
You can pause the connection and keep the key, or disconnect and delete it, whenever you choose.
A person confirms each match, and that is deliberate
Two workers can share an email address. A household uses one between them, and an agency address turns up across several people at once. Matching on the address alone would attach one person's compliance record to another, and that is exactly how somebody who left in June starts being assigned training in September.
So CORA confirms a batch only when the email and the name both match and the worker is still active. Everything else is put in front of you one at a time, with what it found and what it is unsure about. It takes a few minutes once, at connection, and it is the difference between a register you can hand an auditor and one you cannot.
CSV in and out, for everything else
Bulk-add workers from any system by pasting or uploading a list of names and email addresses. Training status, credential expiry dates and the full evidence pack export back out as CSV for any date range you choose, so the records reach whatever else you run.
Credentials go back out
A credential verified in CORA becomes a ShiftCare staff qualification, carrying its expiry date and its certificate across with it, so nobody re-keys the same thing twice.
CORA reads what ShiftCare already holds for that person before it writes, updating the row if it is there and creating it if it is not, so a sync that runs every day never leaves duplicates behind it.
Tell us what else you run
ShiftCare is where we started because providers asked for it first. If the system you roster or pay from is not here yet, email hello@coraworkforce.com.au and tell us what you use. That is genuinely how the queue gets ordered.