What is a document management system? Tying files to the customer record

The parts of a DMS are well known: a central store, tags and search that find a document by more than its name, a history that keeps earlier versions, permissions that decide who can see what, an access log that shows who opened what, and rules that set how long a document is kept.

When assessing a DMS, think by document type. A contract is kept for a long time and must not change; a drawing is revised often; an invoice is kept according to tax rules. One rule does not fit them all, and the system should recognise the difference. The need a DMS meets comes from everyday work: the time lost searching for documents and the cost of work done from the wrong one. Scanned paper documents belong to this order as well; the scan of a signed contract enters the record along with where the original is kept.

Example scenario: Picture an architecture practice in İstanbul. The client asks for another revision, the contractor is working from the previous drawing, and nobody in the office is sure which file is the latest. A DMS answers the question because it leaves it to the record, not to the file name.

The problems of a shared folder build up over time. Everyone names files by their own rule. Copies of the same quote multiply in different folders. Some important documents stay in inboxes as email attachments. The files on a departing employee's desktop leave with them.

In an accounting office the same invoice PDF sits in the shared folder, in email, and on a desktop; which one was booked is only clear by opening them. Rules written for the folder structure are usually short-lived too; when the person who set them leaves or work speeds up, everyone goes back to saving files wherever is easiest.

The hardest question stays unanswered too: who downloaded this contract? A shared folder usually does not record it. In a dispute or a data leak, without that information you are left with guesswork.

Example scenario: Picture a showroom. After delivery the customer calls and asks for the invoice and the warranty document. With a folder structure the sales rep searches first by name, then by date, then by invoice number. With files tied to the record, they open the customer card: quote, contract, invoice, and delivery note sit side by side.

A side effect of tying files to the record is that searching changes. You do not need to remember the file name; knowing the customer, the subject of the quote, or the project is enough.

An order tied to the record asks for a new habit too: saving the file to the customer card, not the desktop. The habit settles when the card is the easiest place to save; if the card is already open, the file goes there.

In Corex360 this principle runs through Corex Drive: files sit inside the record they belong to. On the customer card, the Files and Drive tabs sit next to the quote, contract, and project tabs. How drawings and approval files build up in these tabs is shown in architecture practice project tracking.

In a system without version history, even if you find the right document you cannot tell which change was made when. Without defined permissions, the payroll file is in front of everyone. Without an access log, nobody knows who opened it.

In an accounting team the three work together: the final signed contract sits on the record, only those whose role allows it can open it, and every open and download is written down with who and when. If something goes wrong, the question is answered from the log, not by guessing.

Retention belongs in this picture too. Some documents must be kept for a legal period, while some personal data should be deleted once the purpose of processing is gone. When a document is tied to the record, which rule applies to it can be read from the record as well. Defining permissions by role rather than file by file makes the work easier: sales sees quotes, accounting sees invoices, the manager sees everything.

If the architecture practice sends the drawing to the contractor as an email attachment, the file has left the practice's control. Even after the job ends, it sits in the contractor's inbox, perhaps on someone else's computer. A time-limited link has an end; when the job is done, the link is closed.

Email attachments have another problem: large drawing files often do not fit, and the office falls back on personal file-sharing accounts. The company's document then sits in an account the company cannot see. With a time-limited link, the office knows which version the recipient opened; in a dispute, "I never saw that drawing" does not stand against the log. Who each shared link went to should sit on the record as well; seeing which links are still open when the job ends is the first step to closing them.

In Corex Drive, sharing uses a time-limited, permission-bound link; the link can be revoked, and every view and download is logged. You can find short answers on sharing, access logs, and hosting on the Corex Drive and security questions page.

Signed contracts and legal files are tied to the relevant record; when an employee leaves, the document stays in the company, on the customer card. Permissions are role-based, and permission changes are logged. Data lives in a company-specific space on Corex360 Cloud or on your own server. The scope and limits are set out on the Corex Drive document management page. Version history is not promised in Corex Drive today.

Corex Drive works not like a separate file server but like a tab on the customer card. The salesperson who prepares the quote, accounting who keeps the contract, and the project team who shares the drawing all look at the same file inside the same record.

Bring your own document setup to the demo: let us look side by side at how many places you check today to find a contract, and where the same document sits when it is tied to the record.

Corex Drive has these sections: My Drive, Shared spaces, Labels, Starred, Recent, Shared and Trash. Shared spaces are common folders set up by department or topic, and the organisation defines its own labels. The dashboard shows personal and shared storage use and the spread of file types. Every view and download in Drive is logged, and sharing uses timed, permission-bound links that can be revoked.