> 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/design-considerations-and-frameworks/frameworks/feedback-portal-framework/feedback-portal-configuration.md).

# Feedback Portal Configuration

## Description

The following information details how to create a feedback portal application and set the configuration options.

## Create Feedback Project

To create a feedback portal application, click on your Designer project menu and create a new project.

1. With the name of your new project highlighted, click the ***Modify*** button.
2. In the *General* section, go to *Type* and select ***based on framework*** from the dropdown menu. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-9cf1c12a79f835a9f4a4d6759603b38705359a59%2F2f8ce10f-e178-4f09-96b8-6d053ff42179.png?alt=media)
3. Select ***FeedbackPortal*** from the *Framework* dropdown menu.
4. Click ***Save*** to save your updates.

## Feedback Categories

The system provides default feedback categories:

* Bug/Defect
* Content Correction
* General Inquiry
* Improvement/Suggestion.

However, you can configure your project to use other categories instead.

1. Click the name of your project and click the ***Modify*** button.
2. Go to the *Framework* tab.
3. In the *Categories* section, enter the number ***1*** under *Id* and enter the name of the category you want to add in the *Category* field.
4. Click the ***add*** button.
5. To enter the next category, enter the number ***2*** under *Id* and enter the second category in the *Category* field.
6. Click the ***add*** button.
7. Continue this until you have added each of the categories you want to use.
8. Click ***save*** to save your changes.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-9901c200a58c1da8e5b6e7d19b16aad3799cddab%2Fa3fcef05-463f-40e9-b9bf-3daae6daa3da.png?alt=media)

## Feedback Priority

As with categories, the system includes default feedback priority levels:

* Blocker
* Severe
* High
* Medium
* Low

However, you can configure your project to use other priority levels instead. To do this, click the name of your project and click the Modify button.

1. Go to the *Framework* tab.
2. In the *Priority* section, enter the number ***1*** under *Id*. Enter the name of the priority in the *Priority* field, and enter a description of that priority level in the *Description* field.
3. Click the ***add*** button.
4. To enter the next priority, enter the number ***2*** under *Id*. Enter the name of the priority in the *Priority* field, and enter a description of that priority level in the *Description* field.
5. Click the ***add*** button.
6. Continue this until you have added each of the priorities you want to use.
7. Click ***save*** to save your changes.

## Feedback Status

The system defines certain default feedback statuses:

* Opened
* Assigned
* Developing
* In Testing
* Postponed
* Staging
* Completed
* Released
* Cancelled

As with Category and Priority you can configure your project to use other status levels instead.

1. Click the name of your project and click the ***Modify*** button.
2. Go to the *Framework* tab.
3. In the *Status* section, enter the number ***1*** under *Id*. Enter the name of the status in the *Status* field.
4. Click the ***add*** button.
5. To enter the next status, enter the number ***2*** under *Id*. Enter the name of the status in the *Status* field.
6. Click the ***add*** button.
7. Continue this until you have added each of the statuses you want to use.
8. Click ***save*** to save your changes.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-84b04dd7dc48cf93d8763679511193190ebe9974%2Fca5f7b66-bd89-4640-9b11-1ff3682ccab9.png?alt=media)

## Add Feedback

If you want to allow your users to add new feedback using the portal, go your project's *Framework* tab and select ***Yes*** from the dropdown menu next to *Add new feedback*. Select ***No*** if you do not want your users to have this option.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6f8f11822603a8b0e932025fd077821a331d89c5%2F147598df-389a-4c4c-84b6-5f13ceba1c9c.png?alt=media)

## Allow Open Session

The system allows you to configure your feedback portal so users can open a session from the portal using the session information saved as part of the feedback. To configure your feedback portal to do this, go to the *Framework* tab and select ***Yes*** from the dropdown menu next to *Allow open session*.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-cde6de59eb74d018c0826257b81f2d4fe8b57f94%2F16b0d16f-3e7f-487a-bde7-62008472730f.png?alt=media)

If you set the value of this option to ***Yes*** the system displays to your portal users an *open* button in the details popup window.


---

# 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/design-considerations-and-frameworks/frameworks/feedback-portal-framework/feedback-portal-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.