These docs are for version 1.x of Rasa Open Source.

# User Guide

- [Installation](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/installation/)
- [Tutorial: Rasa Basics](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/rasa-tutorial/)
- [Tutorial: Building Assistants](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/building-assistants/)
- [Command Line Interface](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/command-line-interface/)
- [Architecture](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/architecture/)
- [Messaging and Voice Channels](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/messaging-and-voice-channels/)
- [Testing Your Assistant](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/testing-your-assistant/)
- [Setting up CI/CD](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/setting-up-ci-cd/)
- [Validate Data](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/validate-files/)
- [Configuring the HTTP API](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/configuring-http-api/)
- [Deploying Your Rasa Assistant](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/how-to-deploy/)
- [Cloud Storage](https://legacy-docs-v1.rasa.com/1.10.1/user-guide/cloud-storage/)

# Domains

The `Domain` defines the universe in which your assistant operates. It specifies the `intents`, `entities`, `slots`, and `actions` your bot should know about. Optionally, it can also include `responses` for the things your bot can say.

- [An example of a Domain](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#an-example-of-a-domain)
- [Custom Actions and Slots](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#custom-actions-and-slots)
- [Responses](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#responses)
- [Images and Buttons](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#images-and-buttons)
- [Custom Output Payloads](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#custom-output-payloads)
- [Channel-Specific Responses](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#channel-specific-responses)
- [Variables](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#variables)
- [Variations](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#variations)
- [Ignoring entities for certain intents](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#ignoring-entities-for-certain-intents)
- [Session configuration](https://legacy-docs-v1.rasa.com/1.10.1/core/domains/#session-configuration)

## An example of a Domain

As an example, the domain created by `rasa init` has the following yaml definition:

```yaml
intents:
  - greet
  - goodbye
  - affirm
  - deny
  - mood_great
  - mood_unhappy
  - bot_challenge

responses:
  utter_greet:
  - text: "Hey! How are you?"

utter_cheer_up:
  - text: "Here is something to cheer you up:"
    image: "https://i.imgur.com/nGF1K8f.jpg"

utter_did_that_help:
  - text: "Did that help you?"

utter_happy:
  - text: "Great, carry on!"

utter_goodbye:
  - text: "Bye"

utter_iamabot:
  - text: "I am a bot, powered by Rasa."

session_config:
  session_expiration_time: 60
  carry_over_slots_to_new_session: true
```

**What does this mean?**

Your NLU model will define the `intents` and `entities` that you need to include in the domain. The `entities` section lists all entities extracted by any [entity extractor](https://legacy-docs-v1.rasa.com/1.10.1/nlu/entity-extraction/#entity-extraction) in your NLU pipeline.

For example:

```yaml
entities:
   - PERSON          # entity extracted by SpacyEntityExtractor
   - time            # entity extracted by DucklingHTTPExtractor
   - membership_type # custom entity extracted by CRFEntityExtractor
   - priority        # custom entity extracted by CRFEntityExtractor
```

[Slots](https://legacy-docs-v1.rasa.com/1.10.1/core/slots/#slots) hold information you want to keep track of during a conversation. A categorical slot called `risk_level` would be defined like this:

```yaml
slots:
   risk_level:
      type: categorical
      values:
      - low
      - medium
      - high
```

[Actions](https://legacy-docs-v1.rasa.com/1.10.1/core/actions/#actions) are the things your bot can actually do. For example, an action could:

- respond to a user,
- make an external API call,
- query a database, or
- just about anything!