Skip to main content
Book a demo

Connect Lattice to Claude Cowork

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

Book a demo Claude Cowork setup guide

Set up

Add Lattice to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork 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 Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Lattice’s 22 tools show up in Claude Cowork’s own tool list.

    Claude Cowork 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 Cowork

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

Tools

22 Lattice tools in Claude Cowork

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork 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)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination