Intely File System

The Intely File System (IFS) is per-organization file storage built into the platform.
It's the common ground between features: agent jobs write results into it, data processor
jobs read source code and inputs from it and write outputs back to it, Interface Server can
use it as a message source or destination, SFTP uploads land in it, and integrations read
and write files there.

Find it under Files in the main navigation.

Common file-based workflows

File-based integration is typical where structured reports or extracts must be transformed
before delivery. Representative examples:

• A hospital sends daily CSV reports that need to become FHIR Bundles for ingestion into a
  clinical data warehouse
• A payer system requires flat-file eligibility extracts, but the data is stored as nested JSON
• A digital health platform transforms Excel-based lab results into HL7 v2 messages for
  EHR upload

Structure

IFS is a normal directory tree. Every file and folder records its size, its extension, when
it was created, last modified and last accessed, and by whom.

Two flags are worth knowing:

• Hidden — the file exists but is filtered out of the default listing.
• Protected — the file cannot be deleted until protection is removed. Use this on inputs
  a scheduled job depends on.

Working with files

From the Files page you can create a New Folder, upload, download, rename, move, copy, copy
a file's path, and delete. Files can also be protected, which guards them against deletion.
Selecting several at once enables bulk delete, download and move/copy, and Download from Path
and Go to Path let you work by path directly. The listing shows Name, Size,
Modified At and Modified By.

Accepted file types

The file system accepts any file type. The upload control accepts any selection, and nothing on the write path validates an extension or a MIME type. If you can put it on disk, you can put it in Intely.

What does vary is how much the platform can do with a file once it is there. Three different tiers, and conflating them is the most common source of confusion:

The Interpreted list is the live set of Data Type categories, so it is the authoritative answer to "can Intely read my file?"

Where a specific format is required

A handful of features narrow the accepted set at the point of upload. These are the ones users actually hit:

Practical limits

• Files above roughly 1 MB are uploaded in chunks automatically. This is a limit of the web upload path, not of storage — it is not a cap on file size, and you do not need to do anything about it.
• The browser uploads at most 10 files per batch; larger selections are queued.
• On download, the content type is detected from the file itself rather than trusted from the extension, with .zip handled specially.

The Recycle Bin

Deleting a file recycles it rather than destroying it. The file's original path is
preserved, so restoring puts it back exactly where it was.

Emptying the recycle bin is permanent.

Paths in other features

IFS paths are how features hand files to each other. Some conventions to be aware of:

Access control

Three permissions govern IFS:

IFS is enabled per organization. If Files isn't in your navigation, your organization
doesn't have it turned on yet — contact your Intely representative.