Collections are K's framework for grouping, classifying, and governing data assets across your ecosystem. Unlike tags, collections are governed structures with defined hierarchies, roles, and automation rules — making them the right tool when consistency and accountability matter.
Collections are used across data discovery, knowledge management, and data governance — from automatically flagging PII to linking business glossary terms to technical assets.
Organise your data estate with a consistent structure
The outcome: Data teams can group and classify data assets using a defined framework that all users understand — with automation rules to keep linkages current and governance controls that manage who can create or modify collections.
How K delivers this:
|
Feature |
Role in this outcome |
|---|---|
|
K's built-in platform collections (Zone, Usage, PII) provide out-of-the-box structure that's automatically maintained by the platform — no manual effort required |
|
|
Domains and sub-domains are managed as collections, giving governance managers a structured way to align data assets to business areas |
|
|
Make large-scale updates to collection instances using Excel templates — without manual one-by-one changes |
|
|
Visualise what's been linked to a collection and identify lineage-based coverage gaps — then link missing items directly from the map |
Who this is for: Data Governance Managers, Data Managers, and K Administrators.
Surface, identify and act on sensitive data
The outcome: PII and sensitive data is automatically detected and flagged through the platform's scanning capabilities — giving governance teams clear visibility of exposure risk and enabling fast, targeted remediation.
How K delivers this:
|
Feature |
Role in this outcome |
|---|---|
|
K's automated scanner detects PII in tables and columns and links them to dedicated PII collections — making sensitive data immediately searchable, filterable, and governable |
|
|
Review what's been linked to PII collections and quickly identify related assets in your lineage that may also require tagging |
Who this is for: Data Governance Managers and K Administrators.
🔒 See Data Governance for K's full governance toolset — including PII detection alongside change management, impact assessment, and DQ integration.
Connect business language to technical data
The outcome: Business users can navigate and understand technical data assets using familiar terms, while governance teams maintain control over shared vocabulary through structured, searchable glossaries.
How K delivers this:
|
Feature |
Role in this outcome |
|---|---|
|
Glossaries are a specialised collection type — structured hierarchically, with searchable terms linked directly to data assets and surfaced on the Data Profile page |
|
|
Understand when to use a governed collection versus a flexible tag — and which approach suits different users and use cases |
Who this is for: Data Governance Managers, business analysts, and data product managers.
💡 See for the full picture of how K builds context around data assets, including AI-generated descriptions, crowdsourced feedback, and data profiles.