Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.abundly.ai/llms.txt

Use this file to discover all available pages before exploring further.

Each agent has its own file repository for storing and organizing documents, similar to an operating system. Both the agent and its users can create, read, and edit documents—and the platform tracks changes with full version history. Documents can be pure content, such as a text file or PDF or image, or they can be Interactive Apps or Agent Databases.
Documents panel showing a list of agent documents organized in folders
Agent documents work out of the box with no configuration. For external files like Google Drive or SharePoint, enable the corresponding capabilities.

Supported file types

Documents are plain text by default—typically Markdown for simple formatting. You can also upload other file types:
File typeHow it works
Text & MarkdownNative format, directly editable by you and the agent
Code filesJavaScript, TypeScript, HTML, CSS, JSON, YAML, and more—stored as editable text
SVG graphicsStored as editable text, rendered as vector graphics in preview
PDFs, Word, PowerPointTranscribed to text—original file preserved for reference
SpreadsheetsTranscribed to text—original file preserved for reference
ImagesVision AI generates a text description the agent can read
AudioAutomatically transcribed to text
VideoAudio track extracted and transcribed (video frames not analyzed)
For uploaded files (PDF, audio, etc.), the platform creates a text version that the agent works with. You can access the original via the Original file button. If you edit the text, it will diverge from the original—the agent always works with the text version.

Working with documents

Click any document to open it in a modal with a mode selector. Available modes depend on document type and context.

Text mode

The text representation of the document—this is what the agent sees and works with. You can edit the text directly here.

View mode

A visual rendering of the document, depending on its type:
  • Markdown → Rendered with formatting, headings, and links
  • React or HTML → Live rendered application or web page
  • Mermaid diagrams → Rendered flowcharts, sequence diagrams, etc.
  • SVG → Rendered vector graphic (editable as text)
  • Database documents → Interactive table view of the data
Here is an example of a preview of an Interactive App document.
Document view mode showing a live Launch Dashboard app with countdown timer, metrics, charts, and progress bars

Data mode (for databases)

For agent databases, you can open a dedicated Data mode to view and edit raw JSON plus the schema.

Changes mode

A version timeline showing every change made to the document. Click any version to view it, or click between two versions to see a diff of what changed. You can approve or undo individual changes, or revert to any previous version.
Changes mode showing version timeline and inline diff with additions and removals highlighted

Visibility levels

Documents have two separate controls:
  • Visibility to the agent controls what your agent can discover and read while working.
  • Publishing controls whether people outside your workspace can open a public link.
By default, agents know which documents they have (name and summary) and can read the full content when needed. You can adjust visibility per document:
LevelBehavior
FullAgent always knows the full content—included in every prompt alongside instructions. Use for essential context the agent should never forget.
Summary(default value) Agent knows the document exists and its summary. Reads the full content only when relevant. Good for most documents.
HiddenAgent cannot see or find this document. Use for your own notes or materials not relevant to the agent’s job.
To change visibility, click the visibility icon next to the document name in the Documents panel.
Document visibility level dropdown in the Edit Document modal
Start with the default Summary visibility. You can add many documents without overloading the agent’s context—it will read full content only when needed.

Adding documents

You can add documents in three ways: 1. Upload or create directly Click Documents in the sidebar, then drag files from your computer or click Create document for a new text document. 2. Save from a conversation Drag a file into the chat, discuss it with the agent, then ask it to save the result. For example:
  • Drag a meeting transcript, ask for a summary, then “save this as an agent document”
  • Ask the agent to draft a newsletter, refine it together, then “save this to the newsletters folder”
When the agent opens content in the side panel (a chat-scoped document), click the menu and choose Save as agent document to promote it to a permanent agent document without asking the agent to do it.
3. Instruct the agent to create documents automatically Add instructions like:
  • “When processing an invoice, add it to the processed invoices database”
  • “Save all incoming emails to a message log”
  • “After posting release notes, save a copy to the ‘release notes’ folder”
  • “When you receive an email with an attachment, save it as an agent document”
4. Download from a public URL Ask the agent to fetch a file from a URL and save it—for example, “Download the PDF at https://example.com/report.pdf and save it to the reports folder.” Images, PDFs, Markdown, and plain text are all supported.

Organizing with folders

Documents can be organized into folders. Create folders in the Documents panel and drag documents to organize them. Reference folders in your agent’s instructions: “Save meeting notes to the ‘meetings’ folder.”

Version control

Every edit—by you or the agent—creates a new version automatically. The Changes mode lets you:
  • Browse history — See all versions with timestamps and who made each change
  • Compare versions — Side-by-side diff view to see exactly what changed
  • Approve or reject — Optionally mark changes as approved or rejected (rejecting creates a new version with that change undone)
  • Revert — Roll back to any previous version if needed

Publishing documents

You can publish a document to make it available to anyone with the link. Open the document menu and choose Publish (or Publish details if it is already published). Anyone with the link can view the document—no Abundly account required. If it is an app, they can interact with it. Published documents are marked with a Published badge in the Documents view. Use cases:
  • Share a live dashboard with colleagues
  • Publish an input form for data collection
  • Share reports, drafts, or documentation externally
  • Create a public-facing interactive app
You can also publish Interactive Apps and Agent Databases. For agent databases, choose what public users can do:
  • Read to query and view data
  • Create to insert new items
  • Update to modify existing items
  • Delete to remove items
For uploaded files (like PDF, audio, or spreadsheets), you can optionally enable Also publish original file so anyone with the link can download the original file without logging in. If a published app depends on other documents, publish those documents too (with at least Read enabled) so the app can access them from the public link.
Publish document dialog
Published apps update automatically. Create a dashboard, share the link, and your colleagues always see the latest data.

Editing and searching documents

Agents don’t need to rewrite entire documents to make changes. They can:
  • Edit precisely — Replace, insert, or append text
  • Search within a document — Exact match, full-text, or semantic (meaning-based) search
  • Find documents — Fuzzy keyword matching across names, descriptions, and content
  • Rename and describe — Update document names and summaries
Use semantic search within documents to find content by meaning, not just keywords. For example, searching “global warming” can find sections about “climate change.”

Downloading documents

You can download individual documents in several formats:
  • Download text — Get the text content as Markdown, plain text, or other formats
  • Download as MS Word — Convert Markdown content to a .docx file
  • Download original — For non-text files (PDF, audio, etc.), download the original file
To download multiple documents at once, use Download all in the Documents panel to get a ZIP file containing everything in the current folder, including any nested subfolders. You can also choose Download folder as ZIP from a folder’s menu to download just that folder’s contents.

Documents as extended context

Agent documents are a powerful way to give your agent additional context without bloating its instructions. Instead of pasting everything into the instructions, store reference materials as documents:
  • Checklists — Step-by-step procedures for specific tasks
  • Templates — Formats for reports, emails, or communications
  • Guidelines — Company policies, compliance rules, or style guides
  • Reference data — Product catalogs, contact directories, FAQs
With Summary visibility (the default), the agent knows these documents exist and reads them when relevant—keeping its context focused while still having access to everything it needs. For best results, guide your agent on when to use specific documents:
  • “Before responding to compliance inquiries, read the compliance guidelines document first”
  • “When drafting emails, use the email template in the templates folder”
  • “All meeting notes are saved by date—search for them when you need context”
If you don’t want the agent to create or edit documents, disable the Edit Documents capability in settings.

Chatting about documents

Click Chat about this next to any document or folder to start a new conversation with that content as context. The agent has immediate access to the selected document(s), making it easy to ask questions, request edits, or work through the content together.

FAQ

It depends on the document type:
  • Agent documents (created directly in Abundly) are stored in EU data centers in Stockholm, Sweden. They remain fully under your control—you can delete them at any time.
  • External documents (Google Drive, SharePoint, etc.) remain on their original provider’s servers. The agent accesses them through your permission but doesn’t copy them to Abundly’s infrastructure.
For example, if you share a Google Doc with an agent, the document stays on Google’s servers and is accessed only through your authorized connection.See Infrastructure & Compliance for details on data residency and security.