Company profile and document sources
PromptEye has two distinct sources that people may call “knowledge.” The company profile is saved on the project and edited on the Company profile tab of Knowledge or as Brand input in the article wizard. Knowledge documents are separate records in the project or organization library. Understanding the difference helps you choose what to update for the whole project and what to select for one article.
The company profile
Section titled “The company profile”The company profile describes the project’s business in six fields: industry, product or service category, target audience, ideal customer, operating area, and company description. When you set up your first project, it can be filled from your website; review that text and remove claims your organization cannot support.
Saving the profile updates the project, not just the article currently open. PromptEye uses it when it prepares briefs and articles and when it evaluates how well monitored prompts fit your business. When a brief is created, its company-knowledge context is captured for that brief; the article then uses the saved brief context. Keep stable company facts here. Put article-specific instructions in that article’s brief or editorial guidance.
Knowledge documents are separate sources
Section titled “Knowledge documents are separate sources”Documents live in the Knowledge page’s Project base or organization Shared base. They can be uploaded files, pasted text, or imported web pages. They are not merged into the company profile. In the article wizard, select the specific documents that should support that article. The saved brief keeps document references; when article generation runs, it reads the current stored content for those selected documents. Replacing or removing a document can therefore affect a later generation from a saved brief.
The picker can show loose documents at the root of either base, and it can show documents in folders that are not connected to a prompt group. A folder-to-prompt-group connection supports the folder’s material-coverage checklist and organization; it does not make its documents automatic article sources. When the picker opens, a few documents may already be selected; they are not chosen for the prompt, so review the selection each time.
One thing to know: corrections made with Edit text are shown in Knowledge, but the article writer uses the text read from the original upload. If a correction must be used by the article writer, add the corrected text as a new pasted-text document or upload a corrected file, then select that document. See Add documents and import website pages for the import details.
How the two sources relate
Section titled “How the two sources relate”| Source | Where you maintain it | How it reaches an article |
|---|---|---|
| Company profile | Knowledge → Company profile, or Brand input in the article wizard | Project-wide context is captured when the brief is prepared and carried into article generation. |
| Knowledge document | Knowledge → Project base or Shared base | You select it for the article; its stored content is read when generation runs. |
| Published article citation | Content library, using the article’s live URL | Tracks whether an already published page is cited; it is not a Knowledge source document. |
Company knowledge and Knowledge documents can both inform one article, but they have different editing locations, sharing scope, and selection behavior. Citation tracking is a later workflow for a published URL and does not use the source-document library as its target.