Omniscio

Cross-Org Connections (Team Chat Lane C)

Cross-Org Connections is the Team Chat lane that starts a one-to-one DM with any Omniscio user by exact sign-in email — a coworker, or someone in a completely different organization — with the connection forming only once the recipient approves. Covers where to send and approve a request, and the privacy switch that opts you out.

On this page

The shared promise. Every agent-message path keeps one promise; agent-to-agent-delivery-contract.md states it once and says where each path keeps it.

What it is

Connect with any Omniscio user by email — a coworker in the same workspace OR someone in a completely different organization — to start a 1:1 DM. The connection forms ONLY when the recipient approves.

Where to find it

Everything starts in Team Chat, which has a Connections section in its sidebar; the Connect by Email dialog opens from there. A request you receive shows up in that same sidebar section and as a card in your Inbox, where you accept or decline it. Once a connection exists, its conversation sits in the Team Chat sidebar with your other chats. If that person is also a teammate you already DM, they keep one row, and the connection's messages open from a Connection chat row under Main in their topic list. Your own discoverability switch is on your Team Chat self-profile popover — the avatar strip in the sidebar — so you can stop receiving connection requests without leaving Team Chat.

How it behaves

How it works

  1. Request — type a person's exact sign-in email in the Connect by Email dialog (opened from the Team Chat sidebar's Connections section). The request is sent via the globalAuthProfile Cloud Function (requestConnection action).
  2. Approval — the recipient sees a pending request in their Team Chat Needs you list AND as an Inbox item (see connection-request-inbox.md). They can Accept (creates the connection and opens the DM) or Decline (deletes the pending doc so a future re-request starts clean).
  3. Cancel — until it is accepted, a request you sent shows under Sent requests in your Team Chat sidebar with a Cancel button. Cancel runs the withdrawConnectionRequest action on the same Cloud Function: it checks on the server that you sent it, finds the pending request from your own sent record, removes it only while it is still pending (an accepted connection stays), deletes your sent record and lifts the 24-hour "already asked" block so you can ask again. It answers the same way whatever state the other side is in, so it reveals nothing about the address.
  4. Messaging — once accepted, both users can message each other in a 1:1 DM that lives in a top-level connections/{connId} collection, separate from any org's channels. Messages use the same frozen schema as org channels. Reactions, pins, and threads all work on connection DMs (parity with org channels). The lane is bounded on the server: a pair may send 30 messages a minute and 2,000 a day on one connection, and anything past that is removed as it arrives rather than delivered, so a scripted flood cannot drive the other person's sidebar. Ordinary conversation never reaches either number.
  5. Messaging — once accepted, both users can message each other in a 1:1 DM that lives in a top-level connections/{connId} collection, separate from any org's channels. Messages use the same frozen schema as org channels. Reactions, pins, and threads all work on connection DMs (parity with org channels).
  6. Disconnect — either person can end an accepted connection at any time: open the conversation and click Disconnect in its header. The app asks for confirmation first, because it cannot be undone for the pair — the conversation disappears from both sidebars and neither person can send the other a new connection request afterwards (a later request is answered neutrally, so it never reveals that a block is why). It runs disconnectConnection on the same Cloud Function, which checks on the server that you are part of the connection, deletes it, records a block for the pair and writes an audit row naming who disconnected. Your other chats, and the other person's, are unaffected. Turning off the discoverability switch does not do this: that switch only stops NEW requests, so an accepted connection needs this action to end it. Disconnect is on the computer's app; the phone link has no connection mutations.
  7. Deleting or editing a message — the one-line preview of the newest message in a conversation is kept on the connection itself so both sidebars and phones can show it without reading every message. When you delete a message, or edit personal details out of one, that preview is repaired for you: deleting the newest message replaces the preview with your previous message (or removes it entirely when nothing is left), and editing the newest message re-caps the preview to its new text. This happens on the server, so it works the same for the other person's devices and does not depend on the app you are using.

When a connection stops working

If a connection starts refusing Omniscio's messages, the app does not silently switch your connection off. A refusal on its own is not proof the connection is gone — the same refusal code also carries unrelated answers, such as "this copy of the app could not be verified". So before anything is turned off, the app reads the connection itself: only a connection that is genuinely gone, or that is no longer accepted, has its switch turned off and a reason recorded against it.

A connection that is still there keeps its switch ON. If the app cannot confirm either way — the read that would settle it fails, times out, or comes back with that same permission answer that is not about your connection — it holds: nothing is turned off, because being wrong the other way means switching off a connection that works, which you would have no way to notice.

A hold is written to the app's log today, and that is the whole of it: nothing is shown in the UI yet. No card or notice tells you a connection is in this state, and the switch simply stays ON. That is a known gap rather than a safeguard — the card that would report it is not built yet — so do not read the silence as the app having concluded your connection is fine.

How long a direct message is kept

A direct message carries an expiry deadline from the moment it is sent: 730 days (two years) after it was created — the same horizon a channel message gets by default. A connection belongs to no workspace and no organization, so there is no plan-based history window to read; the fixed two-year deadline is the one that applies.

Two things bound it in practice. The deadline is only stamped while plan enforcement is switched on, so with enforcement off a DM carries no deadline at all. And nothing is removed until the database's expiry policy for these messages is enabled on the server, which is an operational step rather than part of the app — until then the deadline is recorded but nothing is deleted at it.

The parent feature — the org channels and the sidebar this lane lives in — is on the Team Chat page. How a pending request is presented in the unified queue is on Connection Request Inbox Items, and the queue itself is described on the Inbox Overview page.

Contract: team-chat-connections-contract.md (C1-C13).

Last verified 2026-11-08