Skip to main content
Using Document Types

Document categorization with influence on metadata.

Sebastian Nedoma avatar
Written by Sebastian Nedoma
Updated over 9 months ago

Introduction πŸš€

In the fast-paced world of document management, effectively categorizing and managing various document types is crucial. fynk offers distinct document types, each is associated with unique metadata (refer to the "Utilizing Metadata" article for further details on the associated metadata and how to customize it) to ensure seamless sorting, searching, and managing of your documents.


Document Types Available in fynk

The following article explains the various document types available when using fynk.

Contract

A binding agreement between two or more parties that stipulates the terms and conditions of their interaction, primarily pertaining to business or trade.

πŸ’‘ Note: Additionally, contracts offer a secondary level of categorization: the contract type. Depending on the selected type, this further shapes the metadata fields that are associated with the contract. More details on the various contract types and their implications can be found in our "Contract Types" article.

Proposal / Quote

A business document that details the specifics of a project, task, or service. They often encompass project outlines, lists of products (services or goods), estimated costs, timelines, and terms.

Form

Standardized documents designed with predefined or fillable fields, which consistently collect specific information (e.g. order form, application).

Other

A catch-all category that includes a range of miscellaneous document types, such as reports, invoices, letters, memos, and more.


Understanding and leveraging the metadata associated with each document type in fynk will optimize your document management processes, ensuring that you can swiftly locate, review, and act upon any document in your repository.

πŸ’β€β™€οΈ Our expert Support Team is on standby. Engage with us via our chat feature or reach out at [email protected] for any assistance πŸš€.

Did this answer your question?