---
title: Quickstart
description: Install Schema City and open your content model as a city in the Umbraco backoffice.
seo:
  image: /og/quickstart.png
---

## Requirements

| Requirement | Version |
| --- | --- |
| Umbraco | 17 or 18, tested on 17.6.2 and 18.1.1 |
| .NET | 10 |
| Backoffice user | Access to the Settings section |

## Install

```sh
dotnet add package TheBuilder.SchemaCity
```

Restart the site. The package needs no migration and adds nothing to your schema.

## Open the city

Open **Settings > Advanced > Schema City**. The city opens on a raised view of the whole schema, with a board for each type allowed at root.

Every Document Type editor also gets a **Relationships** tab. It opens the city focused on that type and its neighbours.

## Turn off the Relationships tab

The tab is on by default. To leave it out of the Document Type editor, set `RelationshipsTab` to `false` in `appsettings.json` and restart the site:

```json appsettings.json
{
  "SchemaCity": {
    "RelationshipsTab": false
  }
}
```

The city under **Settings > Advanced** stays either way. As with any appsettings value, an environment variable can set it too: `SchemaCity__RelationshipsTab=false`.

## First steps

1. **Find a type**

    Press <kbd>⌘</kbd> <kbd>K</kbd> or <kbd>Ctrl</kbd> <kbd>K</kbd> and search by name, alias or property alias.

2. **Look at its neighbourhood**

    Click its building to open the inspector, then double-click it to focus on the types it connects to.

3. **Check the schema**

    Open **Findings** in the header to see what the checks flag across the schema. See [Review findings](/findings).

4. **Trace a change**

    Press <kbd>I</kbd> with a type selected to see every type a change to it reaches. See [Trace the impact of a change](/impact).

Press <kbd>?</kbd> for every control, or read [Navigate the city](/navigation).

To look around before you install, [try the demo](https://schema-city-demo.thebuilder.dk). It runs in the browser with a sample schema and needs no Umbraco install.