# OrgKeep glossary

> The terms we use, in a sentence or two each.

Source: https://orgkeep.com/resources/glossary

- **Member:** Anyone in the organization, human or AI. Every module records that a member did something, whichever kind it is.
- **AI employee:** A member backed by an AI engine instead of a person, with its own role, manager, permissions, budget and responsible human. [More about AI employees](/ai-employees).
- **Responsible human:** The person accountable for an AI employee and what it does.
- **Autonomy:** How much an AI employee may do on its own, set per action: suggest only, act with approval, or act alone.
- **Reply policy:** The admin setting that decides whom an AI employee may email: internal people only, or external people too, and what it does on a thread with both.
- **Human-only step:** A workflow step that only a person can complete, such as a payment, a contract or a production deploy.
- **Use access:** A vault access level that lets a member use a credential without seeing its value.
- **Credential broker:** The server component that inserts a secret into an outgoing request, so the AI never sees it. [How it works](/security).
- **Vault:** A named, encrypted store of credentials that belongs to the organization, a department or a project.
- **Engine:** The loop that runs an AI employee: OrgKeep's built-in engine, or a coding agent such as OpenCode, Claude Code or Codex.
- **Agent Host:** A service installed on any machine that runs AI employees there, for example a coding agent inside a project folder.
- **Model gateway:** The single route through which AI employees reach any AI provider or local model.
- **Skill:** Reusable know-how in the open Agent Skills format, a folder with a `SKILL.md` file, taken from the organization's reviewed library.
- **Specialist:** An AI employee whose home project is a product, brought into customer projects for its expertise.
- **Container:** Something that holds folders and vaults: the organization, a department or a project.
- **Project link:** A "uses" relationship from a customer project to a product project, which shares the product's shared folders one way.
- **Capability:** A kind of outside system that modules talk to, such as Chat or Accounting.
- **Connector:** The implementation of a capability for one product, such as Slack for Chat or QuickBooks for Accounting.
- **Task tool:** The outside system that holds tasks: Tecfy Tasks first, with others to follow. OrgKeep reads tasks there live and changes them through the tool's API, and never copies them.