Intake
Connect Slack to Intake in Irys
Plenty of legal work never reaches a mailbox. It is asked for in a channel. Connecting Slack makes those asks arrive on the register the same way email does, so the request is on the record instead of scrolling away.
This is Slack as a source of work. It is a different thing from using Slack inside a matter, and connecting one does not connect the other.
Connect it
You connect Slack once, then choose what it watches. The sign-in is the same one used under Settings, so a workspace that has already approved Irys will not be asked again.
Open the sources page
From the register header, open the intake processes and sources page. Slack sits alongside your intake mailbox, Uploads and Sign.
Sign in with Slack
Use your work account. The first time anyone connects, your Slack administrator may need to approve Irys for the workspace.
Pick the channels
Tick the channels you want watched. The list covers the channels you are already in, public and private, with private ones marked. Select all is there if you want everything.
Decide about direct messages
Direct messages are a single option, not a list of people. Ticking it watches every one-to-one DM sent to you, including conversations that start later. Leave it off and only channels are watched.
Save
Saving needs at least one thing ticked, a channel or direct messages. From that moment, new messages in what you picked arrive as items.
If your Irys workspace is shared with other people, watching your direct messages puts those messages and their attachments in front of everyone in that workspace. The setup screen says so next to the option, and ticking it is how you accept that. If your DMs carry anything you would not put in a shared register, leave the option off and pick channels instead.
What becomes an item
A new message in a watched channel becomes one item on the register. It does not need a file attached. A message with files brings them in as the item's documents, and a message without files comes in as the request itself.
A thread is one item. Replies posted under a message that already became an item are added to that item rather than starting a second one, so a conversation that runs for a day stays in one place.
Short acknowledgements do not create items. A reply that is only a word of agreement, a thanks, or an emoji is skipped by a fixed list, with no judgement call involved. Short genuine requests are not caught by this, because the rule looks at what the message says rather than how long it is.
Intake watches from the moment you save. Nothing posted before that is pulled in, so connecting a busy channel does not drag months of old history onto the register.
What Irys does in Slack
Intake listens, and that is all. It does not post, reply, or delete anything in the channels you pick. Reading is the whole of what it does there: it needs message history and the ability to download a shared file, and nothing beyond that.
Managing the connection
The Slack card on the sources page shows the workspace and how many channels are being watched, and carries the controls for changing them. There is also a way to pull Slack in immediately rather than waiting for the next scheduled check.
Disconnecting Slack is wider than Intake. It removes the Slack workspace from Intake in every workspace it is connected to and disconnects the underlying Slack integration, so anything else relying on that connection stops until it is reconnected. Items that already arrived stay on the register.
Where Slack items go next
A Slack item behaves like any other item once it lands. It is read on arrival, Irys says what it is, pulls the facts out with citations, and routes it. From there it takes one of the same five paths out: assign it, make it a matter, send it to Sign, open it in Workbench, or record that it went to outside counsel. See How requests are sorted.