Upload files to the Knowledge Base
Upload files to give the Assistant content a website import can't reach: the Knowledge Files an ePublisher build produces, and Reasoning Fuel such as your own notes, references and PDFs. Files you add are staged and upload when you click Save Changes.
Add files
In AI Assistants, open the Assistant.
On the Configure tab, go to Knowledge Base.
Drag the files onto the dropzone, or click it and choose them. They are listed under Adding.
Click Save Changes.
The files move to Uploaded, each with its status, and the Knowledge Base shows the Indexing banner. When the banner clears, the Assistant answers from them. To take a file out of Adding before you save, select it and click Remove Selected (the trash icon).
Rule | Limit |
|---|---|
File types |
|
Size | Up to 512 MB per file |
Files per save | Up to 20 |
Storage | Every file counts toward the plan's storage cap, shared by all the organization's Assistants. See Knowledge storage. |
Links | Relative links in |
Remove files
Under Uploaded, select the files.
Click Delete Selected (the trash icon). The files move to Deleting; Undo Delete moves them back.
Click Save Changes.
The files leave the Knowledge Base when indexing finishes. An imported website is removed from Websites instead; see Import a website.
Replace a file
Uploading a file again adds a second entry rather than replacing the first. To replace a file, select the old one under Uploaded, click Delete Selected, add the updated file, and click Save Changes, all in one save.
Near the plan's storage cap, the old file still counts until its removal has finished indexing. If the upload is refused, remove the old file and save first, then upload the updated one once the Indexing banner clears.
Upload statuses
File | While it uploads | Once it is live |
|---|---|---|
| "Pending upload…", then "Uploading…" | "Upload complete" |
| "Queued…", then "Processing…" with a progress bar | "Completed" |
A file that didn't go live shows "Failed:" or "Archive failed:" and the reason, and the Assistant keeps answering from the content it had. See Knowledge Base problems.