What is the difference between folders, tags, and attributes in document management?
Folders provide a browsing hierarchy, tags provide lightweight labels, and attributes provide structured document metadata. In FormKiQ, attributes can have defined types and participate in schemas, search, and automation. Dates are commonly represented as formatted strings rather than a separate date type. Choose organization and authorization rules explicitly; a folder name or label alone grants no access.
Use each structure for a purpose
A folder path helps people browse a collection. A label such as needs-review can support lightweight organization. A defined attribute such as numeric invoiceTotal supports validation and queries that depend on the value's type.
FormKiQ separates reusable attribute definitions from the values stored on a document. Standard value types include STRING, NUMBER, BOOLEAN, and JSON, with additional special-purpose types. Define the expected date format when using strings for dates and apply consistent timezone conventions.
Model an invoice
Use a path such as invoices/2026/example.pdf for browsing, a lightweight label for intake triage, and typed fields for invoice number, amount, vendor identifier, and processing status. Apply a schema where required fields or allowed values matter.
Keep governance and access behavior deliberate. A field named legalHold is not a native legal hold, and a confidential label does not enforce an access policy. Use the actual governance operations and supported folder, site, or OPA controls.
Edition and configuration
Core supports folders, tags, attributes, and schemas. Commercial governance, OPA, and selected search capabilities have their own deployment and permission requirements.