Ask questions of your own documents and get answers with a citation for every claim: the page or section they came from, opened at the exact place. Knowledge Studio is the window for Recall, IW's knowledge index. Open it from Analytics > Knowledge Studio.
A library is one index (a single SQLite file under ${assets}/.recall). The left rail lists them; demo pack marks ready-made libraries such as iw_help, built from IW's own manuals, so you can ask a question straight away. Use + to create a library and Delete library (click twice) to remove one. Deleting removes the index only, never your documents.
Open Sources, then Files... or Folder... (IW's file browser) or type a path such as ${assets}/docs/procedures and press Add. PDF, Word (.docx), HTML, text and Markdown are read. Documents stay where they are: Recall stores a portable path and a content hash, so unchanged files are skipped the next time and changed ones are re-indexed.
Indexing runs in the background with a progress bar and time left; you can keep working, Cancel (the library stays consistent) and Resume later.
Type a question in Ask and press Enter. You get numbered citation chips and the passages that answer it; the first citation opens on the right at its page or section, and clicking any chip or passage opens that one. Tick Answer written by Claude to also get a written answer that cites the same numbers (this needs the Claude CLI on this machine). Recent questions are kept in the left rail.
When nothing in the library answers the question, Knowledge Studio says Not found in this library instead of guessing.
In Sources, type a tag in a source's + tag box and press Enter (click the x on a tag to remove it). In Ask, click tags under the question to search only sources with those tags, e.g. only #procedures or only one customer's documents.
The same libraries are available to workflows through the Recall Add and Recall Ask nodes, and to scripts and AI agents through the recall_* MCP tools (see the MCP page).
A library can answer questions right next to your live data (see Sheets, Dashboards & Documents):
=RECALL("library", "question") puts the answer text in a cell; =RECALL("site_safety", "How many people were in the entry area at the busiest moment?", "count") gives a number you can use in other formulas.Answers are cached per library and question. A dashboard refreshing every second does not ask again; an answer is asked again when the library changes (sources added or re-indexed), when you press refresh, or after the block's interval (10 minutes by default). While an answer is being worked out the block shows a small updating... state and keeps the previous answer.
Demo: open Safety Management > Site Safety Recall Dashboard. Its dashboard puts the live people count next to answers from the site_safety_procedures library (a fictional site safety procedure) and a count from the site_safety footage pack; the workflow also has a sheet with =RECALL cells and a shift report document.
In Sources, a movie row has a Describe button. It opens the clip with a scrubber over the activity curve IW measured, and two tabs on the right.
Describe is for saying what the clip shows, in your own words:
#tags.clips.json next to the movie and re-indexes the clip, so Ask finds the notes and Solution Studio reads them when the clip is tagged.Calibrate turns pixels into real units (mm, cm, m or inches), so measurements, answers and generated apps use real distances:
clips.json and a line such as Calibrated: 1 px = 90.7 mm on the car park plane (RMS 36 mm) is added to the clip's description. Ask can cite it, and Solution Studio uses it to build apps that measure in real units. Tick Also add it to the shared list to offer it under Start from for other clips from the same camera; surfaces saved in Camera Studio are listed there too. Remove deletes only the calibration and keeps the clip's notes.
The Scale bar method works the same way: drag A and B onto the ends of something you know the length of, type the length, then measure.
Speech transcription. In Sources, Speech transcription picks the Whisper model a library uses for audio and video: Small is the default and suits most footage; Medium is better for noisy or non-English audio but about 2-3x slower with about 3x the memory; Tiny and Base are faster and rougher; Large-v3 is the most accurate and wants a GPU; Off skips speech. Language is detected per file unless you fix it (English, Japanese, German, Spanish, French or Chinese). A model is downloaded the first time it is used (Medium is about 1.5 GB), and the job progress says so. The setting applies to sources added afterwards; after a change, Re-transcribe re-runs just the library's movies and audio as a background job you can cancel and resume. Your last choice becomes the default for new libraries in this browser.
Text recognition (OCR). Below it, Text recognition (OCR) reads text that is only in pictures, offline, on the CPU: Scanned documents and images (the default) reads PDF pages that have no text layer and still images, and a citation names the page (scan.pdf p.3); Scanned documents, images and footage also reads sampled movie frames (one every 10 s, so labels, plates and screens become searchable), and text that stays on screen is cited as one time range (gate.mp4 @12.0-18.0s); Off skips OCR. Each recognised line and its box is also kept as a row in table ocr for recall_sql. The setting applies to sources added afterwards.