Security & compliance

Sensitive & restricted conversations

Updated on Oct 5, 2026 · 1 minute read

Not every internal conversation belongs in a company-wide tool. A compensation review, a performance conversation, a legal strategy call, a security incident — these are need-to-know by nature. ArcGlass recognizes conversations like these automatically, in both meetings and emails, and keeps them from being surfaced across the company. The intent is simple: the useful, shareable conversations flow; the confidential ones don't quietly leak.

The sensitivity classifier

After a conversation is analyzed, a sensitivity classifier assesses whether it is a confidential, internal, need-to-know discussion. It recognizes the categories enterprises most care about — among them:

HR & performance — reviews, PIPs, disciplinary matters.
Compensation — pay, equity, bonuses, offers.
Workforce — reductions, reorganizations, restructuring.
Legal — disputes, counsel, privileged strategy.
M&A & finance — deals, diligence, material financials.
Security incidents — breaches and investigations.
Executive strategy — confidential leadership planning.

🛡️

Conservative by design. The classifier is tuned to act only when it is confident a conversation is genuinely confidential, and to do nothing when it isn't sure. It would rather leave a borderline conversation in place than hide real work — so a normal customer call is never swept up. Every automated decision is recoverable (below).

What happens to a flagged conversation

You choose, per organization, how a conversation the classifier flags as sensitive is handled. There are three options:

Keep out of company-wide analysis (the default) — the conversation is removed from the shared workspace and recorded as a reversible tombstone, so it never feeds org-wide memory or insights. Nothing is lost permanently; an owner can restore it.
Restrict to attendees — the analysis is kept, but made visible only to the people who were actually in the conversation. The room keeps its notes; the rest of the company never sees it.
Process normally — turn the screen off and treat every conversation like any other. Appropriate for teams that don't record confidential matters in the first place.

This runs before a conversation is folded into any company-wide memory or cross-account intelligence, so a sensitive discussion is handled at the door — not after it has already propagated.

Restricted conversations

A restricted conversation (from the "restrict to attendees" mode, or set manually) stays in ArcGlass but is governed by a strict attendee-only rule: only the people who took part can open it. It is hidden from everyone else in the organization — including people who would otherwise see it through their data scope. Viewing conversations that have been restricted org-wide is reserved for the Organization Owner.

Always reversible

Because the classifier acts automatically, nothing it does is final. Conversations it set aside are listed on the owner-only Sensitive Conversations tab in the Admin center, where the Organization Owner can review each one and restore it with a click. The decision is auditable, and the content is never destroyed as part of the automated screen.

👤

Reviewing and restoring set-aside conversations is an Organization Owner capability — the same person who holds the organization's other most-privileged controls. It is never granted to administrators who don't otherwise have access to conversation content.

How it fits the access model

Sensitivity screening is a layer on top of roles and data scope, not a replacement for them. Roles decide what each person can do; data scope decides which conversations they can see by reporting line; and the sensitivity classifier removes or restricts the handful of conversations that shouldn't be in the shared picture at all — regardless of role or scope.

SecurityLeast-privilege data access → SecurityAccess control & roles → AdminAdmin center →