Historical brief · 2026-11-18

Protect sensitive data in your traces: new controls in LangSmith

According to LangChain Blog: LangSmith introduces three new controls to help enterprise teams manage access to sensitive production trace data. These controls allow administrators to restrict visibility into trace inputs and outputs, manage team permissions via user groups, and set trace-level policies using metadata, balancing engineering visibility with security compliance.

Polyemergence editorial artwork · Not a source image

According to LangChain Blog:

LangSmith reports that its new enterprise features resolve the ongoing conflict between engineering needs and security compliance. While engineers require production traces to debug issues and optimize agent performance, security teams must enforce least-privilege access to protect sensitive customer information such as names, payment details, and health records, complying with regulations like GDPR and HIPAA.

The update introduces three core components. First, admins can restrict who views trace inputs and outputs while still allowing engineers to access run trees, latency metrics, and token usage for troubleshooting. Second, user groups enable team-by-team permission management layered on top of existing RBAC and ABAC setups. Third, trace-level access policies can be defined using root run metadata, allowing granular rules such as granting support agents access only to specific customer IDs.

According to LangSmith, these capabilities let organizations retain full data fidelity in their traces without resorting to messy workarounds like duplicate workspaces or redacting data entirely. These features are now available for enterprise plan customers.

View selection rationale
Official releaseStage not established

Importance 54/100

Signal60Structure50Consequence50Confidence86Momentum40
About this brief
Content type
News summary
Source type
First-party / official source
Original source
LangChain Blog ↗
Source published
Process
AI-assisted discovery, translation, summarisation, classification and scoring; standards and corrections are maintained by the editorial desk.
Verification
The original URL and publication metadata are retained. This brief is not independently fact-checked unless explicitly stated.
Published by
Polyemergence Editorial Desk · PolyEmergence Pte Ltd.
Conflict disclosure
No financial or commercial conflict declared.

Editorial standards → · Corrections →

POLYEMERGENCE / EXPLORE

Keep exploring

Follow the topic, not just the headline.

Explore the Artificial Intelligence archive →