# Websites: how they work

See how your website runs on Data Visions, create one, and find your way around the Websites screen.

Your company website can live in the same place as the rest of your work. It can show live information from your workspace, such as open jobs, and send what visitors type into a contact form straight into your modules. Every change is checked on a preview address first, and going back to an earlier version takes one click.

[Open Websites now](/tenant/?open=settings/websites)

## How it works

- **Your own website, kept in versions.** Every change is a new numbered version with its own preview address. Visitors only see a version after someone publishes it.
- **Someone builds it for you, usually an AI.** The Module Builder in the app, Claude connected to your workspace, or a web designer with the command line. All three work on the same versions, so you can mix them.
- **It reaches your data only through feeds.** A feed is a door a module opens on purpose for its website, such as *job openings* or *send a contact request to the CRM*. The website never signs in to your workspace and can't see anything else.
- **Your own domain.** Connect addresses such as *acmeprecision.com* and *www.acmeprecision.com*. You prove you own them with DNS records.

## The Websites screen

1. Open **System settings**, then **Websites**.
   ![Open Websites](files/5fdac737-5a33-42ba-85db-967a3af2238a/websites-screen.webm#t=4.9,20.1)

Each website is a tile with:

- a **picture of its live home page**, taken again after every publish;
- its name and status;
- the **address visitors use**: your own domain once it's connected (the bare name, such as *acmeprecision.com*), or the Google address ending in *run.app* until then. Other connected domains show as *Also …*;
- which version is live;
- **DNS instructions**, with how many domains are still waiting.

Click a tile to open the website's page. It has **Edit in Module Builder**, **Retake picture**, and the sections **Versions**, **Upload new version**, **Feeds**, **Settings**, **Domains** and **Routes**.

## Create a website

1. On the Websites screen, click **+ New website**.
   ![New website](files/5fdac737-5a33-42ba-85db-967a3af2238a/websites-screen.webm#t=21.0,23.1)
2. Type its **Name** (for example *Company website*) and a **Short name** such as *www*: lower-case letters, numbers and dashes. The short name can't be changed later.
   ![Name and short name](files/5fdac737-5a33-42ba-85db-967a3af2238a/websites-screen.webm#t=24.0,31.4)
3. Click **Create website**.
   ![Create website](files/5fdac737-5a33-42ba-85db-967a3af2238a/websites-screen.webm#t=32.4,34.0)

To let the website use a module, such as sending its contact form to the CRM, add feeds on the website's page afterwards. See [Connect a website form to a module (CRM leads)](article:b2d3c3af-db89-4d34-9fb4-5d6a0912765e).

The new website is empty until its first version is uploaded. That first version comes from your web designer or a coding agent: as a file here (below) or from the command line. See [Websites with Claude and the command line](article:8a279ac0-4012-4ede-ad92-8a257c2badee). Once it has a version, the Module Builder and Claude can change it.

> **The first version goes live by itself.** There is nothing else to show yet, so it starts serving at its Google address straight away. Every later version waits for **Publish**.

## Upload a version yourself

If your web designer hands you the website as a file:

1. Open the website. Under **Upload new version**, choose the **.zip** or **.tar.gz** in **Site folder**, and say what changed in **Notes**.
   ![Site folder and notes](files/9b2bf5b5-a16f-4e3d-94c7-d9610f2831ce/website-versions.webm#t=29.7,37.6)
2. Click **Upload**. The platform builds it, which takes a few minutes. The page checks every 10 seconds.
   ![Upload](files/9b2bf5b5-a16f-4e3d-94c7-d9610f2831ce/website-versions.webm#t=37.6,39.2)
3. Click **Preview** on the new version and look at it, then click **Publish**.
   ![Preview and Publish](files/9b2bf5b5-a16f-4e3d-94c7-d9610f2831ce/website-versions.webm#t=22.6,25.8)

The file must be a complete website that Data Visions can build: it needs a file named *Dockerfile* at the top. Your web designer or AI agent takes care of that. More in [Versions, preview, publish and roll back](article:6fab4ced-4291-4c52-b83d-b74de2ee3ecd).

## What a website can't do

- **Customer logins.** A portal where your customers sign in and see their own records is not available yet.
- **Read anything a module doesn't offer as a feed.** If you need something new on the website, the module needs a feed for it first. See [Connect a website form to a module (CRM leads)](article:b2d3c3af-db89-4d34-9fb4-5d6a0912765e).

## Good to know

- **Who can do what.** Workspace Admins can do everything here. You can also give others three separate permissions: *View websites*, *Manage websites* (prepare versions, feeds, settings, domains) and *Publish websites* (put a version live or roll back). Give your web person *Manage websites* and keep *Publish websites* for one or two people. See [Users and roles: create and edit roles](article:88d4e232-d5b8-4909-b452-cfe96d3d550f).
- **Preview addresses are public.** Anyone with the link can open one, so don't put anything secret in a version.
- **Settings** hold plain values the website reads, such as a contact email or an analytics ID, never passwords. Values aren't shown again after saving, and saving replaces the whole list, so type every value again when you edit. They apply with the next version.
- **A failed build** shows its reason and a **Build log** link. The live version keeps running.
- **Hosting is counted per live website** on your monthly bill. See [Billing](article:74594451-2ed3-4d0f-b24a-33799c898a43).

[Show me how](showme:platform-publish-a-website)


Source: https://datavisions.ai/docs/system-settings/workspace/websites-2/websites-how-they-work
