> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/getting-started/core-concepts.md).

# Words you will see

The vocabulary, in the order you are likely to meet it. Keep this page open for your first week.

## The basics

**Organisation**: your company or institution within the platform. Everything belongs to one: users, assistants, documents, settings. Some organisations manage others beneath them, called child organisations.

**Assistant**: a chat-based helper with a specific job, built by your administrators and given your documents and your house style.

**Element**: one tool in the AI Toolbox. A form you fill in that produces a finished result.

**Prompt**: the question or instruction you type.

**Model**: the underlying AI that generates the answers. Administrators choose which model each assistant uses.

**Token**: how model usage is measured, roughly a word-part. You will only meet this word in cost reports.

## Knowledge

**Knowledge base**: your organisation's documents, organised so assistants can answer from them.

**Collection**: a named container of documents inside the knowledge base.

**Label**: a coloured tag on a document, used for filtering and for controlling what a given assistant can find.

**Search tool**: what makes a collection searchable for an assistant. Documents are not findable until a search tool covers them and it is switched on.

**Sources**: the earlier version of the knowledge feature. Some organisations still use it.

**Sources used**: the block under an answer showing which documents it came from.

## Doing things

**Tool** is a capability an assistant can use to act: look something up, run a task, search your documents.

**Connector**: a connection to an external server that offers **actions** an assistant may perform.

**Secret key**: a stored credential that tools use, so no one has to type a password into a configuration screen.

**Service account**: an account for software rather than a person, used when another system needs to talk to the platform.

## Working

**Project**: a named container keeping related chats, files and background information together, so you do not re-explain the situation every time.

**Session** or **chat**: one conversation with an assistant.

**Tone of voice**: a saved writing style that can be applied to assistants and elements.

**Theme** is the visual style of a chat window: colours, logo, corners.

## The Inbox

**Communication channel**: a mailbox connected to the platform.

**Conversation**: all the messages exchanged with one person on one thread.

**Draft**: the reply the assistant wrote, waiting for a person to review and send.

**Mail template**: the branded frame wrapped around every outgoing reply.

**Direct chat**: the separate queue where a live web-chat visitor asks to speak to a person.

## Access

**User**: a person with an account.

**User group**: a named set of people. Groups are how rights reach people.

**Role**: a set of rights, attached to a group.

**Rights** or **permissions**: what a role allows in each area.

**Administrator**: someone who configures the platform for your organisation.

**Account manager**: your organisation's contact for plans, contracts and anything the platform does not currently do.

## Assurance

**Quality control**: automated checks that an assistant keeps answering correctly.

**Scenario**: one situation being tested, made of steps.

**Run**: one execution of a quality control, producing a score.

## Two that trip people up

**A collection is not searchable by itself.** Uploading documents is storage. It takes a search tool to make them findable.

**Rights come from groups, never from a person's own record.** To give someone access, add them to a group. There is nowhere to grant a right directly.