Lattice
Use Lattice as the HR record of who works here: everyone's status, manager, department and start date, and who is a Lattice admin. Compare it with Okta and Google to catch leavers whose accounts are still on, new starters with no accounts yet, and people with no manager.
Questions you can answer 15
Each one is a saved query that ships with ConfigView, reading your Lattice data on your own server. Ask it in plain English, SQL, Slack or the API.
- Who are the Lattice admins?
- Which deactivated people still have Lattice admin rights?
- Who can see everyone's reviews in Lattice?
- Who has left according to Lattice but still has an Okta or Google account?
- Which leavers did HR deactivate that IT has not offboarded?
- Are any deactivated Lattice employees still active in Okta?
- Do our new starters have Okta and Google accounts yet?
- Who starts soon according to Lattice, and are their accounts ready?
- Which recent hires in Lattice have no Okta account?
- Which Lattice users are not synced from our HR system?
- Who was added to Lattice by hand?
- Are there contractors in Lattice without an HR record?
- Who has no manager in Lattice?
- Which employees report to someone who has left?
- Who would be missed by manager-based access reviews?
No Lattice questions match that yet. Try a shorter word.
What ConfigView collects from Lattice 2
-
Departments
Lattice's departments, with how many active people each one has.
-
People
Everyone in Lattice - active, invited, not yet invited and deactivated: name, work email, job title, status, manager, department, start date, job level and type, whether they are a Lattice admin, and the employee ID their HR system gave them. Birth dates, gender, reviews, feedback, goals and pay are never collected.