← Back to Presence

Connector readiness

Verify people where the work already happens.

Your teams keep using Google Meet, Zoom, Teams, Slack, Okta and SAP. Presence checks the person at the moment something consequential is about to happen, and does only what that platform genuinely permits.

Web, meetings, collaboration, identity, and ERP

These labels distinguish what is live, what is pilot-ready, and what still needs a real-platform validation.

LiveSelf-connectNot yet
Available now

Web

Check the person in your own web app, before the approve button does anything.

What it can do on the call
Let it through, ask for another check, send it to a reviewer, or stop it outright.
What the platform will not let us do
A signed record of every decision — including the ones you chose not to act on yet.
Live test pending

Google Meet

Verify the consenting participant from their local Meet self-view with the Presence browser extension.

What it can do on the call
Streams bounded liveness telemetry to Presence and locks the consequential action when the server requires more proof.
What the platform will not let us do
The extension path is built and covered by automated tests. Its first authenticated, in-call Google Meet validation is still pending.
Connect it yourself

Zoom

Verify who is actually on the call, using Zoom's own events.

What it can do on the call
Locks the approval button immediately. Removing someone from the call needs Zoom to grant moderation first.
What the platform will not let us do
Sign-in and event handling are built. Our Marketplace listing is in review with Zoom, which is our job, not yours.
Connect it yourself

Microsoft Teams

Your Microsoft admin approves Presence once, and everyone joining a call is verified from then on.

What it can do on the call
Only ever does what your organization has granted it — never more.
What the platform will not let us do
Sign-in, renewals, and health checks are built, and your admin's approval is the only step.
Connect it yourself

Slack

Your security team gets the case, the evidence, and the approve or deny buttons in a Slack channel.

What it can do on the call
Approvals and alerts only. Slack gives nobody the ability to mute or remove from a Huddle, so we do not claim it.
What the platform will not let us do
Sign-in, key rotation, request signing, replay protection, and a required reason on every decision are all built.
Connect it yourself

Webex

Verify who is on the call, using Webex's own events for your organization.

What it can do on the call
Mute or remove, using host permissions we have already validated on our own org.
What the platform will not let us do
Sign-in, token renewal, per-install signatures, duplicate handling, and health checks are all built.
Connect it yourself

Okta

Check the person before a sensitive identity change goes through — a password reset, a privilege grant.

What it can do on the call
Allow, ask for more proof, or deny. Their sessions are only cleared once a block actually takes effect.
What the platform will not let us do
Service credentials, request signing, replay protection, and signing people out are all built.
Workflow setup

SAP S/4HANA

Put a check in front of a release step in your existing SAP workflow.

What it can do on the call
Answers release, hold, or reject — SAP enforces it before anything is committed.
What the platform will not let us do
Workflow contracts, encrypted credentials, freshness checks, and replay handling are built. Still needs validating on a live tenant.

Bring your execution surface

One adapter contract, without a second policy engine.

ERP, banking, identity, commerce, and collaboration systems can map actors and actions into the same Presence decision boundary. Decionis remains the policy authority.

Open developer workspace →

How it works

Keep the workflow people already know.

Presence runs inside the tools your people already use. Your existing approval rules stay where they are — we do not become a second place to configure policy, and any managed browser extension or connector asks for no more access than its action needs.

  1. 01

    Who is actually there

    The person on the call is matched to the account they are claiming.

  2. 02

    What they are about to do

    A $25M transfer is treated differently from joining a meeting.

  3. 03

    Whether it should proceed

    Your policy decides, and you get a signed record of why — including the times you chose not to act on it.

  4. 04

    What happens next

    Lock the approval button, mute, or remove — never more than the platform genuinely allows.

Connect one in a few minutes.

Start a sandbox in watch-only mode today, or talk to us first about what a meeting platform will and will not let us do on your calls.