---
title: "Briks documentation: guides for every feature | Briks"
url: https://briks.dev/docs
description: "Step by step guides for every part of Briks: your account, the dashboard, writing a brief, changes, publishing, domains, forms, data and teams."
---

Documentation

# Everything Briks does, explained step by step

Plain guides with walkthroughs and worked examples, from your first brief to your own domain. Each one was checked against the studio as it works today.

## New to Briks? Start here

New to websites? Read [Briks in plain words](https://briks.dev/docs/plain-words) first: the words you will see, and the jobs Briks does for you.

1. [**What Briks does** Briks plans, designs, builds, checks, hosts and publishes websites, web apps and dashboards from a plain description. What it does, and what it cannot do yet. *Read the guide*](https://briks.dev/docs/introduction)
2. [**Create your account** Sign up with your email or Google, confirm the link we send, sign in, join a workspace from an invitation, and see where your 50 free credits come from. *Read the guide*](https://briks.dev/docs/create-your-account)
3. [**Exploring the dashboard** A guided tour of the Briks dashboard: the navigation, Home, Projects, Templates, Agents, Jump to, notifications, your credits and the tabs inside a project. *Read the guide*](https://briks.dev/docs/exploring-the-dashboard)
4. [**Your first site** Follow one small bakery from New project to a preview on briks.live, a first change in the chat and Publish to production, with every screen shown in order. *Read the guide*](https://briks.dev/docs/your-first-site)

## Getting started

Make an account, find your way around and publish your first site.

- [**Briks in plain words** New to building a website? The words Briks uses everywhere, from credits to domains, and the jobs Briks does for you, such as hosting, certificates and checks.](https://briks.dev/docs/plain-words)
- [**What Briks does** Briks plans, designs, builds, checks, hosts and publishes websites, web apps and dashboards from a plain description. What it does, and what it cannot do yet.](https://briks.dev/docs/introduction)
- [**Create your account** Sign up with your email or Google, confirm the link we send, sign in, join a workspace from an invitation, and see where your 50 free credits come from.](https://briks.dev/docs/create-your-account)
- [**Exploring the dashboard** A guided tour of the Briks dashboard: the navigation, Home, Projects, Templates, Agents, Jump to, notifications, your credits and the tabs inside a project.](https://briks.dev/docs/exploring-the-dashboard)
- [**Your first site** Follow one small bakery from New project to a preview on briks.live, a first change in the chat and Publish to production, with every screen shown in order.](https://briks.dev/docs/your-first-site)
- [**Credits and plans** How Briks credits work: holds of 50 and 5, charges for the work done, estimates and builds that wait, what happens at zero, and what each plan includes.](https://briks.dev/docs/credits-and-plans)
- [**Words we use** Plain definitions of the words used across the Briks docs, from A/B test and brief to webhook and workspace, each linked to the page that explains it in full.](https://briks.dev/docs/glossary)

## Building

Describe what you want and steer how Briks builds it.

- [**Start a new project** Every choice on the New project page, step by step: the kind of project, your brief, a site you like, brand, pictures, build switches and what starting costs.](https://briks.dev/docs/new-project)
- [**Writing a good brief** What to put in a brief so the first build lands: the business, its audience, the pages, the main action, facts and tone, with six before and after examples.](https://briks.dev/docs/writing-a-brief)
- [**Questions before building** Before a first build is planned, Briks asks which pages to make and what your brief leaves open. How to answer, use Decide for me or turn extra questions off.](https://briks.dev/docs/questions-before-building)
- [**Build from a site you like** Add one site and up to six screenshots you like. Briks reads its layout, spacing, type, motion and menus, then builds yours in that spirit without copying.](https://briks.dev/docs/build-from-sites-you-like)
- [**Pick a look** See three looks before your site is built, each a board of colours, type, corners, a button and cards set with your own hero words, then build the one you pick.](https://briks.dev/docs/pick-a-look)
- [**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)
- [**Watching a build** Follow a build as it plans, writes and publishes, watch your pages fill in, stop a build safely, and learn what is checked and what a failed build costs.](https://briks.dev/docs/watching-a-build)
- [**Pictures** Choose how your site's pictures are made, add your own photos and logo, replace any picture without spending credits, and fix a picture that is wrong.](https://briks.dev/docs/pictures)
- [**Web apps and dashboards** What the App and Dashboard kinds build, where their records live, what is not available yet, with worked examples for bookings, stock and a café's orders.](https://briks.dev/docs/web-apps-and-dashboards)
- [**Skills** Give Briks guidance it follows on every project in your workspace, such as your tone of voice, house facts and naming rules. Add, check and switch off skills.](https://briks.dev/docs/skills)

## Working on a project

Change, compare, test and roll back what you built.

- [**The project page** A guided tour of a project in the Briks studio: the conversation, the live preview and its screen widths, the tabs under the top bar, Settings and Publish.](https://briks.dev/docs/the-project-page)
- [**Making changes** How to change your site by writing to Briks: what to say, adding pictures, what a change holds and costs, inner pages, queued requests and fixing a miss.](https://briks.dev/docs/making-changes)
- [**Visual Editor** Click anything on your own page to change its words, links, pictures, look, sections and pages, work on it with your team, then publish with no credits used.](https://briks.dev/docs/visual-editor)
- [**Asking questions** Ask Briks about your site, its visits or Briks itself in the chat you use for changes. Answers come at once, with no build. What it knows and what it won't say.](https://briks.dev/docs/asking-questions)
- [**Versions, undo and redo** Every build and change is saved as a version of your site. Undo a change, redo it, or put any earlier version back live exactly as it was, with no credits held.](https://briks.dev/docs/versions)
- [**A/B tests** Test a saved version of your site against the live one: start it from Versions, see which converts more visitors, then keep the winner. With a worked example.](https://briks.dev/docs/ab-tests)
- [**Your site's code** Browse, edit and publish your site's code in the File Explorer on every plan. On a paid plan, download any version as a zip, and see what it leaves out.](https://briks.dev/docs/code)
- [**GitHub sync** Connect a GitHub repository, so each version you publish is committed there and each push to its branch is checked and published on your site.](https://briks.dev/docs/github)
- [**Sharing a preview** Send someone your site's preview address, invite teammates to follow the work, or share a read-only analytics link with no sign-in, and take it back later.](https://briks.dev/docs/sharing-a-preview)
- [**Project settings** Rename a project, add its logo and favicon, set the Built with Briks badge, list it in Made with Briks, set the rules builds keep to, copy, move or delete it.](https://briks.dev/docs/project-settings)
- [**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)
- [**Discord** 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.](https://briks.dev/docs/discord)

## Publishing and domains

Go from a preview to your own domain.

- [**Preview and production** How a Briks site moves from a preview at its briks.live address, kept out of search, to production, where search engines can list it and forms email you.](https://briks.dev/docs/preview-and-production)
- [**Publish to production** Take a Briks site from preview to production: what the launch check reads, what blocks a launch, how to fix each finding and how to go back to preview.](https://briks.dev/docs/publish-to-production)
- [**Connect your domain** Connect a domain you own to a Briks site: the three DNS records to add, how providers name them, what each status means and how to remove a domain.](https://briks.dev/docs/custom-domains)
- [**Your site's address** Every Briks site gets an address at briks.live. How the name is chosen, the rules a new name must follow, how to change it and what happens to the old one.](https://briks.dev/docs/site-address)
- [**Published versions and deploy hooks** See every version your site has published, restore one, and make deploy hooks: private addresses that publish your site again when another tool calls them.](https://briks.dev/docs/publish-history)
- [**Search engines** What every Briks site in production gives search engines: titles, descriptions, a sitemap, robots rules, structured data and fast pages, plus your own steps.](https://briks.dev/docs/search-engines)

## Your site's features

Analytics, chat, forms, email, sign-in, payments, media, storage and social posts.

- [**Analytics** See who visits your site, where they come from and what they do, counted without cookies. Ask about your visits in plain words, set goals and get weekly emails.](https://briks.dev/docs/analytics)
- [**Chatbot** Switch on a chat that answers visitors from your published pages, passes what it cannot answer to a verified email, and keeps every chat for you to read.](https://briks.dev/docs/chatbot)
- [**Forms** Add a form to your Briks site, test it in preview, find every entry in the studio, get each one by email in production and pass them on with a webhook.](https://briks.dev/docs/forms)
- [**Site email** Let your site send confirmations and replies from its own address on emails.briks.live, choose where replies go, and track sending against a monthly allowance.](https://briks.dev/docs/site-email)
- [**Sign-in and payments** Give your site's visitors their own accounts and take one-time payments and subscriptions through your own processor, with every key kept on the site's server.](https://briks.dev/docs/sign-in-and-payments)
- [**Media library** Upload your own pictures and videos once to the workspace media library, place them on any project from the prompt box, and swap pictures on a site for free.](https://briks.dev/docs/media-library)
- [**Image editor** Make social posts, stories, thumbnails and pins in your site's colours at each platform's exact size, or describe one and pick from three designs.](https://briks.dev/docs/image-editor)
- [**Storage** Keep files for your project, share them by link or through a public folder, see where your plan's storage goes, and download everything as a .zip file.](https://briks.dev/docs/storage)
- [**Marketing and social posts** Connect your X and LinkedIn profiles, write a post once with a version for each, schedule it on the calendar and see the visits and enquiries it brought.](https://briks.dev/docs/marketing)

## Data and automation

Records, backups, schedules, webhooks, secrets and logs.

- [**Database** Find what your site stores, edit and add records by hand, and download collections as JSON or CSV, with who can do what and the limits that apply.](https://briks.dev/docs/database)
- [**Backups** What Briks keeps of each project: code versions, database restore points and nightly copies. How to restore, how to download and what each copy holds.](https://briks.dev/docs/backups)
- [**Scheduled tasks** Run a scheduled task on your site at set times: a morning summary, a weekly tidy up. Write a schedule, read each run, fix one that fails, and see plan limits.](https://briks.dev/docs/crons)
- [**Webhooks** Send a signed message to another tool when your site is published, a form is sent or a record changes. Payloads, signatures, retries and deliveries explained.](https://briks.dev/docs/webhooks)
- [**Secrets** Keep API keys and passwords your site's code needs on the site's server, never in pages or downloads. Add, change and remove them, and the rules Briks enforces.](https://briks.dev/docs/secrets)
- [**Logs** Read the build log and the last day of your site's requests, filter by level or status, and track down a failing form, a failing job or a slow page.](https://briks.dev/docs/logs)

## AI agents

Hire agents that look after a live site, lead them and decide what they may do.

- [**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)
- [**Team lead** The Team lead plans your agents' week from your goals, waits for your approval, hands each task to the agent who can do it, and sends you one stand-up.](https://briks.dev/docs/team-lead)
- [**Approvals and budgets** See what agents ask before they act, approve it in the studio, by email or on Telegram, choose what they may do alone, and set the budgets that cap their spend.](https://briks.dev/docs/agent-approvals)
- [**Security agent** Hire the Security agent to check your site's code, keys and live pages, hear in plain words what it finds, and have the Builder fix what you approve.](https://briks.dev/docs/security-agent)

## Workspaces and account

Teams, roles, clients, billing, templates and your profile.

- [**Workspaces** A workspace holds your projects, members, media, skills, plan and credits. Create one, switch between them, rename one and delete one you no longer need.](https://briks.dev/docs/workspaces)
- [**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)
- [**Handing a site to a client** There is no handover button: you hand a workspace over by making your client its Owner. A walkthrough for agencies, with plans, credits and domains covered.](https://briks.dev/docs/handing-over-to-a-client)
- [**Billing** See your plan and credits on the Billing page, buy a plan at checkout monthly or yearly, move up or down, cancel, and find your receipts and invoices.](https://briks.dev/docs/billing)
- [**Your profile and sign-in** Change your name, email and password, sign in with Google, see where you are signed in, connect Telegram, pick a theme, and delete your account for good.](https://briks.dev/docs/account)
- [**Templates** Browse templates, preview each one at its own address, make one yours with your business details, and share your own published site as a public template.](https://briks.dev/docs/templates)
- [**Made with Briks** List your published site in the Made with Briks gallery on briks.dev. See what is shown, how to switch it on and off, and what must be true for it to appear.](https://briks.dev/docs/made-with-briks)

## Help

Answers to the questions people ask most.

- [**Troubleshooting** What to do when something in Briks is not working: signing in, credits, builds and changes, domains, forms, email, the chatbot, data and teams.](https://briks.dev/docs/troubleshooting)
- [**Common questions** Short, straight answers about Briks: what it is, what it costs, the free plan, domains, your data, teams and clients, and what is coming next.](https://briks.dev/docs/faq)

## Can't find it?

Write to [hello@briks.dev](mailto:hello@briks.dev) with what you were trying to do and the page you were on.