> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kinship.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Models and Projects

> Kinship’s model and project system mirrors how BIM teams actually work together—giving you a smarter, more organized way to manage your Revit work.

Managing multiple Revit files can be tricky—especially when a real project involves several related models. Related **Revit models** are organized into **projects** that reflect how your teams actually collaborate. This structure gives you a clear, unified view of all your project files, their history, and their content—all in one place.

***

## What are models and projects?

* **Models**: A model is any Revit file (RVT) your team works on.
* **Projects**: A project is a collection of related models that belong together—usually because they’re part of the same real-world job or client work.

Instead of treating every Revit file as a separate item, related models are brought together into projects so you can see the big picture, track progress, and manage access across your team.

***

## How your files are organized

Whenever you use **Synchronize with Central** (SwC) on a workshared Revit file:

* The model is registered and key info like its name, file path, and project details is gathered.
* The model is matched to an existing project by looking at things like file names, BIM 360 project info, or where the central file is stored.
* If there’s no clear match, a new project is created or the model is kept “Unassigned” until you organize it.

This automatic grouping means you spend less time sorting files and more time designing.

***

## Working with projects: public and restricted

Not every project should be visible to everyone. Both **public** and **restricted** project types are supported:

* **Public projects**: Any team member can see and access these projects and their models.
* **Restricted projects**: Only admins and users who have actually worked on (synced with) one of the project’s models can view them. These projects are clearly marked with a blue lock icon for easy spotting.

This approach keeps sensitive work private, while still letting the right people collaborate.

***

## Why organize this way?

* **Clarity**: See all the related models for a project together, along with their changes and history.
* **Control**: Easily manage who can access what, and keep private work confidential.
* **Convenience**: Automatic project matching saves you setup time and helps avoid mistakes.

***

## Quick recap

| Term           | What it Means in Kinship                                                      |
| :------------- | :---------------------------------------------------------------------------- |
| **Model**      | A single Revit file your team works on                                        |
| **Project**    | A group of related models for a single job or client                          |
| **Public**     | Visible to your whole team                                                    |
| **Restricted** | Only for admins (or security admins if enabled) and those who’ve worked on it |

***

## Want to dive deeper?

Start with our [overview of tracking models](about-tracking-models-with-kinship), or explore more specific topics:

* [How to track models](how-to-track-models)
* [Automate model tracking with Model Sync Rules](about-model-sync-rules)
* [How to set up Model Sync Rules](how-to-set-up-model-sync-rules)
* [How to prevent models from being tracked](how-to-set-up-model-sync-rules-to-prevent-models-from-being-tracked)