Words we use

#A

• Accept the risk: Your answer to a finding in the Security agent's report when you choose to live with it. The agent does not raise it again unless it gets worse. See Security agent.
• A/B test: Showing a saved version of a site to some visitors and the live version to the rest, to see which gets more people to act, such as tapping a phone number or sending a form. See A/B tests.
• Admin: A role. Admins manage members, settings, templates and skills, and can move projects to another workspace. See members and roles.
• Agent: An AI helper you hire for a project, from the Starter plan. It works on a schedule or when something happens, such as a new form entry, and asks you first before anything goes out, unless you have let it act on its own. See hire AI agents.
• Analytics: The visitor figures for a published site: visitors, pages, sources, referrers and campaign tags, counted without cookies. On by default. See analytics.
• Approval: Something an agent wants to do that waits for your yes. You decide under Waiting for you on the Agents page, from the email it sends, or on Telegram. See approvals and budgets.
• Approval steps: Optional pauses in a first build where you approve the words, choose a look or choose a hero layout before Briks carries on. See approve as it builds.

#B

• Backup: A saved copy to go back to. Each publish keeps a version of the site's code, and on a paid plan a project's database can also take nightly copies, kept for 30 days. See backups.
• Brief: Your description of what to build: who it is for, what it offers, how it should feel and which pages it needs. Up to 25,000 characters. See writing a good brief.
• Build: The work of turning a brief into a published site: planning, design, the code, checks and publishing. A first build holds 50 credits. See watching a build.
• Built with Briks badge: A small link to Briks in the bottom-left corner of every page. Free sites always show it. On a paid plan it is off unless you switch it on in the project's settings. See project settings.

#C

• Change: Something you ask for in plain words in a project's conversation, such as 'add a page for our menu'. Briks builds it and publishes it. A change holds 5 credits. See making changes.
• Chatbot: An optional chat window on your site that answers visitors from your published pages and emails you the questions it passes on. Off by default, up to 400 chats a day per site. See chatbot.
• Check: Briks looking at your site for problems. Contrast is checked on every first build; the full check at four screen sizes, which repairs what renders broken, is one you switch on. A check run on its own holds 5 credits. See watching a build.
• Collection: A named group of records in a project's database, such as bookings, products or sign-ups. Think of one sheet in a spreadsheet. See database.
• Credit: The unit Briks charges its work in. Each job is charged for the work it took, to the hundredth of a credit. See credits and plans.
• Custom domain: Your own web address, such as yourbakery.co.uk, connected to a project alongside its briks.live address. Starts on the Starter plan. See connect your domain.

#D

• Database: Where a project keeps what it stores, collection by collection. It is made when a build needs to store data. Its records can be viewed and edited, and exported on a paid plan. See database.
• Decide for me: The button on the questions before a first build that takes every recommended answer at once. See questions before building.
• Deploy hook: A secret web address that publishes a project again when something calls it, for example a content tool after an edit. See published versions and deploy hooks.

#E and F

• Editor: A role. Editors create, change and publish projects. See members and roles.
• Estimate: What builds like yours usually take, in credits, worked out from what similar builds cost and rounded up to the nearest 5. The studio shows one before a first build, and for a change that adds pages, when it is more than you have. See credits and plans.
• Form entry: A message a visitor sends through a form on your site. Entries are kept in the studio, where the latest 100 are shown, and emailed to you only once the site is in production. They cannot be exported yet. See forms.

#H and I

• Hold: Credits set aside from your balance when a job starts: 50 for a new site, 5 for a change, 5 for a check, 3 for an agent's run. When the job ends, what it did not use comes back. See credits and plans.
• Image editor: Where you make pictures for social posts, stories and thumbnails in your site's colours and typefaces, at each platform's exact size. Describe it writes three designs from your words. Open on every plan. See image editor.
• Invitation: An email that lets someone join your workspace with a role. Its link works for 7 days and only for the address it was sent to. See members and roles.

#L and M

• Launch check: The check Briks runs when you press Publish to production, including a look for links that lead nowhere. If something needs fixing, nothing changes and you are told what. See publish to production.
• Marketing tab: A project's tab for social posts: connect its social accounts, then write and schedule posts for them. It shows once posting is available to you. See marketing and social posts.
• Logs: A project's record of every build, change and publish and the steps each went through, plus the site's requests and errors over the last 24 hours. See logs.
• Media library: A workspace's store of pictures and videos, which you can use in any of its projects. See media library.
• Member: Someone who belongs to a workspace. Every member has a role. Each plan includes a number of members, with no seat fees. See members and roles.

#N

• Notifications: The bell in the top bar. It lists builds, agents at work, what waits for you, form entries and chat hand-offs, newest first, and opening it marks them read. See exploring the dashboard.

#O and P

• Owner: The role with every right, including billing, adding or removing other Owners and deleting the workspace. A workspace always keeps at least one. See members and roles.
• Preview: A site's first published state, at its briks.live address. It works fully, but search engines are asked to leave it out and form entries are not emailed. See preview and production.
• Production: A site published for real: search engines may list it and form entries are emailed to you. You get there with Publish to production. See preview and production.
• Project: One website, web app or dashboard, with its conversation, versions, address and settings. Each plan includes a number of them. See start a new project.
• Publish: Putting the latest version online at the site's address. Every build and change publishes; Publish to production is the separate step that makes a preview public in full. See publish to production.

#Q and R

• Queue: Messages you send while a build is running wait in a queue and run when it finishes, together as one change. See making changes.
• Questions: Before the first build of a website or web app, Briks asks which pages you want and, unless you switch it off, about anything your brief leaves open. A question you type into the conversation later is answered without a build. See questions before building.
• Record: One entry in a collection, such as a single booking or a single product. Think of one row in a spreadsheet. See database.
• Resume building: The button that carries on a first build waiting for credits, from its plan, once you have them. A waiting build never carries on by itself. See credits and plans.
• Reference site: A site you like and show Briks when starting a project, so it can follow its layout, spacing, type, motion and header menu. One per project, plus screenshots. See build from a site you like.
• Role: What a member can do in a workspace: Owner, Admin, Editor or Viewer. See members and roles.

#S

• Scheduled task: A call to an address on your site, or any secure web address, made on a timetable, such as every day at 09:00. Used for daily digests, tidying old records or syncing with another service. See scheduled tasks.
• Secret: A private value your site needs, such as a key for another service, kept with the live site rather than written into its code. See secrets.
• Site address: The address every project gets, in the form name.briks.live. It is made from the project name, and an Owner or Admin can change it to any free name of 3 to 40 lowercase letters, numbers and hyphens. See your site's address.
• Site email: Email your site sends, such as a confirmation to a visitor, from an address at emails.briks.live. Off by default, with a monthly allowance set by the plan. See site email.
• Security agent: An agent that checks a site's code, its keys and the live site each week and after every publish, and tells you plainly what it found. Its fixes always wait for your approval. See Security agent.
• Skill: Written guidance Briks follows on a workspace's projects when a task fits it: your tone, your facts, your conventions. See skills.
• Storage: A project's own files, including public folders the site can serve to visitors. See storage.

#T and V

• Team lead: An agent that leads a project's other agents. It plans the week from your goals, hands out the work and sends you one stand-up, and never approves anything for anyone. See Team lead.
• Template: A published site frozen as a starting point. Start from one, give your business's details, and every page is rewritten for you before it is published. See templates.
• Version: A saved state of a site. Every build, change and recheck makes one, and anyone with edit rights can undo, redo or restore. See versions, undo and redo.
• Viewer: A role that can see projects, previews and analytics but change nothing. See members and roles.
• Visual Editor: A project tab where you click any part of a published page and change its words, pictures and sections by hand, then publish with no build and no credits. AI help with words is charged per use. Comes with a paid plan. See Visual Editor.

#W

• Waiting for credits: A first build stopped once planned, because the rest usually takes more credits than you have. The plan is kept until you press Resume building. See credits and plans.
• Webhook: A message Briks sends to another service's address when something happens: a site is published, a form entry arrives or a record changes. See webhooks.
• Workspace: A shared space with its own projects, members, plan and credits. One person can own up to 10. See workspaces.