--- title: "Project settings and preferences | Briks" url: https://briks.dev/docs/project-settings description: "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." last_updated: 2026-10-08 --- # Project settings and preferences A project's settings live in its **Settings** tab, and this page covers two of its sections. **General** is about the project itself: its name, logo and favicon, the Built with Briks badge, the Made with Briks listing, copying, moving and deleting. **Preferences** is about how Briks builds it: design rules, pictures, checks, search and the websites it may load from. 8 minute read Checked against the studio on 8 October 2026 Where 1. Projects 2. Your project 3. Settings 4. General The **Settings** tab opens on **General**. **Preferences** is the third section in its list, after **Domain**. The other sections have pages of their own, and [the project page](https://briks.dev/docs/the-project-page) lists them all. ## Name and marks | Field | What it does | | --- | --- | | **Project name** | 2 to 60 characters. “The name is used across the studio and in the site's own words. The address stays as it is.” | | **Logo** | “Used in the header and the footer in place of the drawn mark. A PNG or WebP on a transparent ground reads best.” | | **Favicon** | “The small square in the browser tab. Square, at least 180 by 180.” | | **Show the Built with Briks badge** | On paid plans: “A small link to Briks in the bottom-left corner of every page. Off unless you switch it on.” | On the Free plan there is no switch. The section says “Your site shows a small Built with Briks badge in a corner. It comes off on a paid plan.” instead, with the way to upgrade. Rename a project and add its logo 1. Change the name Where: Settings, General Type the new name in **Project name**. 2. Upload the logo Where: Settings, General Press **Upload** beside **Logo** and pick a PNG, JPEG or WebP. **Replace** swaps it later, and the bin icon removes it. 3. Save Where: Settings, General Press **Save** under **Name and marks**. **Saved** shows at the foot of the window. 4. Watch it reach the live site Where: Settings, General On a published site, saving a new logo, favicon or badge setting publishes the site again with it at once, and the studio says “Saved. Publishing the site with this change”. Nothing is held or charged for it. A new name alone reaches the site with your next change, or with **Apply to the live site**. The site's address isn't changed here. Owners and Admins change it under **Settings**, **Domain**; see [Your site's address](https://briks.dev/docs/site-address). ## Made with Briks Made with Briks is a gallery on briks.dev of sites their owners chose to show. The switch reads **Show this site in Made with Briks on briks.dev once it is in production**. It's off by default. When on, the gallery shows the site's name, a picture of its first screen, its address and your words, with a link to the site. Switch it off at any time to take the entry down. - **Short description** (optional): up to 160 characters, in your own words. With 80 or more, search engines can list the site's own page in the gallery. - **Category** (optional): Food and drink, Hospitality, Shops, Services, Creative, Health and fitness, Professional or Other. - A preview is never shown. The page says “This site is a preview, so it is not shown yet. It appears in the gallery once you publish it to production.” - Once saved and in production, it says where the entry is, under briks.dev/made-with-briks. Description Family bakery > `A family bakery in Bristol, baking sourdough and pastries every morning since 2019.` Category: **Food and drink**. At 83 characters the entry is long enough for search engines to list its own page in the gallery. More on the gallery is in [Made with Briks](https://briks.dev/docs/made-with-briks). ## Copy, template or move Below Made with Briks is a card of what you can do with the project as a whole. Copies and templates are made from the published version, so publish first. The same three are in the ••• menu on the project's row in **Projects**. | Action | What it does | | --- | --- | | **Duplicate** | An editable copy of the published version, here or in another workspace you work in. Its domain, messages and analytics stay with the original. It holds 5 credits while it's built and published, is charged only what that takes, and counts towards your plan's sites. | | **Save as template** | Freezes the published version so everyone in this workspace can start new projects from it. Later changes to this project never reach it. | | **Move to another workspace** | **Move project** hands it to another workspace where you are an Editor, Admin or Owner. The published site keeps running while it moves. Versions, domains, analytics, form messages, the chatbot and the library pictures and videos it uses go with it. The credits already spent stay behind, its AI agents let go of it, and members reach it only if they belong to the other workspace. | ## Delete a project At the bottom, under **Danger zone**, is **Delete project**. In the studio's words, it “Takes the site and its own domains offline, then deletes the project for good: its versions, pictures, analytics, form messages and chatbot. The credits it used stay on the workspace's record.” 1. Download what you want to keep Where: Settings, Backups Deletion can't be undone. On a paid plan, download the code of any version you might want later. 2. Press Delete project Where: Danger zone It's greyed out while something is running on the project: wait for that to finish. 3. Type the name Where: Dialog Type the project's name exactly and press **Delete project**. The site stops working at once, on every address. There's no way back A deleted project can't be restored, and its versions go with it. The project is marked as being deleted straight away and removed in the background. ## Preferences: design rules Anything set here beats what Briks would choose, on this build and every one after it. Leave a field alone to let the design decide. Changing a rule doesn't redo the site: it applies to the next change or build. | Field | What you set | | --- | --- | | **Accent**, **Ink on the accent**, **Page ground**, **Body ink** | Colours as six digit codes, such as `#1F6FEB`. | | **Display face**, **Body face** | A typeface from the list, or **Let the design decide**. | | **Corners** | A pixel value, such as `12px`. | | **Mode** | **Either**, **Light** or **Dark**. | | **Page width** | **Either**, **Narrow**, **Standard** or **Wide**. | | **Rhythm** | **Either**, **Tight**, **Standard** or **Airy**. | | **Motion** | **Either**, **Subtle**, **Standard** or **Cinematic**. | | **Flat colour only, no gradients** | A switch. | | **Rules in your own words** | Up to 1,000 characters, kept to build after build. | Rules in your own words Bookshop > `Never set words over a photograph. The footer stays black. Prices always in pounds with the £ sign.` Every change after that kept to the three rules, without the owner repeating them. ## Preferences: pictures and publishing **Pictures** sets where the site's pictures come from when Briks builds or changes it. One option is included; another draws every picture new at a price per picture. See [Pictures](https://briks.dev/docs/pictures). **Building and publishing** holds these switches, in this order. Those about the first build matter most before the site is built. | Switch | Starts | | --- | --- | | **Check the published site after the first build** | Off | | **Check the published site after every change** | Off | | **Measure builds against the reference** (for a site built from one you like; off saves credits) | Off | | **Ask about what is unclear before building** | On | | **Approve the words before building** (not for dashboards) | Off | | **Choose the look from three directions** (for a site built without a reference) | Off | | **Choose the hero from four wireframes** (not for dashboards) | Off | | **Keep this site out of search results** | Off | While the site isn't kept out of search, two fields take your **Google Search Console code** and **Bing Webmaster Tools code**. See [Search engines](https://briks.dev/docs/search-engines). As with General, press **Save** at the foot of the group, then **Apply to the live site** under **Live site** if you want the published site to pick the change up now. It publishes again with no design work. ## Preferences: allowed websites and the reference Your site loads code, connects and shows pages only from itself and the studio. **Allowed websites** is where you add another one when something on the site needs it, such as a booking widget or a map. Type it in **Website**, one at a time, such as `booking.example.com`, and confirm **Allow this website**. Code from that website runs on every page with the same reach as your own, so allow only one you know and trust. Each addition or removal applies from the next publish. For a site built from one you like, a **Reference site** group shows its address until the site is first published, because only the first build reads it. See [Build from a site you like](https://briks.dev/docs/build-from-sites-you-like). ## Sign-in and Payments The Settings list has an **Accounts and payments** group with **Sign-in** and **Payments**. **Sign-in** switches the ways your site's visitors sign in: email and password is on by default, and Google, Apple, Microsoft, GitHub, X, Facebook, LinkedIn and Discord are added with your own keys. **Payments** connects one payment processor with your own keys, for one-time payments and, with Stripe, Paddle, Polar or Lemon Squeezy, plans that renew. Keys go straight to the published site's own server and are never shown again. See [Sign-in and payments](https://briks.dev/docs/sign-in-and-payments). ## Who can change what | Action | Who | | --- | --- | | See General and Preferences | Everyone in the workspace | | Rename, logo, favicon, the badge, Made with Briks, preferences, allowed websites, **Apply to the live site** | Owner, Admin, Editor | | **Duplicate**, **Save as template** | Owner, Admin, Editor | | **Move to another workspace** | Owner, Admin (and Editor or above in the other workspace) | | **Delete project** | Owner, Admin | | Change the address | Owner, Admin | | Keys and switches in **Sign-in** and **Payments** | Owner, Admin | ### Does saving settings cost credits? No. Saving stores them, and **Apply to the live site** publishes again without building anything new. A change you ask for is charged as usual. ### I saved a new logo but the site still shows the old one. On a published site, saving a new logo publishes the site again by itself. If the save said the live site was not updated, press **Apply to the live site**, or the logo arrives with your next change. ### Can I get a deleted project back? No. On a paid plan, download its code from **Settings**, **Backups** before you delete it if you might need it. ## Read next - [Publishing and 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) - [Workspaces and account **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) - [Building **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) - [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) 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.