External content

External content can be made available to Elephant AI. The external content will be fed to the assistant using specific instructions and files.

The title is meant as a way for navigation. Can be overwritten by instructions.

Files are fed to the assistant. Keep filenames simple, and use the right file extension.

By default, Elephant AI provides all the instructions in English. Using a single language for instructions is a good practice, and should be enforced.

	Description
Title	The title is meant for the user to navigate contents. Keep the name simple and meaninful.
Active	Active AI content will be fed to the assistant. The main use of `active` is to allow editing without publishing.
Restricted	When restricted, the content is only available to `Premium Networking` users and `admins`. Otherwise, the content is available to any user with permission to access the assistant.
Instructions	The instructions will tell the assistant how and when to use the information provided by the files. At this point it's important to follow some rules: The recommended format for instructions is Markdown. Start the instructions with a header. By default, it would be `# Title Query Policy`. Despite being free to change this header, it's highly recommended for you to keep it. Include the context in which the files should be inspected. Be imperative about it. E.g. Use `file` ONLY when the user asks for `context`, replacing file with the filename and context with the keywords that represent this content. Mention all the files you have uploaded, and the reason why it should be inspected.
Documents	The documents you upload will be fed to the assistant. You can use as many formats as you want. Have in mind, though, that the most common formats will work better. That is, using plain text, with strong markup for starting/ending each item in the file, may work better. Keep in mind: Use strong field names, E.g. `name=Item name`. Use always the same fields for each item. E.g. do not `name=Item name` in one item and `title=Item name` in another. Whenever possible, use a unique field value at top of the list of fields. Fields with much verbosity are better kept at the end of the field.

Printer version

English

05/12/26 14:13

Lluís Turró Cutiller

Serveis BaaS BaaS Home Server Email Outsourcing Support Synergies Case Studies Distribuïdors Incubadora Anem per feina BaaS DEMO El més social Gestor de projectes Manteniment informàtic

Projects Project Desk Android Comunicació Desplegament JavaEE Object Pascal

Organization Foundation Work with us Developer Content creation License ZK Open Source License Technology Partners Calendars Activity Agenda Public calls Downloads Foundation Hub Legal notes

Documentation BaaS Single Sign On BrightSide Application Framework Contactes Adjunts Dossiers Publicacions Customer Relationship Financials Resource Planning Components Elephant Getting started Content Layouts Users Components Administering Best Practices Processos Feedback Javadoc Dependencies Tutorials Fundació Fundació i Imperi Segona Fundació Els limits de la Fundació Fundació i Terra Valors Treballa amb nosaltres Marketing Definició d'entitats

Publications Totes les categories Blog Customer Relationship New & Noteworthy

lluis@turro.org
Tel. +34 609323947