Core Concepts
This page defines the concepts that appear across xTrakt user, API, architecture, and security documentation.
When To Use This
Use this page when onboarding a new team member, creating a template, making an API request, or reading architecture docs.
Before You Start
- Review the Product Overview.
- Know whether you are working as an end user, administrator, developer, or operator.
Concepts
| Concept | Meaning |
|---|---|
| Tenant | The isolated customer or subscription context for users, data, templates, and audit records |
| Subscription | The commercial and entitlement context that controls access to product capabilities |
| User | A person authenticated through the xTrakt identity and platform flow |
| API key | A credential used by external systems to call xTrakt APIs |
| Platform token | A token obtained after SSO authentication that grants access to platform APIs |
| Template | A reusable definition of expected fields and extraction behavior for a document type |
| Classifier | Product behavior that identifies the type of document submitted |
| Extraction | The process that turns document content into structured fields |
| Review | A user workflow for validating extraction output before downstream use |
| Audit trail | Metadata that records who created or changed data and when it changed |
Workflow
- A user signs in and enters a tenant context.
- An administrator or operator creates templates for document types.
- A user or API client submits a document.
- xTrakt classifies the document when needed.
- xTrakt extracts structured fields using a template.
- A reviewer validates the result.
- The approved data is used by a workflow, API client, or downstream system.