Skip to main content
Book a demo

Connect Lattice to Claude

Give Claude governed access to Lattice’s 22 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Lattice to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Approve Lattice in Runlayer

    Add Lattice from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Lattice’s 22 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Lattice

    Each user signs in to Lattice with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Lattice from Claude

    Lattice’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

22 Lattice tools in Claude

Runlayer policy decides which of these Claude 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.

See all 22 Lattice tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every Lattice call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination