Work on your sites from Discord

#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.

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.

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:

Whatever your alerts, a change, undo or publish you start from a chat is always reported back in that chat.

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.

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.

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.
• 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.
• 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.

#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 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 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.