Orvine AI
Integrations

Slack

Turn Slack into a capture surface and an ambient interface for organizational memory.

What you get

  • /orvine slash command — ask cited questions inside any channel or DM. Answers respect the asker's workspace role.
  • Thread capture — react to a thread with the Orvine emoji to extract a candidate decision or SOP from the conversation.
  • Notifications — route review tasks, SOP staleness, and continuity alerts into the channels of your choice.
  • Auto-ingest — opt-in, channel-scoped: every message in selected channels is indexed into the workspace memory.

Install

From Settings → Integrations, click Install Slack. You must be a Workspace Admin in both Slack and Orvine. The OAuth flow requests the minimum scope set:

Slack scopes
channels:history       Read messages in channels Orvine is added to
channels:read          Resolve channel metadata
chat:write             Post Orvine answers and notifications
commands               Register /orvine
files:read             Index attached transcripts and decks
reactions:read         Detect the Orvine extract-this emoji
team:read              Resolve workspace identity
users:read             Resolve message authors
users:read.email       Match authors to Orvine members

Permission model

Orvine joins a channel only when explicitly invited. Auto-ingest is disabled by default and must be turned on per channel. Direct messages and private channels Orvine isn't in are never read. Every Slack-sourced artifact carries a citation back to the original message link.

Compliance

On Enterprise plans you can require that Slack content be tagged before indexing — for example, only messages with a #decision or #sop tag are written to memory. This dramatically limits accidental capture of personal or speculative conversation.