Decision channels
Decisions get made in a Slack thread, a Discord server, a forwarded email, a web chat nobody has an integration for — and then they live nowhere. A decision channel is a way for one of those messages to reach Pragma's sorting pipeline, where it is read once and turned into suggestions: the item it implies, the link it belongs on, the transition it asks for.
Whatever channel a message arrives by, it lands in the same place — your Emails to review list — and the suggestions are answered the same way.
Two ways in
| What it is | What it means | |
|---|---|---|
| Connected capture | Pragma reads with a credential you stored — a connected mailbox | Everything is read, and Pragma decides what is relevant. Automated senders and irrelevant mail are filtered out. |
| Gesture capture | You point at one message and ask for it to be sorted | The pointing is the judgement. No relevance check to fail, no automated-sender rule to fall foul of — forward a newsletter and it is sorted, because forwarding it was the decision. |
Every channel on this page is gesture capture. The connected mailbox is the one connected-capture channel, and it is documented inside the app under Settings → Mailbox.
The channels
| Channel | Gesture | Set up |
|---|---|---|
| Slack | The Sort into Pragma message shortcut | An administrator installs the app; each member claims their Slack account |
| Discord | The Sort into Pragma message command | Each member links their Discord account; a server install is optional |
| Forward an email | Forwarding a message to your own capture address | Nothing to install — the address is already yours |
| Browser extension | Right-click a selection, or open the panel on a mailbox page | Sign in to Pragma from the extension |
Next on the roadmap: Microsoft Teams, Google Chat, WhatsApp, Telegram and a generic inbound webhook.
Who Pragma takes you for
A button pressed on a Pragma card outside the web app — Apply, Dismiss — runs under your own Pragma account, with your permissions and your name in the history. Never under the account of whoever installed the app.
That is what claiming your chat account is for. Until Pragma can name the person who pressed, a card can show what it found and can apply nothing: an unlinked member is asked to link, and nothing happens on their behalf.
Two documents carry this, and they answer different questions:
- A channel identity binds one external user to one Pragma account. It says who pressed the button. It is yours, it is the same in every organization you belong to, and no administrator can see or create it for you.
- A channel installation binds one external workspace to one organization. It says which organization a gesture files into, and it holds the credential Pragma acts with there. It is the organization's, and only its owner sees it.
Membership is re-checked at every gesture and at every press, never assumed from either document.
What Pragma does not read
Pragma never watches a conversation. There is no channel history scope on the Slack app, no standing page permission in the browser extension, and no polling of anything. The only message Pragma sees is the one somebody pointed at.
Getting access
Message sorting is switched on per organization rather than by plan. If Settings → Chat apps or Settings → Mailbox does not show it yet, write to contact@pragma.pm and we enable it for your organization.