Integrations

One safe handoff, wherever work happens.

Start without installing anything, or connect SecretBridge to a collaboration platform for verified context, organisation policy, and native notifications.

Browser

Create an encrypted public link with no account or installation.

The browser flow is ideal for an immediate handoff. It supports expiry, reveal limits, sender and recipient display labels, and an optional separate passphrase. Labels do not verify identity, and the complete link acts as the access credential.

Create a secret

Slack

SecretBridge uses slash commands, safe message metadata, and verified Slack identities. It asks for the scopes needed to handle commands, send app responses, resolve users, and check conversation membership; it does not request permission to read message history.

Inside a workspace

Open SecretBridge from a conversation and address observed members using Slack context. Workspace installation credentials are stored for that workspace and are revoked from SecretBridge when Slack sends supported uninstall or token-revocation events.

Across organisations

The receiver runs /secretbridge expect and shares the opaque receive ID with the sender. There is no public cross-customer directory.

Add to Slack

Microsoft Teams

Teams installations bind Microsoft 365 identity and conversation context to SecretBridge. The personal app, team, or group-chat scope determines where it is available. In a controlled pilot, a Microsoft 365 administrator uploads the publisher-provided app package if custom apps are permitted.

Current availability: Teams is distributed as a controlled pilot package. This site does not claim a public Teams Store listing until that publication is actually complete.

Opening a protected SecretBridge task or dialog from the conversation keeps the experience connected to Teams while allowing sensitive entry and reveal to happen in a browser-controlled surface.

Teams installation help

Outlook

The Outlook add-in creates a safe email card containing metadata rather than secret plaintext. By default, the reveal link is copied for delivery over a separate channel; embedding it in the email is an explicit choice because forwarding the message would also forward that access.

Outlook organisation activation uses Microsoft identity and fails closed when it cannot verify the tenant.

Ask about the Outlook pilot