--- title: "Work on your sites from Discord | Briks" url: https://briks.dev/docs/discord description: "Add Briks to your Discord server to ask for changes and questions, approve steps, publish and hear about your builds in the channels you choose." last_updated: 2026-10-08 --- # Work on your sites from Discord The Briks bot on Discord does what the conversation in the studio does, through slash commands: you ask for a change and Briks builds it. It acts as you, with your role in each workspace, so it can never do more than you could in the studio. 9 minute read Checked against the studio on 8 October 2026 ## Add Briks to your server A workspace's Owner or an Admin connects a Discord server to the workspace. Each server belongs to one Briks workspace, and its channels only ever reach that workspace's sites. A workspace can connect several servers. 1. Open Chats in Settings Where: Settings, Chats Open the workspace's **Settings** from the sidebar. Its **Chats** section lists the Discord servers this workspace has connected. A project's own **Settings** has a **Chats** section too, but that one is the log of your site's chat. 2. Press Add to Discord Where: Settings, Chats Discord opens and asks which server to add Briks to. Discord lists only the servers you can manage. In the server, Briks asks only to see channels, send messages and show links. 3. Choose the server Where: Discord You come back to Settings, which says Briks is in your server. Adding it also links your own Discord to your Briks account, so you can use the commands straight away. A server that is already connected to another Briks workspace can't be added until it is removed there. Settings lists each connected server with who added it and when. ## Link your Discord account Everyone who wants to use the commands links their own Discord once. Briks knows people by Discord's own number for their account, never by a username, which can change hands. With the /link command 1. Run /link Where: Discord In any channel Briks is in, or in a direct message with the bot. Only you see the reply, with a **Link Discord** button. 2. Sign in to Briks and confirm on Discord Where: Briks, then Discord Sign in to Briks if you aren't already. Discord may then ask you to confirm who you are. Finish within 10 minutes, in the same browser. 3. Check your profile Where: Profile, Discord Your profile says your Discord is linked and shows your Discord name. You can also start from the studio: open **Profile** and press **Link Discord** in the **Discord** section. A Discord account links to one Briks account, and an account to one Discord. Linking it to another account moves the link. Anyone who uses a command before linking gets the **Link Discord** button instead, shown only to them. ## Give a channel its site and alerts Each channel works on one site. Run `/sites` in the channel and tap the site: the channel works on it until someone picks another. In a channel, `/sites` lists only the sites of the workspace the server is connected to. In a direct message with the bot, it lists every site you can see, across all your workspaces. Then run `/alerts` and tap each alert to turn it on or off. Every alert is off until someone turns it on: | Alert | What you get | | --- | --- | | Builds finished or failed | The site's name, what changed and its address, or why it didn't work. A failed build is not charged. A build that was stopped, and GitHub sync needing you, come under this alert too. | | Steps waiting for approval | The step, with the buttons to decide it, and a first build waiting for credits, with **Get credits**. | | Domains live or needing attention | When a custom domain goes live, or something needs fixing, with what to do. | | Credits running low | When the workspace has fewer than 20 credits left after a build, at most once a day. | | New form messages | That a message came in, with the form's subject and a link to read it in the studio. What the visitor wrote is never sent to Discord. | | Comments in the Visual Editor | Who commented, or named someone in a comment, and on which page, with a link to it in the [Visual Editor](https://briks.dev/docs/visual-editor). The comment's words are never sent to Discord. People named in a comment also hear it in their own chat with the bot. | | Urgent security findings | An urgent finding of the [Security agent](https://briks.dev/docs/security-agent) or of the checks after a publish, with a link to the security report. | Whatever your alerts, a change, undo or publish you start from a chat is always reported back in that chat. Who sets up a channel Discord shows `/sites` and `/alerts` only to members who can manage the server, unless the server's admins change that in Discord's own settings. Briks then asks for Editor or above in the workspace to choose a channel's site or alerts. In a direct message with the bot, the choice is yours alone. The same choices are in the studio. **Settings**, **Chats** lists each channel that has used a Briks command, with a **Site** menu and a switch for each alert, which Editors and above can change. The switches wait until the channel has a site. Under each channel you see when the last alert was sent, or why it wasn't. ## The commands Discord passes Briks its commands and button presses only, never the rest of a channel's conversation, so everything starts with a slash. As you type a command, Discord shows the box to fill in. | Command | What it does | | --- | --- | | `/sites` | Lists your sites, to pick the one this channel or chat works on. | | `/new` | Starts a new site from a description, holding 50 credits like **New project** does. Put a name before `\|` to choose it, and start with `app` or `dashboard` to make one of those. | | `/status` | The chosen site's state, its address, when it was last published and a link to it in the studio, with any step waiting for you. | | `/change` | Asks for a change in your own words, with a picture if you add one. | | `/ask` | Asks a question about the site, answered at once with no build. | | `/undo` and `/redo` | Go back to the previous version, or bring back the one you undid. | | `/publish` | Publishes the site to production, after you confirm. | | `/agents` | The site's agents, for Owners and Admins: switch one on or pause it, run it now or write to it. | | `/alerts` | Chooses what this channel or chat is told. | | `/link` and `/disconnect` | Link your Discord to your Briks account, or unlink it. | | `/help` | What the bot can do. | Lists, menus and anything only for you, such as `/status` and `/alerts`, are shown only to the person who asked. What a change did is posted in the channel for everyone. ### Changes, questions and pictures Write what you want in the `/change` box. Briks reads it the way the studio does: a question is answered at once with no build, and anything else becomes a change, which sets aside 5 credits like any change. Use `/ask` when you only want an answer. A change A plumber's site > /change Add our emergency number 0113 496 0000 to the top of every page, in bold. The bot says it's working on it. When the change is published, it tells the channel what changed and gives the site's address. To use a picture, add it in the **picture** box of `/change` and say what to do with it, such as "use this in the hero". JPEG, PNG, WebP and GIF pictures work. If a build is already running, your change waits in line, exactly as in the studio. Your changes and questions are kept in the project's conversation, so you can carry on in the studio. ## Approve with a button - **Steps of a first build.** If a first build stops for your approval (the words, a look or a hero), the bot shows buttons: **Approve the words**, one button per look or hero, or **Decide for me** for the questions before building. **Open in the studio** shows the options side by side. To answer in your own words or ask for something different, use `/change`. A change that needs a key shows an **Add** button for each key, which opens the site's Secrets, and **Build**; a first build waiting for credits shows **Get credits**. - **Agent approvals.** When an agent asks before it sends an email, changes your site or publishes a post, Owners and Admins can get the request in a direct message from the bot, with **Approve**, **Reject** and **Look first**. The **On Discord** switch under **Agent approval requests** in **Profile** chooses whether they come there. Once anyone decides, wherever they did it, the buttons go and the message says who decided. See [Approvals and budgets](https://briks.dev/docs/agent-approvals). - **Direct messages.** The bot can only message people who share a server with it. If your profile asks you to, use any Briks command once in a direct message with the bot so it can reach you there. - **Publish.** `/publish` asks whether to publish the site to production, with **Publish** and **Cancel**. If the first draft made up facts, such as figures or quotes, they are listed, and **Publish** confirms they are right. The launch check runs first, and the bot tells you how it went. See [Publish to production](https://briks.dev/docs/publish-to-production). - **Agents.** Pick an agent in `/agents` and press **Write to it**: a box opens for your message, and the agent's answer comes back in the same place. An agent's question has a **Reply** button that opens the same box. Watch out Approving a step sets aside up to 50 credits for the rest of the build, as it does in the studio: what your balance has, down to 5. If you have less than that, the bot says so. See [Approve as it builds](https://briks.dev/docs/approval-steps). ## What Briks keeps - The words of a change or a question join the project's conversation, as if you had written them in the studio. - For each message to and from the bot, Briks keeps only when it was sent, what kind it was and whether it went, never its words, and removes even that after 90 days. - The **Activity log** on the Agents page shows what was done or sent through Discord, in Briks's own words, such as a change asked for or an alert that couldn't be delivered. It goes back 13 months. - A removed server's details are deleted 90 days after Briks leaves it. The [Privacy Policy](https://briks.dev/privacy) has the details. ## Remove Briks or unlink - **Remove a server.** Owners and Admins press **Remove** beside the server in **Settings**, **Chats**. Briks leaves the server, and its channels stop hearing about your sites and lose their settings. Linked Discord accounts stay linked. - **Removed in Discord.** If the bot is removed from the server or loses access to a channel in Discord, Briks notices the next time it sends there and stops trying. Settings then says why alerts aren't reaching that channel. Using any Briks command there starts them again. - **Unlink your Discord.** Press **Disconnect** in **Profile** or run `/disconnect`. The bot then no longer acts for you. - Chats with bots are not end-to-end encrypted. Never send the bot passwords, keys or anything you'd keep secret. Use [Secrets](https://briks.dev/docs/secrets) in the studio for those. A key pasted into a message is cut out before it is kept, and the bot tells you where to add it, with **Open Secrets**. - The bot answers up to 30 messages a minute from each person, and questions are limited to 30 per site every 10 minutes, as in the studio. - The bot is on every plan, and everything costs the same credits as in the studio. ### Can I write to the bot without a command? No. Discord passes Briks only its commands, so use /change for a change and /ask for a question. ### Can I use Briks on Discord without adding it to a server? No. Briks has to be in a server you are in. Once it is, the commands also work in a direct message with the bot. ### Someone in our server can't see /sites. Discord shows /sites and /alerts only to members who can manage the server, unless its admins change that in Discord's own settings. Everyone who has linked can still use the other commands, with their own role. ### The bot says the server isn't connected. Briks was removed from the server, or never added from the studio. An Owner or Admin adds it again from Settings, Chats. ## Read next - [Working on a project **Telegram** Connect Telegram to Briks to ask for changes, get answers, approve steps, publish and hear when builds finish, alone or with your team in a group.](https://briks.dev/docs/telegram) - [AI agents **Hire AI agents** Hire AI agents that look after a live site: 13 kinds led by a Team lead, or your own, each with a schedule and a budget, asking you before they act.](https://briks.dev/docs/ai-agents) - [Workspaces and account **Members and roles** Invite people by emailed link and give each one a role: Owner, Admin, Editor or Viewer. See what each role can do and how many people each plan holds.](https://briks.dev/docs/members-and-roles) - [Building **Approve as it builds** Have a first build stop for you: approve the words, choose one of three looks, then pick a hero from four grey layouts. How to turn it on and what it costs.](https://briks.dev/docs/approval-steps) Still stuck? Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.