Pillar One — Connections

Supported Connectors

PanOps connects to your existing communications infrastructure without changing how anyone works. Ten channels. One intelligence layer. All of it inside your cloud environment.

Live Connectors

Current Connector Coverage

All connectors are authenticated via standard OAuth or API credential flows. No agent software. No endpoint installation. All authentication occurs inside your cloud environment.

Connector	Category	Status	Data Captured
Microsoft 365 Email	Email	Live	Sent, received, threads
Gmail / Google Workspace	Email	Live	Sent, received, threads
Microsoft Teams	Messaging & Video	Live	Channel messages, DMs, calls, meeting transcripts
Slack	Messaging	Live	Public channels, group messages, direct messages (Enterprise Grid)
Google Chat	Messaging	Live	Spaces, messages (requires Business Plus)
Zoom Meetings	Video	Live	Meeting transcripts, recordings
Google Meet	Video	Live	Meeting transcripts
RingCentral	Voice / UCaaS	Live	Call transcripts, voicemail, SMS
Dialpad	Voice / UCaaS	Live	Call transcripts, voicemail, SMS
Zoom Phone	Voice / UCaaS	Live	Call transcripts, voicemail, SMS
OpenPhone	Voice / UCaaS	Live	Call transcripts, SMS
Enterprise Software Systems	Core Systems	Live	Structured records (communications, activity logs, transactions — scope defined per system)

Authentication

How Authentication Works

Every connector authenticates through standard industry-standard flows. Credentials are stored and used entirely within your cloud environment — PanOps never has access to them.

OAuth 2.0

Standard OAuth Flow

Email, messaging, and video connectors (M365, Gmail, Teams, Slack, Zoom, Google Meet) authenticate via OAuth 2.0. The authorization token is stored in your environment only. PanOps initiates the flow; your environment stores the credential.

API Credentials

API Key / Webhook Authentication

Voice and UCaaS connectors (RingCentral, Dialpad, Zoom Phone, OpenPhone) authenticate via platform API keys or webhook delivery. All keys are provisioned into and stored within your cloud environment only.

Credential Storage

Inside Your Environment Only

No connector credentials are transmitted to or stored by PanOps. All tokens and keys live in encrypted storage within your cloud environment, under your encryption keys. PanOps has no copy.

Scope

Minimum Required Permissions

Each connector requests only the permissions required for data ingestion — read-only where possible. No write access to source platforms. No admin access. Scopes are documented per connector during onboarding.

Data Detail

What Is and Is Not Captured

PanOps captures communication content and metadata. It does not capture endpoint activity, file contents, or personal account data outside of business communication channels.

Subject, body, sender, recipient, timestamp, thread ID

Captured for all sent and received messages within the enrolled employee's business email account. Attachments are not ingested. Personal email accounts are not connected.

Messaging (Slack, Teams)

Message text, channel, sender, timestamp

Public channels, group messages, and direct messages are captured. Slack DMs require Enterprise Grid and separate employee consent. Reactions and emoji are not captured.

Video & Meetings

Meeting transcript, attendees, date, duration

Transcripts are generated from recordings or live captions via a self-hosted open-source transcription pipeline. No raw audio or video is retained after transcription. Transcripts are stored in your environment.

Voice & UCaaS

Call transcript, participants, date, duration, voicemail text

Call audio is transcribed inside your environment and the audio is not retained. Voicemail is transcribed from platform-delivered audio. SMS via OpenPhone is captured as text. Personal mobile numbers are not captured.

Privacy

Employee Consent

Every employee whose communications are ingested completes an explicit consent flow before data collection begins. This is not optional — it is required by the PanOps enrollment flow.

Consent Framework

Employees see exactly what is collected — before they agree.

The enrollment flow presents each employee with a plain-language summary of which platforms are connected, what data categories are captured, and who can query it. Consent is recorded per employee per channel and stored in your environment. Consent is revocable at any time by the employee or by an administrator. No communication data is ingested for any employee who has not completed enrollment.

Ready to see Signal in action?We'll walk through exactly which connectors are relevant to your stack and what a full deployment looks like.

Request a Demo