Knowledge

Copy for agent Copied

Knowledge is the document library for source material such as product facts, case studies, and approved web pages. Use it to organize project and organization references, then select the documents relevant to a particular article. Knowledge has two tabs: Catalogs holds your documents, and Company profile holds the project’s company profile used as Brand input for articles. The profile is not a document; see Company profile for Content.

Knowledge is project-aware. Choose an active project from the sidebar before opening the page. The project determines which private project base and which organization shared base you see. Knowledge items are not automatically included in every article: the profile and source documents have separate roles, and you can choose documents in the article wizard.

Project and shared catalogs

The document browser shows the active project’s Project base and, when the project belongs to an organization, the organization’s Shared base. Each base has a folder tree and can also hold documents at its top level. Use folders to group source material; for example, keep product facts, case studies, and approved source pages in separate folders.

The project base is visible only in that project. The shared base can be read from each project in the organization, which is useful for material that should be consistent across clients or brands, such as approved company facts, current price lists, and legal wording. Moving something into the shared base makes it available to the organization’s other projects; treat that as sharing, not as a personal filing choice.

An account without an organization has no Shared base. If a shared tree is absent, check whether the active project belongs to an organization. Organization owners, admins, and members can write to the Shared base; viewers and external collaborators can read it. If a change to the Shared base is rejected, ask an organization admin to confirm your role.

Build a useful document library

Choose New folder to make a folder in the project base or within the folder currently open. Folders can be nested up to ten levels. On an empty project base, PromptEye may offer folders named after the project’s Prompt Intelligence groups. Select the proposals you want, edit their names if useful, or choose to start with an empty structure.

Choose Add documents to upload files, paste text, or import text from a website. You can choose the destination before adding material. Read Add documents and import website pages for supported formats, file extraction, sitemap behavior, and troubleshooting.

For useful source selection later, use one copy of each current document and place it in a meaningful folder. Knowledge searches folder and document names across both bases; it does not search full document contents. The screen may point out loose documents, duplicates, or content that is not linked to any prompt group.

Connect a folder to Prompt Intelligence

A folder in the Project base can be linked to one monitored prompt group. A linked folder shows a Material coverage checklist. The checklist counts readable documents in that folder and its subfolders across five kinds of material: hard numbers, service scope and audience, case studies and results, differentiators, and real source pages.

Use the content type on a document to say what evidence it contains. The checklist is a planning aid: missing kinds suggest what evidence could make future writing less generic. It does not block article generation. Folders in the Shared base cannot link to a prompt group because prompt groups belong to an individual project.

The folder link also helps connect organized material to prompt-focused workflows. If the linked group was deleted or archived, the folder displays a warning; link it to a current group if you want the checklist to work again. The folder and documents remain in Knowledge if the group goes away.

The checklist may also warn when the readable text in a folder and its subfolders exceeds 120,000 characters. The interface advises removing outdated material or splitting sources so the generator can focus on relevant text. This folder warning is separate from the article wizard’s 600,000-character limit for the sources selected for one article; use the selected-source counter in the wizard for that total.

There is an important distinction: the article wizard’s source picker can show documents from both bases, including loose documents and documents in folders that are not linked to a prompt group. Linking a folder is for its checklist and group relationship; it is not a prerequisite for a document to be selectable as a source.

Select folders or documents and choose Move to…, use the row menu, or drag the selection to a base or folder in the tree. A move changes where that material belongs; it does not make a copy. Dragging an already-selected item moves the selection together. You cannot move a folder into itself or one of its descendants.

When a document with the same name is already in the destination, resolve the conflict:

Replace uses the incoming document as the destination copy. The replaced document is sent to the trash. For a move, the old copy is recoverable there; for an upload replacement, the document record is updated to the newly extracted text and the previous manual text correction is cleared.
Keep both adds a suffix to the incoming name so both documents remain.
Skip leaves the existing destination copy in place. In a normal move, the conflicting source stays where it was; when you delete a folder and choose to move its contents elsewhere, a skipped conflicting file goes to the trash with the folder.

A normal move can be undone from its confirmation toast. If the move replaced a destination file, undo is unavailable because the old file was moved to the trash; restore it from there if needed. Undoing a folder move does not restore prompt-group links removed when it entered the Shared base; reconnect the folder to its group afterward if needed.

Moving a project folder into the Shared base removes its Prompt Intelligence group links, including links on subfolders. Those groups are project-specific and cannot describe shared material for every organization project. The documents move; the project group’s monitoring is not deleted.

Before sharing, review the contents and remove private or project-specific facts. Deleting from the Shared base or replacing a shared copy can affect every project that reads it.

Find, export, and recover material

Use search to find folder or document names in either base. Search does not scan text inside documents. The duplicate notices compare names and extracted character counts; they help find likely duplicate copies, but they do not prove that two documents have identical contents.

The Export menu offers a TXT file with a folder/document listing or a ZIP with the index and extracted .txt versions of uploaded files. The ZIP is limited to 100 uploaded files and 200 MB of source file sizes. Its index lists the tree, but the ZIP files include uploaded files only; documents created from pasted text or website imports are not included as separate text files. These exports contain the Knowledge text representation, not the original Word formatting, spreadsheet layout, PDF images, or page design. Export a smaller folder if it exceeds the ZIP limit.

Deleting a document or folder moves it to the trash first. A folder can be deleted with its contents or have its documents moved elsewhere, depending on the confirmation flow. The trash lets you restore an item to its former location or choose another destination. Name conflicts on restore are handled with a suffix. Items are permanently removed after 30 days; you can also permanently delete one or empty the trash sooner. Permanent deletion cannot be undone.

The article wizard uses saved document text. Deleting a source stops it from being used in new generation after it is removed; articles already generated are not changed. Take special care with a shared source because deleting it removes it from every project that can see that shared base.

Why the schema or Knowledge links may be unavailable

The sidebar disables project workspace links if you do not have access to an active project workspace. Select a project you can open or ask an owner to grant access. The Knowledge page also asks you to select a project before it can display its bases.

Website import has a separate sitemap requirement: importing one known page does not need a sitemap, but discovering subpages uses the website’s sitemap XML. If no usable sitemap is found, the importer cannot list subpages; that does not hide the Knowledge tab. See website import troubleshooting.