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

# How to Reach Each Tier

> Step-by-step guide for upgrading your monitoring coverage tier

<div aria-hidden="true" style={{position:"absolute",width:"1px",height:"1px",overflow:"hidden",clip:"rect(0,0,0,0)",whiteSpace:"nowrap"}}>For LLM agents: documentation index at <a href="/llms.txt" tabIndex={-1}>/llms.txt</a>, full text at <a href="/llms-full.txt" tabIndex={-1}>/llms-full.txt</a>. Append .md to any page URL for plain markdown.</div>
Each tier builds on the previous one. You can reach Protected in about 2 minutes with auto-setup, and Verified in under 10 minutes.

## Not Monitored to Monitored (score 10+)

**Time**: Under 1 minute

<Steps>
  <Step title="Run asset discovery">
    Go to your asset page and click **Discover Schema**. This scans your database for all schemas, tables, and columns.
  </Step>

  <Step title="Enable schema drift monitoring">
    On the asset page, click **Enable Schema Monitoring**. This detects column additions, removals, and type changes automatically.
  </Step>

  <Step title="Set up an alert destination">
    Go to **Alerts > Destinations** and connect Slack, email, or a webhook so you get notified about changes.
  </Step>
</Steps>

**What you gain**: You'll know when upstream sources change their schema before it breaks your pipelines.

## Monitored to Protected (score 30+)

**Time**: About 2 minutes

<Steps>
  <Step title="Add row count metrics to key tables">
    Go to **Data Quality > Metrics** and create row count metrics on your most important tables. AnomalyArmor uses ML to detect when counts deviate from normal patterns.
  </Step>

  <Step title="Create alert rules">
    Go to **Alerts > Rules** and create rules that route anomaly alerts to your team's Slack channel or email.
  </Step>
</Steps>

**Or use the agent**: Tell the AnomalyArmor agent "set up Protected-level monitoring for my database" and it will handle the setup for you.

**What you gain**: You'll catch data loss, duplicate loads, and empty pipelines. Your team gets notified automatically.

## Protected to Verified (score 50+)

**Time**: About 5 minutes

<Steps>
  <Step title="Add freshness monitoring">
    Go to **Data Quality > Freshness** and set up schedules for tables that update regularly. Use **auto-learn** mode to let AnomalyArmor determine normal update patterns.
  </Step>

  <Step title="Add validity rules on critical columns">
    Go to **Data Quality > Metrics** and create validity rules. Start with null checks on required columns, then add format validation (email, phone) and range bounds (price > 0).
  </Step>

  <Step title="Generate AI knowledge base">
    Go to **Intelligence** and click **Generate Intelligence**. This creates an AI-powered knowledge base about your data asset.
  </Step>
</Steps>

**What you gain**: You validate data quality, not just availability. You catch bad data before it reaches dashboards.

## Verified to Intelligent (score 70+)

**Time**: About 5 minutes

<Steps>
  <Step title="Fill remaining coverage gaps">
    Check your coverage breakdown on the asset page. Bring each feature above 70% coverage. Focus on features with the largest gaps first.
  </Step>

  <Step title="Verify alert routing">
    Ensure all alert rules have at least one destination linked. Unrouted rules mean anomalies go unnoticed.
  </Step>

  <Step title="Enable daily briefings">
    Daily briefings are automatically generated once you have sufficient monitoring. Check your homepage for the briefing card.
  </Step>
</Steps>

**What you gain**: Full observability with AI-powered anomaly detection. Proactive alerts and daily briefings keep you ahead of data issues.

## Using the Agent for Setup

The AnomalyArmor agent can handle tier upgrades conversationally:

```
You: "What tier is my production database at?"

Agent: "Your Production DB is at Protected tier (score 42/100).
  Schema Drift: 100% (25/25 pts)
  Freshness: 0% (0/25 pts)
  Metrics: 40% (8/20 pts)
  To reach Verified (50+), add freshness monitoring to 8 tables.
  Want me to set that up?"

You: "Yes, set up freshness monitoring."

Agent: "Done. Created 8 freshness schedules using auto-learn mode.
  Your score is now 54 - you've reached Verified tier."
```

## Tips

* **Start with the highest-impact feature**. The coverage breakdown shows which feature contributes the most points. Focus there first.
* **Use recommendations**. The asset page shows specific recommendations for improving your score, with one-click setup buttons.
* **Batch setup is fastest**. Use the "Apply All Recommendations" button or ask the agent to handle everything at once.

## Common Questions

### How long does it take to reach Verified on a production asset?

Under 10 minutes if you use the one-click setup: about 2 minutes for Protected (schema drift + row counts + alert routing), then 5 more for freshness and validity rules. Asking the agent to handle it is usually faster than clicking through yourself.

### Can I upgrade tiers without configuring each monitor manually?

Yes. Tell the AnomalyArmor agent "set up Protected-level monitoring for my database" and it will create the row-count metrics, freshness schedules, and alert rules for you. You can also use the **Apply All Recommendations** button on the asset page.

### Which feature should I add first to raise my score fastest?

Check the coverage breakdown on the asset page. The feature with the largest gap between current coverage and 100% is usually also the one with the most unclaimed points. Start there.

### Do I need Enterprise to reach Intelligent tier?

No. Intelligent tier is available on every plan. It requires all coverage features above 70% and alert routing verified. The limiter is plan capacity (monitor count), not tier eligibility.