> ## Documentation Index > Fetch the complete documentation index at: https://support.legora.com/llms.txt > Use this file to discover all available pages before exploring further. # Legora for Slack > Raise a request from Slack, and keep the reply in the same thread. ## Overview You can now use Legora directly when sending a request in Slack. Anyone in your Slack workspace can mention **@Legora** to open a tracked request, such as a contract review, deal support, or a regulatory question. A request posted in a Slack thread usually has no owner and no record. Someone has to copy it into another tool before the work can start. With **@Legora** in the channel, the request is captured from the message itself: * If anything is missing, you’re asked for it in the same thread. * The request is then sent to the right team. Depending on your team’s setup, an owner can also be assigned. * The work is tracked, and the reply comes back to the Slack thread. Requests work in channels and in threads, not in direct messages. That keeps each request visible to the people in the channel. Read the [Privacy Policy](https://legora.com/legal/privacy-policy) for how Legora handles personal data. ## Before you start Mentioning **@Legora** does not require a Legora license. Anyone in the channel can raise a request. Before that works: * A workspace admin installs the Legora for Slack integration. * An admin connects the Slack workspace in Legora. * **@Legora** is in the channels where requests should be raised. After that, a mention in one of those channels is enough to start a request. ## Send a request Once **@Legora** is in the channel, sending a request looks like this: 1. Mention **@Legora** and describe what you need. 2. Attach the files the team should see. 3. Send the message. A reply appears in the thread, with one follow-up question if something is still missing. 4. A ticket is created and posted in the thread. It shows the title, an ID, a summary, the status, and where the request was routed. A Slack message from Avery Koh mentions @Legora and attaches two Word documents: a marked-up Legora GTC for Denizen Ltd, and Schedule A on data residency. Legora replies that the request was submitted to Commercial legal, then posts a card titled “Review Denizen Ltd GTC markup - need to respond to their GC by EOD,” with ID COM-198 created in Legora, a summary, and a status. What happens next: * The team picks up the ticket and works on it. * The answer comes back in the same thread, with any files they send. * The destination is chosen from the message and the files, and replies use the language you wrote in. * Mention **@Legora** again to add context, or to ask for the current status. ## Troubleshooting ### Nothing happens when I mention @Legora? **@Legora** only sees a channel after someone invites it in. Invite **@Legora** to this channel, or send the request in a channel where mentions already get a reply. If it isn’t available anywhere in the workspace, ask an Admin to connect Slack. ### I sent a request in a direct message, and nothing happened? Direct messages are not supported. Post the request in a channel where **@Legora** is present. ### I replied in the thread, but got no response? Only messages that mention **@Legora** are read. Add the mention to your reply. ### There is a reply, but no ticket yet? Some details are still missing. Answer the follow-up question in the thread, and mention **@Legora**. The ticket is posted once the request is complete. ### Can I change a request after it is submitted? Not from Slack. Add a correction or extra context as a reply in the thread, and mention **@Legora**. For a different request, start a new message.