> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/configuring-screens/building-screens-in-asm-designer/knowledge-article-screens.md).

# Knowledge Article Screens

## Knowledge Submission Screens for the Analyst

Out of the box, ASMs knowledge Submission screens are preconfigured.  However, more often than not, analysts are confused as to what information to put and where to put the information.  This increases the workload for the Knowledge Management Team.  You can add text to the screens to help the analysts understand what information should be entered and how.  The following is an example of a submission screen that includes helpful text for the analyst:

<figure><img src="/files/ZbBJOkq6zES34o2Wkw9u" alt=""><figcaption></figcaption></figure>

## Knowledge Review Screens for the Analyst

The analyst knowledge review screens can also be edited.

This means you can add and reformat fields as you would any other screen.

## Knowledge Review Screens for the User (SSP and Matching Knowledge)

Out of the box, the review screens on the portal are fully configured.  You may want to go in and remove redundant or unnecessary information and add any custom fields you may have included on the submission screen, if relevant.

{% hint style="warning" %}
Do not stack fields side by side in the review screens for the self service portal.  This is because when Matching knowledge loads there is only space for a single column.  The text will wrap in an incongruous manner and make the knowledge preview appear "off".&#x20;
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/configuring-screens/building-screens-in-asm-designer/knowledge-article-screens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.