Lens connects to the systems your team already uses so it can read context from where work actually happens. This page explains how those connections work, what Lens reads from each one, and how to disconnect at any time.

How connections work

Every Lens integration uses OAuth, the standard authorization protocol that lets you grant Lens access to a system without ever sharing your password.

When you connect a system:

1. You're sent to the provider's official login (Slack, Salesforce, etc.) and sign in there.
2. The provider shows you the exact scopes Lens is requesting before you approve.
3. Once approved, the provider issues a token to Lens. Lens stores that token securely; it does not store your password.
4. You can revoke the token at any time from your Lens admin console or directly from the provider's app management screen.

We use a trusted connector platform (Composio) to broker these OAuth flows. This means the same proven authorization standards used by millions of users every day apply to your Lens connections.

Universal rules across all connectors

These apply to every system Lens connects to:

• Read-only by default. Lens does not write to a connected system unless a specific feature requires it and you have explicitly enabled that feature.
• Minimum scopes. We request only the permissions needed for the feature you've turned on. We don't ask for blanket access.
• Admin-controlled. Only users with the Admin role in your organization can connect, modify, or remove integrations.
• Revocable in seconds. Disconnecting an integration immediately stops Lens from reading new data from that source.
• Auditable. Connection events are recorded and visible to Admins.

Available integrations

Slack ✅ Available

What Lens reads:

• Messages and metadata from channels you've authorized Lens to access