# Create, Edit, and Publish a Site

Sites are generated dashboards or apps that you can open from Redbelt. Review a
site’s content, behavior, and audience before publishing a version.

## Preview Before You Publish

A site turns content into a browser experience, such as a launch dashboard. Editing changes the working version; publishing makes the configured version available at its destination. Check the preview’s text, links, and layout before completing the publish action.

Be explicit about the audience and data you want displayed. A status dashboard should show the intended project information without accidentally including private notes or credentials. Use the published URL to verify the final result, because the editing view and the published destination are separate checks.

![New site, Ideas, and Search sites are the entry controls on the current Sites page.](/screenshots/current/sites-start-controls.png)

## Create a site

1. Open **Sites** and choose **New site** or **Create a site**, or start in the main thread composer.
2. Describe the purpose, intended audience, and information it should show.
3. Supply authorized source context and clear interaction requirements.
4. Open the generated site and test its main paths.

Example request:

Attach a project plan with action owners and due dates, then request:

> Create a project dashboard from the attached plan, with action owners, due dates,
> and a completed-work filter. Make overdue actions easy to spot.

## Edit and inspect versions

Use the site’s editing thread to request a specific change. In **Versions**,
use **Preview** to inspect a version before selecting **Publish**. Check the
layout, source data, links, and interactive controls after each meaningful edit.

A preview and a published version can differ. A working preview does not prove
the published audience has the same data access.

## Check data access and publication

Review any site data-source bindings and capability grants before enabling
actions. Grant only the operations and resources the site needs. Publish the
reviewed version, then open its actual published destination and test it there.

If data is missing or stale, inspect the source binding, access, refresh settings,
and selected version. Do not paste provider credentials into site content.

Related: [sharing](/knowledge/sharing/) and [action approvals](/threads/approvals/).
