Using K
K helps different types of data users in your Organisation to discover, organise, govern and understand your data anda analytical content. This page will help you understand the different user types and the use cases they can use K for.
Data Worker
A data worker is someone that works with data day to day. They might be a data analyst that wrangles data for insights; data engineers that build pipelines to move and transform data; data scientist that runs experiments to test features.
As a Data worker, you can leverage the majority of features in K to discover data, organise your own code, document and share knowledge, run impact assessments, and analyse your data product metrics.
Use case | Feature to use in K |
|---|---|
As a Data Engineer, I want to run an impact assessment over a Database Table that I am looking at changing so I can see the level of testing and change management I need to undertaken. | |
As a Data Analyst, I want to find some code I recently ran for a project that I now want to reuse. | |
As a Data Scientist, I want to find some web traffic data that I can use to run some models on. I want to find data that has been system generated and not transformed. |
Business User
A Business user is typically a consumer of data. They use data products like reports, applications and analyses.
As a Business user, you can use K to find reports that your team uses, understand the definition of a Customer, and receive notifications when a data change will impact the data products I use.
Use case | Feature to use in K |
|---|---|
As a Risk Analyst, I want to check the definition of delinquency that I found in this dataset. | Glossary |
As a new Marketing Analyst, I want to find the reports that my team uses so I can get up to speed. |
Data Owners
A Data Owner can be anyone that is accountable for the collection, handling, and use of a data product. This can be anyone from the Product manager of the application that generated the data, to the Business lead that owns the entire data domain.
As an Owner, you can use K to manage your data product, see who is using your data products, and run reports on unused access.
Use case | Feature to use in K |
|---|---|
As a Data Owner, I want to find all users that have access to my data that has not used their access in the last 90 days. |
Data Governance
A Data Governance user is responsible for guiding the Organisation in the proper controls around the collection, handling and use of data. Data Governance is typically part of the Data Function and have unique responsibilities in helping define and drive data lifecycle management, privacy, quality, stewardship, metadata/master/reference data management, security and classification.
As a Data Governance team member, you can use K to manage your data ecosystem’s metadata, classify data, review data usage and access, assign stewards, capture quality metrics, and enable lifecycle management.
Use case | Feature to use in K |
|---|---|
As a Data Governance Analyst, I want to classify all the PII data we collect and let users of this data know about the updated classification. | |
As a Data Governance Manager, I want to organise Finance data to a Finance domain and assign a purpose (verified use case) to this data. |
Data Manager
A Data Manager is responsible for managing the use, cost and access to the platforms, products and tools that make up the data ecosystem.
As a Data Manager, you can identify how much of the ecosystem is being used, by whom, and how often. You can run reports to identify data products that are at the end of their lifecycle, and take actions to maintain a clean and healthy ecosystem.
Use case | Feature to use in K |
|---|---|
As a Data Manager, I want to run a cost allocation report for the last month so I can ensure each team is paying for their use of the Snowflake platform | |
As a Data Manager, I want to identify all the tables that have been created by users that are unused so I can clean them up |
K Platform Administrators
An administrator has full access to the platform. They are the ones that can help with setting up K, onboarding new systems, sources and change global settings.