Connect Lattice to Crush
Give Crush governed access to Lattice’s 22 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Lattice to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve Lattice in Runlayer
Add Lattice from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Lattice’s 22 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Lattice
Each user signs in to Lattice with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Lattice from Crush
Lattice’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
22 Lattice tools in Crush
Runlayer policy decides which of these Crush users can call. 15 read data only.
Find ancestors
Find ancestors.
Find employees
Searches for employees in the user's company by name, work email, and/or department.
Find feedback
Retrieves feedback items the user has visibility into.
Find one on ones
Find one on ones.
Find reports
Find reports.
Find reviews
Retrieves reviews the user is permitted to see, filterable by who the review is about, who wrote it, the cycle, direction, submission/sharing status, and date range.
Get current update draft
Returns the user's current-period update draft, with the questions on the form, any answers already saved, the period bounds, and the cadence.
Get draft reviews
Retrieves the open performance review drafts the user is currently authoring.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Lattice call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more
