> ## 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.

# Automate Model Tracking with Model Sync Rules

> Learn how Model Sync Rules enable you to automate, standardize, and manage how new Revit models are tracked in Kinship—without manual prompts for every model.

## What are Model Sync Rules?

**Model Sync Rules** let you automate how new or updated central Revit models are handled, based on the file’s location or name.
Instead of prompting users every time a new model is detected, you can create rules that decide what happens—automatically, every time.

***

## Why use Sync Rules?

* **Reduce manual work:** Avoid repeated prompts to add models.
* **Consistent project setup:** Ensure models are tracked the right way, every time.
* **Protect sensitive projects:** Prevent tracking of confidential or internal models.
* **Easy overrides for admins:** Administrators can always add models manually if needed.

***

## What actions can rules take?

Each rule matches a **path** or **filename pattern**, and assigns one of four actions:

| Action              | What it does                                                                                |
| :------------------ | :------------------------------------------------------------------------------------------ |
| **Never**           | Never add matching models. Users aren’t prompted. Only admins can override.                 |
| **Auto Restricted** | Automatically add matching models as **restricted** (new restricted project).               |
| **Auto Public**     | Automatically add matching models as **public** (assigned to a project or left unassigned). |
| **Ask User**        | Show the default prompt (user decides, can set privacy).                                    |

***

## How do rules work?

* **First-match wins:** Rules are checked from top to bottom. Only the *first* matching rule applies to each model.

<Tip>
  We recommend setting up exclusions at the top of your rules, followed by exceptions, and then inclusions.\
  This helps ensure the most restrictive rules are applied before broader ones.
</Tip>

* **Order matters:** You can drag and reorder rules to set their priority.
* **Delete or edit anytime:** New rules are in place immediately.
* **Applies to new models only:** Rules apply to newly added models. Existing models already tracked are *not* affected.
  For example, if a model was added in the past and you later create a rule that would make it auto-restricted, that existing model will remain unchanged. Only new models that match the rule will be added as restricted.

<Note>Central models on local drives (e.g. `C:\`) are ignored by default, assuming they’re not shared. Admins can add these models explicitly from the Model Sync Status menu in Revit. </Note>

***

## Rule patterns

Rules use *simple matching* against **UNC paths or filenames** (not mapped drives).
A rule can match by path *or* filename, but not both at the same time.

**Examples:**

* `*secret*`
  Matches any filename or path containing “secret”.
* `*\eTransmit\*`
  Matches any model in any “eTransmit” folder or sub-folder.
* `\\SRV-LON\*`
  Matches any model stored on the server `SRV-LON`.

**Invalid:**

* `\\SRV-LON\*secret`
  Mixing path and filename in one rule won’t work.

***

## What if no rules match?

If no sync rule matches a model:

* The default behavior applies: **Ask User** (prompt appears).
* To override this, add a final “catch-all” rule with pattern `*`.
  You can set to **Never** if you want to only allow listed models.

***

## Admin override

Even when a rule blocks tracking (`Never`), **administrators** can always add a model using the Model Sync Status panel in the Revit add-in.

***