> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/speech-recognition-voice-input/speech-project-configuration.md).

# Speech Project Configuration

## General Speech Configuration

When you create a project based on the Assessment Framework there are several available speech configuration items in the Framework tab for project configuration. The fields include the following speech recognition options:

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-eefc06a3a50df329110eb9caf33a60f13decdd58%2F5b9f2781-b684-4832-982c-153aa4932534.png?alt=media)

### Enable S\*\*\*\*peech Recognition

In this field, select *Yes* to enable speech recognition and select *No* to disable speech recognition.

### Speech Recognition Language

This field defines the language specification for all speech elements. The currently available language options are:

* English (US)
* English (UK)
* Dutch
* German
* French

This also determines how to trigger tab pages and buttons in the Assessment Framework. Different languages require different statements to switch tabs or select a button. For example, to switch a tab in English you have to say "Page XXX" and in Dutch you would say "Pagina XXX". With a button selector you would say "Go to YYY" in English or "Ga naar YYY" in Dutch.

### Speech Reporting Group

This field is free text and it sets which reporting group to use. A reporting group is a speech-recognition-specific configuration and is a combination of a language set and specific dictionary. It is configured in the G2Speech / Recognosco speech engine. Selecting the right name will help the software to choose the correct reporting group. If the system cannot find the reporting group identified in this field it will select the first available reporting group.

**Note:** *The configured Speech recognition language must match the language for the reporting group!*

### Speech Navigation Sound

The system allows the user to select a sound to play as audible feedback when the system navigates to another question, either because the end user answered a question or because the end user navigated using the FWD/REW buttons. The user selects the audio file to play from the files available in the resources/media folder in the the project tree.

### Speech Recognized Sound

When the end user gives an answer and the system recognizes the answer the system plays a sound. This is intended for the directly recognized answers and not for free text, number, or date inputs.

The user selects the audio file to play from the files available in the resources/media folder in the the project tree.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/speech-recognition-voice-input/speech-project-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.