# Generate on-style game assets without leaving Slack > Bring Layer's agent into Slack. Mention Layer in any thread to generate images, video, 3D and audio with your team's styles, reference sets and projects, right in the conversation. --- ## Why connect Layer with Slack Most creative decisions in a game studio are not made in a design tool. They are made in Slack: the art director posts a reference, the UA lead asks for three more variants of the winning hook, a producer wants to know whether the new character sheet is ready. Until now, acting on any of that meant leaving the conversation, opening Layer, and pasting the result back in. With Layer connected to Slack, the conversation is where the work happens. Mention Layer in a thread and describe what you need. The thread becomes a Layer session, the agent answers in it as it works, and what it generates lands in the thread beside the request that asked for it. The people who were already discussing the asset see it arrive, react to it, and ask for the next change in the next reply. For [creative directors](/for/creative-directors) and [art directors](/for/art-directors), this means feedback and iteration live in one place instead of being split between a chat and a tool. For [UA managers](/for/ua-managers) and [marketing teams](/for/marketing-teams), a request for creative variations is answered with the variations themselves. ## The same agent, with your team's context The Layer app in Slack is not a separate bot with a thinner feature set. Every thread is a Layer session, and the agent answering in it is the same one your team works with in the browser, working inside your Layer workspace. That means it already knows what your studio has built up in Layer. Ask for key art "in our house style" and it reaches for the style your team trained. Point it at a reference set and it keeps the new work on-model. Mention a project and it can find the files in it. It chooses the model that fits the request, runs the generation, and posts the result, so a request in Slack gets the same output quality as the same request in the app. ## A thread is a session Every Slack thread you start with Layer is bound to its own Layer session. The first message creates the session and posts a link to it, and every reply after that goes to the same session, so the agent remembers the references, the style and the decisions made earlier in the thread. A thread is the right size for this. A channel runs for months and covers dozens of topics; a thread is one piece of work with a beginning and an end. Keeping one session per thread means each piece of work has its own context, and the character concept in one thread never bleeds into the ad variants in the next. Direct messages work the same way. Send Layer a message and that conversation becomes a session of its own, which is useful for private exploration before sharing the direction in a channel. ## Generated files arrive in the conversation When a generation finishes, its output is posted into the thread. Images, video and audio are uploaded directly, so they display and play inline in Slack and stay under your own Slack workspace's retention and data policies. 3D models arrive as their rendered preview. Anything too large to post inline arrives as a link to open it in Layer. The agent's replies stream into the thread as they are written, so the thread shows that work is under way from the moment the message lands rather than sitting silent until the whole answer is done. Everything that appears in the thread is also saved to the Layer session. Open the session from the link at the top of the thread to see the full-resolution files, keep editing on the canvas, or hand the work to someone who prefers the browser. For [studio leads](/for/studio-leads), that means nothing generated in Slack is lost in the scroll: it is in the workspace, attributed to the person who asked for it. ## Every member acts as themselves Layer matches each Slack member to a member of the connected Layer workspace, so what someone generates in Slack is theirs, uses their permissions, and draws on the workspace's Creative Units exactly as it would in the browser. There is no shared bot account that everyone generates through. The match is made only within the workspace the Slack team is connected to. Someone Layer cannot match is offered a button to connect their Layer account, rather than being given access they have not been granted. For [compliance and legal teams](/for/compliance-legal-teams), that keeps Slack inside the same access model as the rest of Layer. ## Notifications in the channels you choose The same install lets Layer post workspace notifications to Slack. Pick the channels in Layer's notification settings and the team hears there when a style finishes training, a teammate mentions someone in a comment, or the workspace nears its usage limit, without keeping a Layer tab open. Because the agent and the notifications share one connection, there is one thing to install, one thing to reauthorize if Slack access ever lapses, and one thing to disconnect. ## Setting it up Connect Slack takes a workspace admin to Settings → Connectors in Layer. Approving the Layer app in Slack installs it for the whole team and links your Slack workspace to your Layer workspace, and from then on anyone can invite Layer to a channel or message it directly. Nobody else installs anything: each teammate is matched to their own Layer account the first time they mention it. Disconnecting from the same page removes the link. Layer stops answering in Slack and stops posting notifications, and every session created from a thread stays in your Layer workspace. ## Frequently Asked Questions ### How do I add Layer to Slack? A Layer workspace admin opens Settings → Connectors, picks Slack and signs in to the Slack workspace the team uses. That one install gives the team the Layer app in Slack and lets the workspace send its notifications there. Nobody else has to install anything. ### Is the Slack agent the same as the agent in Layer? Yes. A thread in Slack is a Layer session, so it is the same agent you work with in the browser, with the same access to your workspace. It can use your trained styles and reference sets, find the projects and files you point it at, and pick the right model for the job, then generate straight into the thread. ### How do I start working with Layer in Slack? Mention Layer in a channel, or send it a direct message. The thread that message starts becomes a Layer session, and every later reply in that thread goes to the same session, so the conversation keeps its context for as long as the work lasts. ### Where do the generated files go? Images, video and audio are posted into the thread, so they show and play inline. 3D models arrive as their rendered preview. Everything is also saved to the Layer session, which the thread links to, so the full-resolution files and the rest of the work are one click away in the browser. ### Who can use Layer from Slack? Members of the connected Layer workspace. Each person acts as themselves, so what they generate is theirs and draws on the workspace's Creative Units exactly as it would in the browser. Someone Layer cannot match to a workspace member is offered a link to connect their account instead of being served someone else's workspace. ### Can Layer send notifications to Slack? Yes. The same install delivers workspace notifications to the Slack channels you pick in Layer's notification settings, so the team hears when a style finishes training, a teammate mentions them in a comment, or usage nears its limit, without watching a tab. ### Why is a thread a session, rather than a channel? A channel runs for months and covers many topics, so binding it to one session would pile unrelated work into one context. A thread is already one piece of work, which is the size a session should be. ### How do I disconnect Slack? Open Settings → Connectors in Layer, choose Slack and disconnect it. Layer stops answering in the Slack workspace and stops posting notifications there. Your sessions, and everything generated in them, stay in Layer. --- Connect Slack, mention Layer in a thread, and generate your next asset where the team is already talking about it. --- [View original](https://layer.ai/integrations/slack) | [All Integrations](https://layer.ai/integrations)