Torii Lever Integration - What It Does and When to Use It

The Torii–Lever integration connects Lever (your ATS) with Torii’s SaaS management platform to automate user lifecycle actions, surface license and cost insights, and reduce manual provisioning work. It creates a single system of record for applicant-to-employee transitions so IT, Finance, and Hiring teams see consistent user and license states. This article explains exactly what the integration synchronizes, the technical mechanics, the common business scenarios that justify it, implementation steps, and practical controls to reduce risk and maximize savings.

What the integration synchronizes (at a glance)

• Candidate to user lifecycle Leverages Lever hire/offer events to trigger Torii workflows for provisioning, license assignment, or onboarding tasks when a candidate becomes an employee.
• Provisioning and deprovisioning triggers Automatic creation, assignment, suspension, or removal of SaaS access based on Lever hiring, termination, or role-change events.
• User attribute mapping Syncs core fields (email, name, role, department, start date) to support accurate license assignment and cost attribution.
• Audit and status updates Logs actions and sync statuses back to Torii for license utilization tracking and to Lever for HR visibility.

Core capabilities enabled by Torii + Lever

When to use this integration (practical scenarios)

• High hiring volume If you hire frequently, automating seat assignment and onboarding prevents bottlenecks and reduces time spent on repetitive tasks.
• Distributed app ownership When multiple teams own SaaS subscriptions, the integration ensures consistent provisioning rules and accurate cost attribution.
• Tight security/compliance requirements Use it to enforce timely offboarding and maintain auditable access logs tied to hiring events.
• Desire to reclaim spend Organizations aiming to identify and reclaim unused licenses will benefit because Lever events provide reliable hire/termination signals.

Implementation checklist (step-by-step)

• Map business rules Document which Lever candidate statuses (e.g., offer accepted, hired, declined) should trigger which Torii workflows and which app licenses map to which job roles.
• Configure authentication Create secure API credentials or enable SCIM/webhooks in Lever and add them to Torii with least-privilege API keys.
• Define field mappings Map Lever fields (email, department, title) to Torii attributes to ensure correct license and cost assignment.
• Test in a sandbox Run a pilot with a small group to validate provisioning, offboarding, and error handling before full rollout.
• Monitor and iterate Track sync success rates, provisioning times, and license utilization; refine rules as you learn.

Data flow and synchronization specifics: The integration typically relies on Lever webhooks for real-time events (hire/offer/withdrawal) and Torii APIs to execute provisioning workflows. Field-level mappings are evaluated at event time to determine the correct actions; Torii stores an authoritative SaaS system-of-record to reconcile later. Practical tip: implement idempotent operations and event replay capability — this reduces duplication, handles transient API errors, and ensures consistent state even if events are delivered multiple times.

Security and governance controls to apply

• Least-privilege API keys Grant Torii only the permissions it needs in Lever (read candidate/hire events and limited user writes) and rotate keys regularly.
• Audit logging Enable detailed logs in Torii for every action taken from a Lever event so you can trace who/what changed access.
• Approval gates For sensitive apps, require manual approval steps in Torii that the webhook triggers but won’t auto-complete without human sign-off.
• Retention policies Define how long candidate and provisioning data persists to align with privacy requirements.

Sample use cases with examples

• Pre-boarding access When an offer is accepted in Lever, Torii assigns core tools (email, SSO, collaboration app) and schedules access delivery so users can start on day one.
• Immediate offboarding Upon termination recorded in Lever, Torii revokes SaaS access and flags licenses for reclamation, removing orphaned seats within hours.
• Department-level budgeting Torii tags new hires by department from Lever and continuously updates license spend dashboards for accurate departmental budgeting.

Metrics to track after integration

Common pitfalls and how to mitigate them

• Role mismatch Pitfall: Lever job titles or departments don’t map cleanly to Torii provisioning rules. Mitigation: Standardize source fields in Lever and add a normalization step inside Torii mapping.
• Over-automation Pitfall: Auto-provisioning sensitive apps without approvals. Mitigation: Add approval gates for high-risk tools and keep manual overrides available.
• API rate limits Pitfall: High-volume hiring bursts exceed API quotas. Mitigation: Implement batching, backoff/retry logic, and coordinate with vendors for higher quotas if needed.
• Duplicate accounts Pitfall: Candidates with multiple emails create duplicate user records. Mitigation: Use stable unique identifiers and canonicalize email addresses where possible.

Troubleshooting checklist (quick steps)

• Verify Lever webhook events Confirm Lever is emitting events for the candidate status you expect and check payload contents for mapped fields.
• Inspect Torii logs Look for errors, timeouts, or rejected actions; logs usually identify permission or mapping issues.
• Replay events If available, replay the webhook event after fixing mapping or permission errors to re-run the workflow.
• Confirm API credentials Ensure API keys haven’t expired or been rotated and that permissions align with required read/write scopes.
• Validate idempotency Check that retries won’t cause duplicate provisioning; add idempotency keys if necessary.

Best practices for rollout and governance

• Start with a pilot Begin with one department or a handful of applications to validate mappings and workflows before scaling.
• Define ownership Assign a cross-functional owner (HR/IT/Finance) who can approve mapping changes and monitor metrics.
• Document workflows Maintain clear documentation of triggers, mappings, escalation paths, and approval gates for auditability.
• Schedule periodic audits Quarterly reviews of license utilization and mapping rules prevent drift and reclaim spend.

Frequently asked questions