Skip to main content
Book a demo

Connect Paper to Crush

Give Crush governed access to Paper’s 19 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Crush setup guide

Set up

Add Paper to Crush in four steps

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

  1. 1

    Approve Paper in Runlayer

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

  2. 2

    Connect Crush to Runlayer

    Install the Runlayer CLI so Crush can reach Paper, which runs on the user’s machine.

    Crush setup guide
  3. 3

    Sign in to Paper

    Sign in the way Paper requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Paper from Crush

    Paper’s approved tools appear in Crush. Every call is checked against policy and recorded.

Tools

19 Paper tools in Crush

Runlayer policy decides which of these Crush users can call.

  • Get basic info

    Get essential context about the current design: file name, page name, node count, list of artboards with their dimensions, and a list of font families used in the document.

  • Get selection

    Get detailed information about the currently selected nodes, including IDs, names, component types, size, and which artboard they belong to.

  • Get node info

    Get detailed information about a specific node by ID, including its size, visibility, lock state, parent, children IDs, and text content.

  • Get children

    Get the direct children of a node.

  • Get screenshot

    Capture a screenshot of a specific node by ID.

  • Get jsx

    Get the JSX code representation of a node and its descendants.

  • Get tree summary

    Get a compact text summary of a node's subtree hierarchy showing component type, name, ID, and dimensions.

  • Get computed styles

    Get the computed CSS styles for one or more nodes.

See all 19 Paper tools

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 Paper 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

Find another combination