Documents, Notifications & Support

Organisation in the Documents module is hierarchical. There is a root level and sub-folders beneath it, and the interface provides parent folder navigation so a user can move up and down the tree. Because the folder tree is the primary structure, grouping related files is a matter of placing them in the right folder rather than tagging them individually.

The single most important integration concept is linked-entity tracking. A document does not only live in a folder; it can be associated with a specific business record elsewhere in the system. This is what lets a file behave as an attachment on another object instead of a standalone upload. The same underlying attachment capability is reused by other modules — for example, support tickets can carry attached documents.

Why linking matters

• A contract scan can be kept beside the contract record.
• Supporting paperwork can travel with the transaction it justifies.
• Files remain centrally stored and governed while still being reachable in context.

Moving a document between folders changes its organisational home without breaking its links, because the folder location and the linked entity are distinct pieces of information. This separation lets administrators reorganise the folder tree over time while the record associations stay intact. All of this folder and attachment behaviour is served by the document folders and attachments APIs, keeping the client a thin consumer of a consistent backend model.