LangSmith Adds Controls for Sensitive Trace Data
LangChain announced three new LangSmith controls for managing access to sensitive production trace data: restricting trace inputs and outputs, assigning permissions through user groups, and defining trace-level policies from root run metadata. Administrators can let engineers retain access to run trees, latency, cost, and other debugging or performance data without exposing sensitive inputs and outputs; the controls are available in LangSmith Enterprise plans.
LangSmith now supports more granular least-privilege access for production agent traces, including customer- or user-scoped policies based on root run metadata.
Key Takeaways
- Control input and output access: engineers can debug with run trees, performance statistics like latency and cost, and other trace data without seeing sensitive inputs and outputs
- Manage access by user groups: organize users into groups within LangSmith and set data access and workspace membership on a group-by-group basis
- Create trace-level policies: use root run metadata on your traces to determine which users can see them
You can’t run agents in production without governing the data they touch. When that data includes sensitive customer information, controlling access becomes a regulatory and contractual obligation. That puts engineering and security requirements at odds. Engineers need production traces to debug issues and improve agent performance. Security and compliance teams need to enforce least privilege: people should only see the data their job requires. That’s why we’ve added three new controls to LangSmith to help teams manage access to sensitive trace data:
- Control who can see trace inputs and outputs (i.e., user messages and model responses)
- Manage team-by-team permissions with user groups
- Set trace-level access policies using metadata