Briefs
A brief is a short text agents read before they answer, such as a company overview or a decisions log. A brief prompt writes it from your files and datasets and can keep it current on a schedule.
Files and briefs
- Files, under Library in the sidebar, holds the files synced from Google Drive, SharePoint and OneDrive, as they are. See Files for how to sync them.
- Briefs, under Definitions in the sidebar, holds short briefs written from those files (and from your datasets): a company overview, a decisions log, the definitions behind your KPIs. These are what agents read first.
Brief prompts, under Definitions in the sidebar, is how files become briefs: a brief prompt reads a company's files, and can read its briefs and approved datasets too, then writes a brief, by hand or on a schedule.
Create a brief prompt
Admins and above create brief prompts. On Brief prompts, choose New brief prompt and fill in:
- Name and Instructions: what to write and how to lay it out, in plain language.
- Company: the company whose files it reads. Narrow it with Connection, or with Folders to read under Advanced when only some folders matter.
- Schedule: Manual, Daily, Weekly or After each sync. After each sync runs it within about 15 minutes of a sync of the company's data, at most once an hour. If you chose a connection, only that connection's syncs count. A failed sync does not.
- Reading limit, under Advanced: the most text the brief prompt reads in one run. A run over it fails rather than reading less. Leave it empty for the default.
Open the brief prompt and choose Try it to see the result on a small sample without changing the brief. When it reads well, Update the brief writes it, and every later run adds a new version. A brief prompt that fails three times in a row pauses itself; fix it and choose Resume.
Your agent can also create brief prompts for you, including ones that read your approved datasets or other briefs alongside the files:
Create a weekly brief prompt for Northwind that reads the board meeting notes folder and keeps a decisions log: each decision, its date, and who owns the follow-up.
Approve a brief
A brief is either Approved or a Draft. Agents only read approved ones. The first time you choose Update the brief, it creates the brief as a draft, so you can read it before anyone relies on it. On Briefs, open the brief and turn on Approved, the same switch a dataset has. Admins and above can approve a brief, and turning it off returns it to a draft.
Your agent can approve one too, with a Read/write personal or whole-workspace key, once its brief prompt has Agents can run it turned on (it starts off for a brief prompt made in the dashboard):
Approve the Northwind decisions log brief.
A brief is tagged to the company its brief prompt reads. On Briefs, the No company count shows any that a key limited to some companies can't see.
Briefs to write first
On Briefs, Ideas for getting started suggests the briefs worth having early for each company, and shows which it already has. A few that pay off quickly:
- A company description: what it sells, to whom, and how.
- KPI definitions, so "active customer" means one thing.
- Accounting conventions, such as the fiscal year and currency.
- Data caveats and known gaps, so nobody trusts a number that should not be trusted.
- A decisions log.
Ask about briefs
Once approved, briefs are part of what your agent can read. Ask for them directly, or ask a question that needs both:
What does the Northwind company description say about its largest customers, and how does that compare with its revenue by customer this year?
Your agent reads the briefs first. When none covers the question, it can search the files too. Check what a search finds before you rely on it. Briefs follow the same access as datasets: an agent key only sees the companies it was given. See Best practices for how briefs and datasets work together.