# Refresh

Brand Kit Refresh keeps a Brand Kit current by scanning the sources you choose on a schedule, proposing edits when something changes, and letting you publish or revert each edit from the Brand Kit page.

Organizations move quickly. New products launch, audiences shift, positioning gets refined, and competitors pivot. Out-of-date context produces wrong content, like a competitor comparison or product claim that was true months ago and is wrong today. Refresh removes the burden of hand-maintaining that context inside AirOps and lets your sources of truth, wherever they live, drive updates.

{% hint style="warning" %}
Brand Kit Refresh is available in workspaces with access to Playbooks. If you don't see the Refresh option on your Brand Kit page, contact your account team to confirm Playbooks is enabled.
{% endhint %}

## How it works

1. **Enable Refresh on a Brand Kit.** Open the Brand Kit and turn on Refresh from the Brand Kit page. AirOps creates a default playbook that scans public sources for changes.
2. **Add your own sources (optional).** Point Refresh at the places your brand context actually lives. A Notion MCP connector, a documentation site, a GitHub repository, and any source supported by AirOps integrations can be added alongside the public scan.
3. **Choose a frequency.** Pick how often the scan runs. Each run produces proposed edits to the Brand Kit, not direct writes.
4. **Review and act on proposals in the Inbox.** When the scan finds a change, a notification lands in your Inbox. Open the Brand Kit page to publish the proposed edit or revert it. Edits flow through the standard Brand Kit [draft and publish lifecycle](/context/brand-kit.md#versioning-and-history), so nothing changes in production until you approve it.

## What gets proposed

Refresh can propose edits to any field in your Brand Kit, including Foundations, Product Lines, Content Types, Audiences, and Regions. Each proposal is scoped to the field that changed in the source, so reviewing is fast.

## Enabling and configuring

1. Navigate to the Brand Kit you want to keep fresh.
2. Click **Enable Refresh** on the Brand Kit page. AirOps installs the default refresh playbook for the Brand Kit.
3. Open the Refresh configuration panel to:
   * Add or remove source connectors (for example, a Notion MCP connector pointing at your brand docs).
   * Set the scan frequency.
   * Pause or disable refresh at any time.
4. Save your changes. The next scan runs at the configured frequency.

## Reviewing proposed edits

When a refresh run produces proposed edits:

* A notification appears in your Inbox summarizing what changed.
* Open the Brand Kit page to see the proposed edit inline against the current published value.
* **Publish** the edit to apply it to the Brand Kit, or **revert** it to keep the current value.
* Published edits create a new Brand Kit version with full attribution, the same as any other Brand Kit change.

## Tips

* Start with one or two high-signal sources (your product marketing Notion, your pricing page) before adding more. The signal-to-noise ratio of proposals scales with how curated the source list is.
* If a proposed edit is wrong, reverting it is one click. Reverts don't disable the source.
* Use Refresh for the parts of your Brand Kit that change most often. Foundations like brand voice rarely shift; Product Lines and Audiences move more frequently.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.airops.com/context/brand-kit/refresh.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.