Staff
Everyone gets their own sign-in, and sees only the parts of the service their job needs.
Invite by email
No shared password, and no account for you to set up.
Their job decides what opens
Not who you trust. The same rule applies to everyone in that job.
See what each person owes
Open anyone on your team and see which policies they have signed off.
Step 1
Invite your team by email
You send an invitation and they set themselves up. Nobody is handed a password, and nobody waits on you to make them an account.
Step 2
The job decides what opens
Our server checks each person’s job every time they open a page, so a page somebody should not reach does not load at all.
Step 3
Every person, and what they still owe
Open anyone on your team to see which policies they have signed off and which they have not. Every change in the app is saved against the person who made it, which is what makes a date here worth anything at an inspection.
Your whole team
One price per childcare, however many people you add.
They set themselves up
An invitation by email, accepted by them.
Changes have a name on them
Every change is saved against the person who made it.
Remove in one place
Take someone off and their access goes with them.
Set your childcare up in a few minutes.
No card, no import, no setup call. Add a record and see how it fits.
What it doesn't do
We do not hold Garda vetting, qualifications, references or training records. There is no rota, so nothing here knows who was working on a given day. The jobs are fixed. You cannot build your own set of permissions.
The Everything Plan
Every feature for one price per childcare, whether you have 1 staff or ten, 1 child or a hundred.
Questions
- Can we share one login?
- You can, and you should not. A record is worth something because it says who wrote it, and a shared login says nobody.
- Does adding staff cost more?
- No. One price per childcare covers everyone you add.
Something else? .
