Introduction
This article is designed to help account owners and admins set up fynk quickly and efficiently. It provides all the essential information about tags, metadata and contract types to ensure a smooth start.
Tags
Tags are one of the most effective ways to organize, visually highlight, and filter your contracts in fynk. They help streamline your dashboards and document lists, making navigation and retrieval faster and more intuitive.
What Kind of Data Should You Use Tags For?
Tags work best when the same values apply to multiple documents. However, keep in mind that the more tags you use, the harder they become to manage. That said, tags are incredibly versatile - they offer two layers of clarity through text and color.
For example:
You could tag all your subsidiaries in blue, using the text to indicate the subsidiary’s name. A quick glance at the tag color would show which entity the document belongs to.
Use color coding to represent other dimensions, like:
Red for urgent or high - priority documents
Different colors for different document types (e.g. yellow for NDAs)
Use Cases for Tags
Document Types
Example: All NDAs are tagged in yellow, making them easily distinguishable.High-Volume Projects or Key Customers
Example: Tag documents linked to large projects or important clients to group and access them faster.Locations
Example: If your company operates in several regions, use tags to reflect the document's related location.
When Not to Use Tags
Team Structures: Since fynk already allows filtering by teams, there’s usually no need to replicate that with tags.
Unique Attributes: Avoid tagging attributes that are unlikely to repeat - like contract numbers or unique IDs. For those, use metadata, which is a far more scalable and sustainable solution.
Hint💡: Too many tags can make the tag selection confusing. Make sure to only add tags that make sense and are used frequently.
Metadata
Metadata are the most effective way to store, display, and manage a large variety of document attributes in fynk. Each account comes with a predefined set of around 90 metadata fields, categorized into three groups: System, Reference, and Account metadata.
System Metadata
These are automatically extracted where possible and cannot be edited or configured. No setup is required for system metadata—they’re managed entirely by fynk.
Reference Metadata
Reference metadata are fully customizable. You can:
Edit their properties
Define which document or contract types they should be extracted from
Deactivate any fields that aren’t relevant to your workflows
This allows you to keep your account well-structured by showing only the metadata that matter to you.
Tip: Take some time to review the reference metadata and check:
Should certain fields be extracted from additional document types?
Are there any metadata you don’t use and can deactivate to reduce clutter?
Account Metadata
With account metadata, you can create your own custom metadata fields to tailor fynk to your specific needs. For example, you might add fields for:
INCO terms
Specific due dates
Project or contract numbers
Any other data points relevant to your workflows
This flexibility allows you to fully leverage fynk’s AI capabilities by ensuring that all important information is structured and searchable. Want to learn more about how metadata are used, created, and managed in fynk? Check out this article for a detailed guide.
Contract types
Contract types determine which metadata fields will be extracted from a document during analysis. When a document is processed, fynk first identifies the document and contract type. Based on the recognized contract type, a predefined set of metadata is automatically extracted.
Key Points:
There are currently 14 contract types available in fynk.
Each contract type can be individually activated or deactivated, depending on your needs.
It only makes sense to deactivate a contract type if you're certain you won't use it—contract types are intentionally broad and general to cover a wide range of use cases.
Custom contract types cannot be added at this time.
If the existing types don’t fully meet your needs, consider using tags to further differentiate your documents.