Omniscio documentation
Browse all documentation
  1. Getting Started13
  2. Sessions & Agents115
  3. Inbox & Notifications59
  4. Projects & Tasks95
  5. Automation & Scheduling75
  6. Knowledge & Memory26
  7. AI Features60
  8. Integrations100
  9. Plugins & Marketplace33
  10. Cloud & Teams56
  11. Settings & Customization58
  12. Account & Billing28
  13. Troubleshooting84
  14. CLI & API Reference22
  15. Legal & Policies4
  16. Uncategorised22

Connection Request Inbox Items

A Team Chat connection request arrives as a row in the unified inbox, even for someone who has never switched Team Chat on, so a request is never missed. Covers where the row and its detail pane sit, what Accept, Decline and Dismiss each do, and why dismissing does not answer the request.

What it is

When someone sends you a Team Chat connection request, it appears as an inbox item — even if you haven't enabled Team Chat in Labs. This ensures connection requests are always discoverable through Omniscio's central attention funnel.

Where to find it

The request shows up in the unified inbox, as an ordinary row in the list you already scan for anything that needs you. Right-clicking it or opening it gives the full pane described below. The same pending request is also listed in Team Chat's own Connections section, so either place will do.

Where it lives in the UI

  • Inbox: Connection requests appear as standard inbox rows with an amber "needs attention" dot
  • Detail pane: Clicking the row opens an approval pane with the requester's name, avatar, email, and Accept/Decline buttons
  • Team Chat sidebar: The existing Connections section also shows pending requests (both views share the same Firestore source)

How it behaves

How it works

Accepting a connection request

  1. Click the inbox item to open the detail pane
  2. Click Accept
  3. If Team Chat isn't enabled yet, it auto-enables in Labs
  4. The app navigates to Team Chat with the new conversation open
  5. The inbox item disappears (Firestore doc status changes)

Declining a connection request

  1. Click the inbox item to open the detail pane
  2. Click Decline
  3. The Firestore doc is deleted, the inbox item disappears

Dismissing (archiving) an inbox item

  • Dismissing an inbox item snoozes it — it does NOT accept or decline the request
  • The connection request remains pending in Firestore
  • Undo restores the inbox item

For agents

Technical details

  • Integration: connection-request (approval-routed, registered under the team-chat entry in INTEGRATION_REGISTRY)
  • Data source: Firestore connections collection via useConnectionsListener
  • Projector: connectionRequestSelectItems() in connection-request-inbox-items.ts
  • The connections listener runs for ALL authenticated users, not just those with Team Chat enabled
  • Acting from either the inbox or the Team Chat sidebar resolves the item in both places (same Firestore source)

Related

Accepting a request lands you in the messenger itself, which has its own page — Team Chat — and the list this row appears in is described on Inbox overview.

See also: Team Chat for the built-in messenger this connects to, and Inbox overview for how the unified inbox itself works.

Last verified 2026-09-23