Resources
Glossary Copy page # Glossary
This page lists the terms used in Hane's documentation, console, and API. Each concept is always written with the same term, so look it up here when something is unclear.
## Organizations and users
| Term | Meaning |
| --- | --- |
| organization | The unit that contracts for Hane. Data and permissions are separated here |
| project | A unit within an organization that separates definitions and data |
| environment | Development, staging, and production of the same project (`dev`, `stage`, `prod`) |
| user | A person who signs in |
| member | A user who belongs to an organization, with roles and groups |
| principal | The person or service account who asked for an operation |
| actor | What actually made the call (such as your app's service account) |
| service account | A caller that is not a person |
| API key | A service account's credential. The value is shown only once, when issued |
| access token | A short-lived credential that Hane issues through token exchange |
| role binding | A manifest setting that grants a role to people, groups, or service accounts |
| policy epoch | A number that goes up whenever roles, groups, or keys change. Tokens from older epochs are rejected |
| suspension | Stopping every operation in an organization (the emergency stop). Only the owner can lift it |
| revoke | Making an API key unusable |
| operator engagement | The basis on which the provider's operators work in a customer's project. The customer's administrator sets its scope and period |
## Definitions and releases
| Term | Meaning |
| --- | --- |
| manifest | A definition written as YAML and kept in Git |
| definition | Something activated as a set (types, rules, workflows, agents, and so on) |
| draft | A definition that has been applied but is not yet active |
| apply | Turning manifests into drafts |
| revision | A number that increases every time a definition is applied |
| ReleaseBundle | A set of definition revisions. Its contents never change |
| active release | The ReleaseBundle running now |
| activate | Making a ReleaseBundle the active release |
| promote | Sending a ReleaseBundle from dev to stage and prod |
| rollback | Making an earlier ReleaseBundle active again |
## Data and documents
| Term | Meaning |
| --- | --- |
| record | One item of business data that follows a type |
| type | A kind of record (vehicle, contract, and so on) |
| field | A named value that a type has |
| relation | A link between two records |
| value state | How far a value has been confirmed: confirmed, estimated, pending inquiry, or unknown |
| source | Where a value came from (import, person, computation, document, external) |
| import | Creating or updating records from CSV and similar sources |
| document | An original file and its versions |
| extracted fact | A field value pulled from a document that a person has not yet confirmed. It carries a page and a quote |
| document type | The kind used to sort mixed incoming documents into contracts, invoices, and so on |
| derivative | Something made from a document (rendition, text, search index, summary, and so on). The unit of disposal tracking |
| hold | A setting that keeps a document or contact endpoint from being deleted |
| disposal | The record, per derivative, of what was deleted or kept after a deletion was accepted |
| business knowledge | Knowledge held in definitions with sources and confidence (Axioms and aspects) |
| aspect | A deterministic judgment rule applied to records |
| finding | The result detected by an aspect's rule |
| eval set | Redacted copies of documents that people have checked, used to compare extraction schemas (separate from agent EvalSuites) |
## Workflows and approvals
| Term | Meaning |
| --- | --- |
| workflow | The definition of how a case progresses |
| case | One piece of work moved forward by a workflow |
| step | One stage of a workflow |
| task | One decision or piece of work for a person |
| assignee | The person or group who can decide a task |
| assignment | The rule that decides the assignee |
| approval | A decision a decider makes, tied to a digest |
| decider | Who may decide an approval: a person, a review agent, or a pre-approved policy |
| decider policy | A definition that sets deciders and approval stages per operation and condition |
| approval subject | What an approval decides. The server shows a fixed snapshot |
| schedule | A definition that runs a workflow or agent at set times |
| event subscription | A registered destination and event types for delivering events to your systems |
| webhook delivery | Delivering one event to one subscription |
## Agents
| Term | Meaning |
| --- | --- |
| agent | A definition with a purpose, tools, limits, and input and output schemas |
| AgentRun | The record of one run of an agent |
| driver | What runs an agent (a script, a model, or a CLI) |
| Tool Gateway | The only way agents call tools. It checks permission and state on every call |
| Model Gateway | The way agents and Hane Cowork call models. It checks allowed models and budgets, and records each call |
| ActionRequest | A proposed outbound action. Recipient and content are fixed, and it runs once after approval |
| reception | The entry point that picks the agent and input from a person's free text |
| conversation | An exchange in Hane where people ask the chat agent in natural language |
| chat agent | The agent that receives every chat message and calls business agents when needed |
| review agent | An agent started for each proposal that approves, rejects, or escalates to a person |
| EvalSuite | An agent evaluation: pairs of input and expected result, run in shadow mode and compared |
| budget reservation | Setting aside the maximum tokens a run may use from the daily budget when the run is created |
## Integrations and contact
| Term | Meaning |
| --- | --- |
| route | The path from the public API entry point to one of your registered APIs |
| published API | One of your APIs published on a route |
| consumer | A caller of a published API |
| tool exposure | A declaration that turns one published API operation into an agent tool |
| rotate a secret | Replacing a connection secret with a new value and revoking the old one |
| communication | The service that sends notifications and outbound contact such as email |
| notification | A message sent from a workflow |
| contact endpoint | The number or address of someone to contact, with allowed purposes and stop records |
| stop request | Someone asking not to be contacted again |
| sender identity | The definition of whose name email, SMS, and calls go out under |
| AI call | A call made after approval, in which a conversation agent talks only within the call brief |
| call brief | What may be said in an AI call. It is fixed in the approval subject |
| handoff | Asking a person to take over when a portal flow gets stuck |
| browser runner | A program in your network or on an employee's machine that runs portal flows |
## Next steps
<CardGrid>
<LinkCard title="Key concepts" href="/en/platform/concepts/" />
<LinkCard title="FAQ" href="/en/resources/faq/" />
</CardGrid>
Terms used in Hane's documentation, console, and API, with short definitions.