# Account Instructions (Beta)

{% hint style="info" %}
Account Instructions is a Beta feature, available behind a feature flag. Contact your Finout account team to enable it for your account.
{% endhint %}

Account Instructions let you give [Billy](https://docs.finout.io/ai-and-developer-tools/billy-your-ai-finops-assistant) a persistent set of instructions that shape how it answers — written once, applied to every question across your account.

By default, Billy interprets each question on its own. When two people ask the same thing in different ways, or when a term like "team" maps to more than one dimension in your data, Billy can resolve it differently from one answer to the next.&#x20;

Account Instructions remove that ambiguity: you tell Billy how your account works once, and every user gets answers built on the same assumptions.

Use Account Instructions to:

* **Set a default cost type** — for example, have Billy answer in net amortized cost unless a question says otherwise.
* **Map terms to specific dimensions** — tell Billy that "team" means a specific Virtual Tag, native tag key, or Cost Center label, so it stops guessing.
* **Standardize how answers look** — set preferences for the format or framing you want in Billy's responses.
* **Encode account context** — describe the conventions, naming, and structures specific to your account so Billy's answers reflect them.

***

### Prerequisites

* [AI Services](https://docs.finout.io/cross-platform-features/list-of-cross-platform-features/ai-in-finout/ai-opt-in) must be enabled for your account. This is a one-time action performed by an account Admin.
* You must have the permission to edit Account Instructions: `Edit Account Instructions`. Admins have this permission by default.&#x20;

{% hint style="info" %}
Only users with the `Edit Account Instructions` permission can view, edit, or toggle the instructions. Everyone else receives Billy's answers with the instructions already applied, without seeing or managing them.
{% endhint %}

### Open Account Instructions

1. **Navigate** to **Settings** in the Finout sidebar.
2. **Open** the **AI Governance** tab.

<figure><img src="/files/IDM6b1vP4hhz6FUsFWsl" alt=""><figcaption></figcaption></figure>

### Write your instructions

1. In the Account Instructions field, write your instructions in plain language. No need to follow any required structure — write the instructions the way you'd explain them to a colleague.
2. Keep your instructions within the **5,000-character limit**.

<figure><img src="/files/WNa3TGhsC5tX1JWiTOQd" alt=""><figcaption></figcaption></figure>

### Save your instructions

**Click** **Save**. Your instructions take effect for every account user the next time they ask Billy a question.

### Turn instructions on or off in Billy

You can control whether Billy applies your Account Instructions without deleting them.

1. Open Billy from the left navigation.
2. Toggle Account Instructions on or off. When on, Billy applies your instructions to every answer. When off, Billy answers without them.

{% hint style="info" %}
The toggle controls whether Billy applies your instructions — it doesn't edit them. It's on by default; if no instructions are set yet, Billy simply answers as it normally would until you add them.
{% endhint %}

### Writing effective instructions

Account Instructions work best when they remove a specific ambiguity or set a specific default. A few patterns:

**Set a default cost type**

> When a question doesn't specify a cost type, always answer in net amortized cost.

This keeps every user's numbers consistent, regardless of how they phrase the question.

**Map an ambiguous term to one dimension**

> When someone refers to a "team," resolve it to the *Engineering Teams* Virtual Tag — not the native `aws:team` tag.

This stops Billy from picking a different dimension across sessions when several could match.

**Encode an account convention**

> Our production environment is identified by the `env:prod` tag. Treat "production" and "prod" as the same thing.

This teaches Billy the naming your account actually uses.

{% hint style="success" %}
Be specific and name the exact dimension, tag key, Cost Center, or Virtual Tag you want Billy to use. Vague instructions ("be accurate," "use the right tag") give Billy nothing concrete to act on.
{% endhint %}

***

### How Billy uses your instructions

* **Account-wide.** Instructions apply to every user in the account who queries Billy, so everyone shares the same baseline interpretation.
* **Permissions still apply.** Account Instructions do not change what data a user can see. Billy continues to respect each user's existing Finout permissions and data access. An instruction cannot grant a user visibility into data outside their access scope.
* **Per-question override.** A specific question that names its own cost type, dimension, or time period takes precedence over a default set in your instructions.

### Limitations

* Account Instructions currently apply to **Billy only**. Support for the [Finout MCP Server](https://docs.finout.io/ai-and-developer-tools/finout-mcp-integration) is coming soon.&#x20;
* Instructions are limited to **5,000 characters**.

### FAQs

**Do Account Instructions change what data Billy can access?**\
No. Billy always respects your existing Finout permissions and data access. Instructions shape how Billy interprets and answers questions, not what it is allowed to see.


---

# 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.finout.io/ai-and-developer-tools/account-instructions-beta.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.
