Reference
Pūnaha glossary
Find simple meanings for the main words used in Pūnaha and its guides.
Use the same words across Pūnaha
This glossary gives each important word one preferred meaning. Follow the links when you need a fuller explanation or a task guide.
| Term | Meaning | Learn more |
|---|---|---|
| Tenant | A named area that holds people, access, settings, and work for one organisation or part of an organisation. | Tenants, people, and access |
| Person | A signed in identity that can belong to a tenant and receive access. | Tenants, people, and access |
| Group | A set of people that can receive access together. Pūnaha can manage a local group or read an external group from an identity provider. | Tenants, people, and access |
| Membership role | A tenant level starting set of access for a member. Direct and group access can add to it. A Deny can remove an allowed action. | Tenants, people, and access |
| Permission | An exact decision about who may perform an action on an item. Actions such as View, Search, Run, Work, and Delete are separate. | How access works |
| Workflow | A saved set of connected steps that receives information, performs work, and returns a result. | Workflows, versions, and runs |
| Workflow draft | The editable copy of a workflow. Changing a draft does not change an older published version. | Workflows, versions, and runs |
| Workflow version | A numbered published copy of a workflow that no longer changes. | Workflows, versions, and runs |
| Workflow run | One use of a workflow version, including its state, events, approvals, and result. | Workflows, versions, and runs |
| Case type | A definition of the stages, work, information, requirements, and files used by one kind of case. | Cases and case types |
| Case | One item of work created from a published case type version. | Cases and case types |
| Connection | Saved settings that let an approved workflow or service reach email, an API, or a database without placing its secret in the workflow. | Connections |
| Model | An AI model that Pūnaha can use for response generation, embeddings, or another enabled task. | Models and knowledge |
| Embedding | A numeric representation of text that helps Pūnaha find passages with a similar meaning. | Models and knowledge |
| Knowledge database | A searchable collection of processed documents and their stored passages. Access and API pages may call it a vector database. | Models and knowledge |
| Vector database | The technical name used for the searchable knowledge resource and its stored embeddings. | Models and knowledge |
| Document | A file added to a knowledge database and processed into searchable passages. | Create and search knowledge |
| Operational log | A time ordered record used to understand service and request problems. | Logs and audit records |
| Audit record | A record of an important security, access, or administration event. | Logs and audit records |
If a word is unclear
Search for the word and open the concept page before following a complex task. The task pages use these preferred meanings.
RC1 installation terms
| Term | Meaning |
|---|---|
| Installation | An independent registered Product identity and its approved nodes. |
| Primary | The first server used to establish an installation. |
| Configuration authority | The current approved node responsible for shared configuration and registration. |
| Registration allowance | 720 powered on hours after setup or an expired registered term. It is not a trial or a calendar grace period. |
| Solution package | A protected solution imported, checked, approved, and activated for its recipient. |
Was this page helpful?
Your answer helps us improve the documentation.
Do not include personal information, customer information, passwords, or keys.