People Lifecycle
Joiners, movers, leavers — nothing left half done.
Onboarding, offboarding and role changes run as checklists built from a template and the roles gained or given up. Items have owners and due dates, IAM changes are applied after a confirm, and the case ends with a record PDF.
Free while in beta
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
What it does
- One case per person and flow: onboarding (start date), offboarding (last day), role change (effective date)
- Tasks and decisions with owners, due dates, sub-checks, dependencies and required evidence; reminders and overdue flags
- IAM changes — new person, role assigned or ended, access invited or revoked — previewed, then applied by an owner or admin
- Automator workflows started by items and ticking them off when they report back
- Files in a restricted vault, a case record PDF on completion, CSV exports
How this tool bills
Today's list prices in EUR, read from the qzila price list when this page was built. You are billed monthly for what you used.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
The API
Every qzila tool is a GraphQL API first; the web UI is one client of it. Anything you can do in the browser you can do from a script, a CI job or the Asign platform.
https://lifecycle.tools.qzila.com/graphqlPOST · application/json · { "query": "…" }
Requests are authenticated with your qzila session (the same sign-in as the browser). For automation, sign in once at identity.qzila.com and reuse the session cookie; API keys for service accounts are on the roadmap.
Whatever this tool detects — a verdict flip, a regression, a change, an incident — is emitted as a signal to the qzila alert hub, which forwards it to email, Slack, a webhook or Jira, and to Service Watch, which can also send it as an SMS. Each signal carries the asset it belongs to, so you can correlate it back to your own inventory (or to an Asign asset).
Main operations
caseStartmutationStart a case: flow, the person (from IAM or a new joiner), the date and the roles gained or given up.
mutation { caseStart( input: { flow: "onboarding", anchorDate: "2026-11-02", joinRoleIds: ["rol_sysadmin"], pending: { firstName: "Jana", lastName: "Nováková", email: "jana@example.com" } } clientRequestId: "req_1" ) { id ref status } }caseItemsqueryEvery item of a case in checklist order, with its state and whether it is overdue.
query { caseItems(caseId: "cs_1") { phase title state overdue } }iamActionApplymutationApply an item's IAM change through IAM, after an explicit confirm (owners and admins).
mutation { iamActionApply(caseId: "cs_1", itemId: "it_4", expectedRev: 3, confirm: true) { kind status } }
Send requests to https://lifecycle.tools.qzila.com/graphql
Questions about People Lifecycle
Where do alerts go?
Every tool reports through one alert hub. You choose per destination: email, Slack, a webhook, SMS or a Jira ticket — and Service Watch shows the same signals on one board.
Where is my data kept?
The tools run on AWS in the EU (Frankfurt), operated by adcore s.r.o., a Slovak company. A few services they rely on sit outside the EU — Stripe for card payments, Google for analytics after your consent, the threat-intelligence lookups behind Safe Check — and the privacy policy lists each one.
Start with one tool. Add more when you need them.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.