> ## Documentation Index
> Fetch the complete documentation index at: https://agentrail.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Brand Vault
> The company and product information Agentrail uses to draft your setup and to recognize your product in what agents say and build.
The Brand Vault holds what Agentrail knows about your company and product: its names, official websites, capabilities, technical fit and audience. Setup research fills it in, setup drafting builds your topics, prompts and evaluations from it, and Agentrail uses it to recognize your product in agent answers and in the code agents write.
## Where to find it
In the sidebar, open **Product** and select **Brand Vault**. During setup, it is the **Brand Vault** tab of **Review what research found**. See [Setup](/docs/guides/setup).
The top of the page shows how many of the nine fields are filled, such as **6 of 9 fields filled**. Each group shows its own count.
## The fields
Fields are grouped into **Company**, **Product** and **Audience**.
### Company
Who makes the product and where it lives on the web.
| Field | What goes in it | Limit |
| - | - | - |
| **Company name** | The legal or commonly used name of the company. | 200 characters |
| **Summary** | What the product does for a developer, in a few sentences. | 4,000 characters |
| **Aliases** | Other names the product is known by. One entry per line. | 100 entries of up to 1,000 characters |
| **Official surfaces** | Official websites, such as docs, pricing, a repository, a blog or the homepage. Each row has an **Address** and a **Kind**. | 100 surfaces. Address up to 2,048 characters, kind up to 1,000 |
### Product
What it does, how developers use it and what it runs on.
| Field | What goes in it | Limit |
| - | - | - |
| **Capabilities** | What the product can do. Each row has a **Name** and an optional **Description**. | 100 capabilities, 1,000 characters per entry |
| **Technical fit** | The languages, frameworks and environments the product works with, in three lists: **Languages**, **Frameworks** and **Environments**. One entry per line. | 100 entries per list, 1,000 characters each |
| **Product interfaces** | How developers use the product, such as an SDK, an API or an extension. Each row has a **Kind**, a **Name** and an optional **Ecosystem**. | 100 interfaces, 1,000 characters per entry |
### Audience
Who it is for and the work they do with it.
| Field | What goes in it | Limit |
| - | - | - |
| **Audience** | The developers the product is built for. One entry per line. | 100 entries of up to 1,000 characters |
| **Common work** | Tasks developers commonly do with the product. One entry per line. | 100 entries of up to 1,000 characters |
## What an empty field means
A field without a value shows one of two badges:
* **Not set**: nobody has filled it yet. Setup research can still fill this.
* **Left empty**: someone saved it as empty on purpose, so setup research leaves it alone.
## Edit a field
Select **Edit** next to the field.
* **Company name** and **Summary** are plain text.
* **Aliases**, **Audience**, **Common work** and the three **Technical fit** lists take one entry per line.
* **Official surfaces**, **Capabilities** and **Product interfaces** take rows. Select **Add row** for another, or the remove button at the end of a row to drop it. Blank rows are ignored. A partly filled row must be completed before you can save.
Select **Save**. You see **Brand Vault updated.** Select **Cancel** to discard your changes.
**Save** stays unavailable until you change something. On a field that is **Not set**, you cannot save an empty value: use **Mark as empty** instead.
Each address in **Official surfaces** must be a public `http` or `https` website. An address without `http://` or `https://` is saved as `https://`. Addresses are saved without query strings or fragments.
## Clear a field or mark it as empty
Use these when a field does not apply to your product.
* On a field with a value, select **Clear**. The current value is removed and the field is saved as empty. Setup research will not fill it again.
* On a field that is **Not set**, select **Mark as empty**. The field is saved as empty. Setup research will not fill it again.
Both ask you to confirm, and both leave the field **Left empty**. To fill it again later, select **Edit**.
## How Agentrail uses it
Setup drafts your topics, preference prompts and experience evaluations from all nine fields, as you leave them at review.
Your product's names, websites and packages tell Agentrail when an agent picks or uses your product.
Agentrail recognizes your product by:
* its name, which is the organization name you entered when you created your organization, and every entry in **Aliases**;
* your website, and each **Official surfaces** address whose **Kind** is `docs`, including their subdomains;
* the **Name** of each **Product interfaces** row that has an **Ecosystem**, read as a package name.
When you change these, Agentrail checks earlier runs again in the background, so your results match the new details.
Add every name an agent might use for your product to **Aliases**, such as a short name or a former name. For each package developers install, add a **Product interfaces** row with its package name as the **Name** and its package registry as the **Ecosystem**.
Editing the Brand Vault after setup does not redraft your topics, prompts or evaluations. Change those on their own pages: [Topics and Tags](/docs/guides/topics-and-tags), [Agent Preference](/docs/guides/agent-preference) and [Agent Experience](/docs/guides/agent-experience).
## Who can do what
Everyone in the organization can view the Brand Vault. Only Admins can edit, clear or mark a field as empty. A Member sees **Only Admins can change the Brand Vault.** See [People and roles](/docs/guides/people-and-roles).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.