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

# Metadata, Tags, and Site Files

> Use tags, metadata, notes, media, and documents to make your SDX fleet searchable, reportable, and automation-ready.

Metadata turns a list of routers into an operable fleet. Tags and site files give your team enough context to filter sites, assign ownership, build reports, trigger workflows, and investigate incidents quickly.

## Prerequisites

Before you standardize metadata, decide:

* Which tag keys are required for every site.
* Which values are allowed for each tag key.
* Who owns tag definitions.
* Which notes or documents should be attached to sites.
* Whether tags should be mandatory for sites or other resource types.

## Metadata Types

<CardGroup cols={2}>
  <Card title="Tags" icon="tags">
    Structured key-value context. Tags support filtering, reporting, workflow conditions, and resource selection.
  </Card>

  <Card title="Notes" icon="sticky-note">
    Human-readable operational context, such as access instructions, circuit notes, or support history.
  </Card>

  <Card title="Media" icon="image">
    Site images or visual context that helps identify the location or installation.
  </Card>

  <Card title="Documents" icon="file">
    Files attached to the site, such as handover notes, diagrams, maintenance records, or customer documentation.
  </Card>
</CardGroup>

## Design a Tag Model

Start with a small number of high-value tags. Common tag keys include:

* `region`
* `customer`
* `environment`
* `service-tier`
* `owner`
* `site-type`
* `maintenance-window`

Use predictable values. For example, choose either `production` or `prod`, not both.

<Tip>
  Tags become inputs to reports and workflows. Keep them boring, consistent, and easy to audit.
</Tip>

## Create a Tag Definition

<Steps>
  <Step title="Open tag management">
    Go to **Settings > Tag Management**.
  </Step>

  <Step title="Create the tag">
    Add the tag key, choose a color, and define whether the tag should be mandatory for one or more resource types.
  </Step>

  <Step title="Apply values">
    Add tag values to sites or other supported resources.
  </Step>

  <Step title="Audit coverage">
    Review which sites are missing mandatory tags and fill gaps before using the tag in workflows or reports.
  </Step>
</Steps>

## Add Site Context

From a site, use metadata, notes, media, and documents to capture context that is not visible from RouterOS alone:

* Physical location or rack notes
* ISP and circuit references
* Customer contacts
* Internal escalation notes
* Photos of the installation
* Change or handover documents

## Use Tags in Operations

Tags are most valuable when they drive action:

* Filter sites in fleet views.
* Select sites for reports.
* Route workflow logic with resource tag conditions.
* Apply or remove tags from a workflow.
* Group operational ownership by region or customer.

## Best Practices

<CardGroup cols={2}>
  <Card title="Keep Keys Stable" icon="key">
    Rename tag keys rarely. Downstream workflows and reports may rely on them.
  </Card>

  <Card title="Prefer Enumerated Values" icon="list">
    Use a limited set of approved values where possible.
  </Card>

  <Card title="Document Mandatory Tags" icon="clipboard-check">
    If a tag is required, explain who owns it and what each value means.
  </Card>

  <Card title="Avoid Secrets" icon="ban">
    Do not store passwords, private keys, or tokens in metadata, notes, files, or tag values.
  </Card>
</CardGroup>