# Filing records and organising folders

> You'll file each document once and get its receipt back, and its folder will put it where your team expects to find it.

Source: https://unforged.ai/folio/docs/filing-and-folders

## Filing one document

Send the file as the body of POST /folio/records with its folder and name, and its class if it shouldn't take your default. Files up to 50 MB will go straight through; anything larger, up to 2 GB, will go up in parts as a large upload instead.

Every file will be checked for malware before it's filed, and one that fails won't become a record.

You won't be able to edit or replace a filing once it's made, so if the wrong document goes in, file the right one alongside it.

## Filing a whole import

For an import or a nightly batch, queue each file with POST /folio/filings and follow it with GET /folio/filings/{id}. Each one will go through the same checks as a single filing and end up either filed, with its record id, or refused with the reason why, so you'll always know which files still need attention.

You can pass the system a file came from, that system's own reference and the document's original date, and folio will keep them with the record. For classes that count from an event, the original date will be where retention starts.

## Folders, matters and subjects

Folders will nest as deeply as you like, and folio will create any that are missing when you file. A folder can carry a matter, a subject or both, and everything filed into it will inherit them, so a search for the matter will bring back the whole file.

Renaming a folder or moving a record will need a reason, and the ledger will show where it was before and after. A record's file, fingerprints, class and retention won't change when it moves, and you won't be able to move a record that's under a hold.

## Folders where every view will need a reason

Protect a folder that holds sensitive records, such as people files or a matter in dispute, and every view of anything inside it, at any depth, will need a reason, whatever your organisation's general setting.

Removing that protection will need a second person to approve it, and a sub-folder won't be able to opt out while its parent is protected. Renaming a protected folder, or moving a record out of one, will need a second person too.

## The routes

- `POST /folio/records`
- `POST /folio/filings`
- `GET /folio/filings/{id}`
- `POST /folio/uploads`
- `GET /folio/folders`
- `POST /folio/folders`
- `GET /folio/folders/detail`
- `POST /folio/folders/rename`
- `POST /folio/records/{id}/move`
- `POST /folio/folders/protect`
- `POST /folio/folders/unprotect`

## Related

- [How long each record will be kept](https://unforged.ai/folio/docs/retention-classes)
- [Finding records](https://unforged.ai/folio/docs/search)
- [The ideas behind folio](https://unforged.ai/folio/docs/concepts)

folio is in private beta, and these pages describe how it will work. We'll publish the full API reference when folio is generally available; until then, if you need a detail that isn't here, [just ask us](https://unforged.ai/contact?topic=other&product=folio).