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

# Context

> Shared business, data, and event knowledge that Data Analyst agents can use.

**Settings → Context** is the organisation-wide briefing for agents. Open it from the Agents section in Settings. Organisation admins and superadmins can edit it.

There are three tabs: **Business**, **Data**, and **Events**.

## Business

A single free-form note: company, markets, business model, and anything else agents should know. Saved on the organisation record.

On each Data Analyst agent (Agent Builder → Context), turn on **Include organization context** to append this note to the agent's prompt. Additional instructions on that same card are per-agent only.

## Data

Shared notes about how to use warehouse tables — gotchas, standard filters, joins. Include the table name in the note where it matters (for example `report_channels__performance — always exclude test campaigns`).

These sit alongside table and column descriptions in your connectors and [semantic layer](https://docs.getinteract.com/org-settings/semantic-layer/overview.md). Keep them aligned with the models each agent is allowed to use on [Data Access](https://docs.getinteract.com/agents/settings/data-access.md).

## Events

Time-bounded facts from your warehouse **context events** table (mapped in [Data mapping](https://docs.getinteract.com/org-settings/semantic-layer/data-mapping.md)). Interact lists them here; it does not edit the warehouse rows.

| Column | Meaning |
| - | - |
| **Start date** | When the event began |
| **End date** | Optional end |
| **Type** | Migration, promo, outage, definition change, maintenance, or other |
| **Event** | What happened |
| **Label** | Business unit / market; empty means all labels |
| **Metrics** | Affected metrics, if set |
| **Owner** | Optional owner |
| **Link** | Optional URL |

Events also appear as markers on marketing charts. On each Data Analyst agent, turn on **Include business events** so the agent can treat known campaigns or downtime as context instead of unexplained spikes.

> [!TIP]
>
> Map the context events table under Settings → Data mapping before this tab will show rows.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.