> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adopt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Every Adopt term in one place, with the end-user word next to the platform word.

Adopt has two vocabularies — finance words on the end-user surface, platform words on the builder surface — for the same underlying objects. This table maps them.

| Term                       | Also called                    | What it means                                                                                                      |
| -------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| **Customer**               | —                              | Your firm or organization using Adopt.                                                                             |
| **Workstream**             | Client (end-user)              | One client of your firm; the isolation boundary for their data.                                                    |
| **Engagement**             | Process                        | One process run for a client (R\&D Tax Credit, Transfer Pricing, Close). Lives inside a workstream.                |
| **Run**                    | —                              | A single execution of an engagement's work.                                                                        |
| **Output**                 | Prepared work                  | What a run produced; waits in the review queue until approved.                                                     |
| **Doc Store**              | Files, Documents (end-user)    | Where a client's unstructured files live (File Explorer).                                                          |
| **Data Store**             | Tables                         | Structured tables an agent can query.                                                                              |
| **Connector**              | —                              | A link to a source system (Google Drive, SharePoint, File Upload, S3).                                             |
| **File Sync**              | Sync                           | The process that copies files from a connected source into a Doc Store.                                            |
| **Agent**                  | Task, Template (end-user)      | The thing that prepares the work; carries instructions and skills.                                                 |
| **Space**                  | —                              | An isolated data bucket provisioned automatically when an agent is named.                                          |
| **Skill**                  | Capability                     | Something an agent can do: read documents, query the Data Store, generate a workpaper, web search, fill tax forms. |
| **Plugin**                 | —                              | An added integration / tool extending an agent beyond built-in skills.                                             |
| **HITL**                   | Human-in-the-loop, Review gate | The always-on checkpoint where output waits for human approval.                                                    |
| **Review queue**           | —                              | Where prepared work waits for a reviewer.                                                                          |
| **Scope**                  | —                              | How access is decided, along two axes: Workstream and Agent/Space.                                                 |
| **Workstream-based scope** | Row-level security (RLS)       | Data Store scope where each client sees only its own rows.                                                         |
| **Member**                 | User                           | A person with an Adopt account and some client access.                                                             |
| **BYOK**                   | Bring your own key             | Supplying your own model-provider credentials for model usage.                                                     |
| **Quick setup**            | —                              | The fast, template-driven 3-step setup path.                                                                       |
| **Advanced setup**         | Full builder                   | The explicit 9-step setup path exposing every primitive.                                                           |

## Next steps

1. [The object model](/core-concepts/the-object-model)
2. [Access scoping](/security-access/access-scoping)
3. [Connector reference](/reference/connector-reference)