UPDATED IN VERSION 6.1
Collections are K's framework for grouping, classifying, and governing data assets across your ecosystem. Unlike tags, most collections are governed structures with defined hierarchies, roles, and automation rules, making them the right tool when consistency and accountability matter. Knowledge Collections are the exception.
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
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.
|
Feature |
Role in this outcome |
|---|---|
|
K's built-in default platform collections (Domain, Category, Zone, Usage, PII) provide out-of-the-box structure manage your data ecosystem |
|
|
Create custom collections to organise governance concepts (e.g. Critical Data Element) or management concepts (e.g. Environment) that don't map to a default K collection type |
|
|
One of the critical K Collections giving governance managers a structured way to align data assets to business areas |
|
|
One of the critical K Collections allowing teams can confirm whether a data item is safe to use for a specific use case and flag ones to avoid. Linking Verified Use Case (or Do not use case) can also help uplift the data asset Trust Score |
|
|
Make large-scale updates to collection instances using Excel templates — without manual one-by-one changes |
Who this is for: Data Governance Managers, Data Managers, and K Administrators.
Surface, identify and act on sensitive data
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.
|
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 |
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
Business users can navigate and understand technical data assets using familiar terms, while governance teams maintain control over shared vocabulary through structured, searchable glossaries.
|
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.
Ungoverned Collections
Any user can capture and share context about a data asset (quick notes, caveats, or tips), or group related items together in a list, without needing governance permissions or a formal structure. These are the two exceptions to everything else on this page: Knowledge Collections and Lists are both open to all users, with no governance layer
|
Feature |
Role in this outcome |
|---|---|
|
Knowledge Collections group informal notes the same way a Glossary groups Terms, but open to all users with no permission gate or governance controls |
|
|
Group any list of data assets, users, and collections together, follow updates in your K Feed, and review data quality for the list via its Quality tab. |
Who this is for: All users.