Core concepts

TKP uses the following names in both its web interface and its integration APIs. You do not need to learn all of them before uploading a file; use this page when you encounter an unfamiliar term.

Workspaces and libraries

A tenant is a workspace for a team or project. It separates that workspace's content, members and settings from other workspaces. A user can belong to several tenants and choose which one to work in. See tenant roles.

A library groups related documents and media within a tenant. It has its own folder tree and access permissions. For example, a project workspace might have separate libraries for research papers and meeting recordings.

Files and their extracted content

A resource is an uploaded file, such as a report or recording. Ingestion is the background processing that extracts its contents and prepares them for search. Uploading a file and finishing ingestion are separate steps.

An asset is a piece of content extracted from a resource, such as text, an image or a transcript segment. Some resources also have pages, which let you inspect a rendered document page. TKP divides searchable content into smaller chunks so it can find relevant passages within a large file.

A source reference identifies where content came from, for example a page or a time range in a recording. A citation connects an answer to that source, so the reader can check it. See libraries, resources and assets for how to inspect them in the panel.

Notes and feedback

A note records knowledge about the library, rather than being an uploaded file. A hint asks TKP to review a correction or another proposed change. The notes and hints guide explains their roles.

Access from another application

A credential is something an application uses to prove that it may connect. TKP supports access tokens and OAuth connections. Each credential is tied to one tenant and has its own permissions. Permissions and abilities explain how those limits combine with your own library access.