Connect Lattice so Coworker knows your people and reporting lines. Lattice is identity-only — performance content stays out of Coworker entirely.
Lattice Data in Coworker
Indexed into the knowledge graph
Users and departments — builds a verified Person entity for each employee, with department stamped as an HR property
Builds your org chart from reporting lines
Merges each employee's identity with the same human across every other connected source
Available to users, but kept out of the graph
These stay in the raw warehouse, where they power daily digest reports and live chat tools rather than becoming searchable graph content:
Goals and goal-progress updates on public goals (private-goal details are never collected at all)
Status updates with public bodies (non-public status bodies are never collected)
Review cycles, reviews, and feedback — metadata only: who, when, type, and status. The written review and feedback content is never collected.
Never collected
Compensation and salary data, bank details, review and feedback text, private-goal descriptions, identity documents, emergency contacts, birthdays, and home addresses are excluded at the API-scope and code level for every HRIS connector — they never reach the warehouse, the graph, or a prompt.
Before you start
The primary key must be created by a Lattice Admin or Owner
EMEA workspaces need the regional base URL
Lattice is a beta connector — beta connectors may need enabling for your workspace
Connect as an admin
Open Data Sources from the admin settings in Coworker and select Lattice.
Paste an Admin- or Owner-created API key, and set the regional base URL if you are on EMEA.
Save.
Connect as a member
Individual Lattice keys can be added to the pool for resilience, but they do not safely replace the fully scoped admin discovery key.
Good to know
Lattice keys inherit their creator's privileges and Lattice exposes no scope introspection. A non-admin key can authenticate while the employee roster is silently truncated — this is why the primary key must be Admin or Owner.
Tokens are deduplicated by Lattice account, and a failing key is parked without affecting the others.