Skip to main content

Files and media

Konnie can use files as task context and produce downloadable artifacts. File upload, content analysis, and attaching a result to an operational record are separate steps. Available analysis depends on the configured provider, tool policy, sandbox access, and the surface you are using.

Upload a source​

  1. Open the intended conversation.
  2. Use the file upload control or drop files on the composer.
  3. Wait for each upload to finish. Check the attachment names and remove any unintended draft attachment.
  4. Add a request identifying the relevant content and desired output.
  5. Send the message and inspect the analysis result.

Example: “Read worksheet Materials in this workbook. Keep article codes as text, identify duplicate codes, and prepare proposed materials with a source row for each. Do not invent missing units.”

Removing a draft attachment removes it from that message; it is not confirmation that the uploaded object has been physically deleted. File and conversation deletion follow the configured retention workflow.

Formats and limits​

The chat uploader accepts the following categories. Acceptance for storage does not guarantee every format can be analyzed or previewed by your configured provider.

CategoryCommon examplesTypical use
DocumentsPDF, DOCX, PPTX, TXT, Markdown, RTF, ODT, ODPInstructions, specifications, extraction, and summaries.
TablesXLSX, XLS, XLSM, CSV, ODSCalculations, comparisons, normalization, and proposal preparation.
ImagesPNG, JPEG, WebP, GIF, BMP, SVG, HEIC/HEIFVisual inspection and annotated evidence.
AudioMP3, WAV, AAC, OGG, FLAC, AIFF, M4A, recorded browser audioTranscription and spoken task input.
VideoMP4, MOV, AVI, WebM, MKV, MPEG and other recognized video typesTask evidence and video inspection.
3D objectsGLB, self-contained glTF, STL, OBJShape analysis from multiple sides.
Archives and other filesZIP, TAR, GZIP, RAR, 7Z, structured textSandbox inspection, conversions, or source transfer.

Chat uploads are limited to 100 MiB per file and 100 attachments per message. Audio transcription has a separate 25 MiB limit. Video analysis and automatic attachment indexing can have lower configured limits. Executable application and installer types are rejected. Do not rename an executable to bypass validation.

Use a small relevant set of files and identify which ones matter. Detailed model context is bounded, so attaching many files does not guarantee simultaneous full-content inspection. For a large collection, ask Konnie to inventory it and work through targeted groups.

Understand a 3D object​

Upload a GLB, self-contained glTF, STL, or OBJ file and ask Konnie to identify the object or explain its visible features. Konnie renders the shape from multiple sides and analyzes those views with your configured image-understanding provider. You can ask follow-up questions about the same file in the conversation.

The rendered views use neutral surfaces. Textures and external material libraries are omitted. glTF geometry buffers must be embedded in the file; export a GLB if your glTF refers to separate geometry files. Convert STEP or IGES to a supported format before uploading. Large, compressed, or damaged models may need a simpler export.

Object identity and possible function are AI interpretations. Shape analysis does not establish materials, exact dimensions or tolerances, hidden internal defects, or quality release. Check manufacturing decisions against the authoritative CAD specification and inspection evidence.

Preview, download, and annotation​

Select an attachment to open its available preview. Video previews provide playback; files without an inline preview can still offer download. If a preview or download has expired, reopen it from the conversation to request current access.

Where the image or video annotation editor is offered, add markings that identify the defect, part, or relevant interval, then send the annotated result with a short explanation. Treat an annotation as supplied evidence; it does not establish a defect classification or a quality release by itself.

Analysis and generated artifacts​

Ask for extraction, a calculation, a summary, a conversion, or a report explicitly. For scanned PDFs, poor images, handwriting, or unusual workbook structures, review extracted text and key values against the source. Encrypted or damaged files may need a readable export first.

Sandbox analysis, when enabled for your user, can inspect spreadsheets, Office documents, archives, and other sources and prepare output files. A returned artifact is an analysis result. Download or attach it using the offered result controls. Ask for units, source references, assumptions, and a check of totals when generating a report.

“Prepare configuration from this file” can produce a reviewable change set. It does not by itself make those records live.

Find attachments already in Ennea​

Konnie can search accessible entity attachments when its tools and your record permissions allow it. Ask with an entity, filename, document type, or content description: “Find the current work instruction attached to Assembly A and show its version and source.” Metadata search and indexed content search are different; content coverage depends on enabled indexing and successful processing.

Administrators manage automatic attachment analysis and bounded backfills in the Control Center. A missing search match can mean the file has not been indexed, analysis failed, or you lack access. Ask Konnie to inspect the specific accessible attachment rather than treating a missing match as proof that it does not exist.

Files in Live and Apps​

In Live, use Files, wait for the saved confirmation, and then ask a spoken question about the file. Uploading during a call saves context; it does not automatically start analysis. In an App, file upload is available only when the App author enabled attachments and the required analysis tools. See embedded assistants.

Troubleshooting​

If an upload fails, check size and type, wait for network recovery, and retry the failed file. If storage is unavailable, ask an administrator to check storage readiness. If analysis fails, specify a smaller page range, worksheet, or video segment, or export an accessible format. If processing is prohibited or a tool is disabled, the administrator must review the relevant policy. A successful upload does not override that restriction.

Only upload information needed for the task and permitted by your organization's policy. See security and deployment and Konnie Control Center.