What KRISID is
Assets, types, domains and the links between them, in one page.
Documentation
The KRISID Documentation
The same help centre that ships inside the product, published in full and free to read. 48 pages covering every screen, the question grammar, the metamodel, and the whole HTTP API — endpoint by endpoint, with the permission each one needs and the reasons it refuses.
No registration. Written for the people who use it, not for a brochure.
KRISID is where your organisation keeps track of its data: what each thing means, where it physically lives, who answers for it and where its data comes from. This help centre explains how to use it, whatever you came to do.
Help about the screen you are on
The Help button at the top right of every screen opens the help page about that screen. On the Ask page it opens the page about Ask; on an asset it opens the page about reading an asset. From any help page, Help home brings you back here.
Tip: Press
/from anywhere in KRISID to jump to the Ask box and type a question.
New to the words?
KRISID uses a handful of words in its own way: asset, domain, harvested, roll-up. What KRISID is explains them in one page, and the Glossary defines each one.
If something looks wrong, try Troubleshooting and FAQ.
Get started
Your first ten minutes
Sign in, ask a question, open an answer, follow its lineage.
Signing in and creating an account
Sign in, sign up with your email address, and what to do if you are locked out.
Finding your way around
The top bar, the sidebar, Ask, and the Help button you just pressed.
Find and understand
Ask: search and questions
One box for searching and for asking questions in plain words.
Browsing by domain and by type
Lists of every kind of thing, and everything a domain answers for.
Reading an asset
Definition, attributes, who is responsible, links and history.
Lineage and connections
Where data comes from and where it goes, and how to read the picture.
Lists, conditions and saved searches
Narrow with conditions, save what you built, share it.
Metrics and asking for a number
How KRISID composes a governed query from the semantic layer — and never runs it.
Curate
Editing an asset
Change a description, an attribute or a link, and what happens when you do.
Owners, stewards and responsibilities
Who answers for what, and how responsibility is inherited.
Requests and approvals
Changes that need somebody's agreement, and how to decide them.
Designing a workflow
The canvas: states, steps, scope, who is asked, and what happens when time runs out.
Loading from Excel
Add or change many assets at once, with a preview before anything is written.
The business layer
Domains, subject areas, entities, terms, rules, products and contracts — and binding them to real data.
Editing the semantic model
Metrics, dimensions and segments as YAML, and which side wins.
Classifications and sensitive data
Marks like Contains PII, where they are recorded and where they show.
Administer
People, roles and access
Add people, grant roles, look through somebody else's eyes.
Sign-up and the mail server
Let people create their own accounts, and send invitations by email.
Appearance and Ask examples
Your name and logo, the top bar, and the questions under the Ask box.
Connections and harvesting
Connect Snowflake, Databricks, Power BI, Tableau, Fabric or OpenLineage, and keep them in sync.
Connections a workflow calls
Where a workflow action sends, and the token it sends with.
Pushing tags back to Snowflake
Write classifications from KRISID onto the warehouse itself — previewed first.
The metamodel
The types, attributes and relations everything else is made of.
Lenses
One view over several asset types, and who may see it.
The activity log
What changed, who changed it, and what the application itself did.
Usage analytics
Who uses what, for how long, what they search for — when it is switched on.
Upgrading and licensing
Install a new release safely, and what the licence checks.
Reference
What Ask understands
Every kind of question the box can read, with examples.
Glossary
KRISID's own words, defined once.
Keyboard shortcuts
The keys that save time.
Troubleshooting and FAQ
Common questions, and what to do when something looks wrong.
The HTTP API
Every endpoint the browser calls, grouped by the screen that calls it — with its parameters, what it answers and the permission it needs.
Signing in and the frame
The API calls behind signing in and the frame.
The invite and sign-up screens
The API calls behind the invite and sign-up screens.
Ask and search
The API calls behind ask and search.
Browsing: overview, roll-up, estate, layers, type lists
The API calls behind browsing: overview, roll-up, estate, layers, type lists.
One asset
The API calls behind one asset.
Lineage and the explorer
The API calls behind lineage and the explorer.
The metamodel
The API calls behind the metamodel.
People, teams, roles and access
The API calls behind people, teams, roles and access.
Workflows, requests and change sets
The API calls behind workflows, requests and change sets.
Sources, connections and harvesting
The API calls behind sources, connections and harvesting.
The semantic layer
The API calls behind the semantic layer.
Bulk load and exports
The API calls behind bulk load and exports.
Administration
The API calls behind administration.
The help centre
The API calls behind the help centre.
Reading This to Decide Whether to Buy?
The documentation is deliberately complete, including the parts about what the product refuses to do. If something you need is missing from it, that is worth a conversation.