Restricted to organisation admins and superadmins.
Business context
The general briefing about your organisation — the kind of thing you’d hand a new analyst on day one.
Business models — add one entry per business model if you run more than one:
Business context — a free-form list of individual facts agents should know, e.g. “High return rates — largest cost driver in the business”. Add as many entries as you need.
Business events
Time-bounded facts — things that were (or will be) true for a specific period, rather than always-true facts about your business. Use this for downtime, campaigns, and other events that could explain a spike or dip in the data an agent is analysing.
Example:
2026-11-24 → 2026-11-30 (NL) — Black Friday campaign live
Data context
Shared notes about specific tables — gotchas, standard filters, join logic, or anything not obvious from the table and column descriptions in your connector. Reference the table name directly in the note (e.g.report_channels__performance — always filter out test campaigns using...).
Unlike business context and business events (which are included or excluded as a whole), data context entries are selected individually per Database Query Agent — so a subagent only receives the notes relevant to the tables it’s allowed to query.
How this feeds into agents
Each agent (and each subagent) has independent checkboxes to include Global context (its own text), Organization context (Business context, above), and Organization events (Business events, above) in its system prompt. See Agent Builder → Context for defaults and how to configure them per agent.Business context and business events can also be edited from Settings → Organization, on the same organisation record — both places write to the same data, so changes made in either show up everywhere. This dedicated Context page under Agents is the recommended place to manage them day-to-day.