> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/key-concepts-and-terminology.md).
# Key Concepts and Terminology
### Overview
This glossary standardizes Transform terminology across an Account. Consistent terminology improves reporting, search, and governance.
### Key Concepts
#### Account, Organization, Project
* **Account**: top-level container for all work
* **Organization**: container for a client, department, or business unit
* **Project**: delivery container for a single transformation initiative
#### Blueprint, Process, System
* **Blueprint**: reusable structure applied to new Projects
* **Process**: business workflow, phase, or workstream tracked in a Blueprint
* **System**: application or platform that supports a Process
A System can be a business application, such as an ERP system or a CRM system.
#### Segment Types and Segments
* **Segment Type**: a business dimension, such as Region or Department
* **Segment**: a value inside a Segment Type
Segments and Segment Types are managed at the Organization level.
Start here: [Segmentation](/blueprints/segmentation.md)
#### Work items
* **Requirement**: statement of scope that must be delivered and validated
* **Task**: executable work that implements scope
* **Test case**: validation steps linked to a Requirement
* **Artifact**: supporting file or reference linked to work items
### How It’s Used
Use this glossary when defining Blueprints and reporting fields. Use it when standardizing naming across multiple Projects.
### Benefits
* Fewer reporting inconsistencies across Projects
* Faster onboarding through shared vocabulary
* Cleaner search results and less duplicated work
### Setup Steps
1. Adopt this page as the default glossary for an Account.
2. Standardize page titles, field labels, and view names to match this glossary.
3. Link related pages in onboarding documentation to reduce repeated explanations.
### Best Practices
* Avoid abbreviations for Organization and Project names.
* Prefer dropdown fields over free text for reporting fields.
* Use the term **Save View** for a stored view configuration.
* Treat Segments as Organization-scoped structure, not tags.
### Summary
This glossary defines the core Transform terms used across Account, Organization, and Project scopes.
Related:
* [Start Here](/getting-started/start-here.md)
* [What Is Transform](/getting-started/what-is-transform.md)
* [Understanding the Interface](/getting-started/understanding-the-interface.md)
* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.transform.ai/getting-started/key-concepts-and-terminology.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.