App folders — where files from other apps land

Most files in Documents didn’t come from /documents/browse — they were uploaded from inside another app: a receipt attached to an Expense, an offer letter generated in HR, a signed PDF returned by E-Signatures, a proposal saved to a CRM Deal. Every one of these ends up as a real row in the document library, automatically filed into a predictable app folder owned by the module that created it.

• App folders live under a top-level Apps/ branch in the folder tree (e.g. Apps/Finance/Invoices/, Apps/HR/Employees/[Name]/, Apps/CRM/Deals/).
• The folder structure is chosen by the owning app — some apps organize by record (“one folder per project”), others by document type and year (“one folder per year for high-volume documents like invoices”), matching whichever fits how you’d actually go looking for the file.
• You never pick the destination folder yourself when uploading from inside another app — the platform routes it for you, so every file lands in a consistent, predictable place no matter who uploaded it.
• App folders still obey the same permission and sensitivity model as any other folder: if you can’t see the owning record, you generally can’t browse its attachment folder either.
• You can still browse into an app folder from /documents/browse to see everything a module has stored, or to bulk-manage older files — but day-to-day, you’ll usually interact with these files from the record’s own detail page (see Entity attachments) rather than by hunting through the tree.