Use the fictional sample pack or an authorized upload, then inspect a real Smart Bite, index, answer, and citation.
Quickstart
This is the stored-workspace journey. It follows the existing product tour. It does not add another wizard. The sample pack is fictional. The product still uploads, discovers, reviews, extracts, and answers with that input. Do not substitute a precomputed result for a run that did not finish.
Use a stored workspace. The non-retaining path is a different tutorial.
1. Confirm access
Complete Before you start and Access and roles. You need a stored workspace and permission to upload. If the tour says this environment cannot run the stored tour, stop. That check requires a stored workspace, processing permission, and an approved full runtime. Record the message and escalate. Do not mark the pilot successful.
2. Add data
Choose one source. Both use the same later steps.
- Fictional sample. Open the sample dialog. It is labeled fictional. The pack is five real TXT files. Pick a Catalog collection, then choose add. Nothing is created until you confirm. Replaying the same pack reuses the reservation. It does not duplicate files.
- Authorized files. Upload files your organization allows, or pick an existing collection you can access. Stored upload formats are PDF, DOCX, DOC, TXT, MD, CSV, XLSX, XLS, and images PNG, JPG, JPEG, GIF, and WEBP. Images can be stored. Text extraction for the discovery pipeline accepts TXT, PDF, DOCX, CSV, and XLSX. A scanned PDF with no extractable text stays catalogued with reason
no_extractable_text.
Saving a file is not extraction. The tour waits until documents are readable. Discovery needs at least five distinct documents that contain text. Fix upload or processing errors before you continue.
3. Organize and approve
- Run discovery on the prepared documents. Bundata proposes a schema from the actual content. The tour does not skip this.
- Review the proposed fields in Schema Studio. Approve the review with the existing approval action. Starting the tour does not approve the schema for you.
- Run extraction on the approved configuration. The stage completes only when the saved extraction run finishes and Smart Bites are indexed.
Leave the screen during processing if you need to. Resume from the tour. A failed or partial run needs a person to act. It is not a completed milestone.
4. Inspect a Smart Bite
Open the same collection in Catalog. Open a real chunk. A Smart Bite is a focused passage tied to its source. Confirm the extracted fields and the passage. This is the same collection you uploaded into, not a demo overlay.
5. Ask and open the citation
- Open search and answers for this collection and confirm the knowledge source. The tour does not confirm it for you.
- Ask a question about the documents. You can edit the sample suggestion. Send it yourself.
- Open a citation on the finished answer and read the supporting passage. A citation is not a guarantee that the answer is correct. If there is no usable citation, or you left and the answer is gone, ask again. Questions are not stored as tour progress.
You are done with the first result when you can point to the saved run, the Smart Bite, the answer, and the citation that belongs to that answer.
If something blocks you
| What you see | What it means |
|---|---|
| Missing provider key | Generation or provider embedding cannot run. An owner or admin must save the organization key (OpenAI, Anthropic, or Google) in Settings → AI providers. See Models and credentials |
| Collection profile mismatch | The collection still uses its original embedding profile. Changing the workspace default did not rebuild it |
| Upload confirmed, nothing searchable | Confirmation queues processing. Wait for ready status, then discovery and extraction |
| 403 | Your role cannot perform that action |
| Tour not eligible | Stored workspace, processing permission, or full runtime is missing. Escalate with the workspace id |
Continue with First extraction if you need the run states, or Source connectors if the files live in S3 or a database.