# Writing Sample #6

Hello \_\_\_\_\_ ,

We appreciate you reaching out to us with your concern. \[Product Name] provides a simple way to handle multiple ID formats for the same user. 

The **Username Normalization** option is an on/off feature enabled in the **Protecting Applications** section of the **Admin Panel**. 

When enabled, username normalization strips domain information from the user ID before authentication. 

For example, “njones,” “DOMAIN\njones,” and “<njones@domain.com>” all resolve to a single “njones” \[Product Name] user.&#x20;

Owners, Administrators, or Application Managers can enable username normalization.

1. Log into the **Admin Panel**.&#x20;
2. Click **Applications** in the left sidebar, then click the **Protect an Application** button or the **Protect an Application** submenu in the left sidebar.
3. The **Protect an Application** page lists services you can protect with \[Product Name].
4. Select the application you want to protect (or revise) and click the **Protect** button.
5. You’ll see the application’s properties page, where you can update the settings for that application.
6. Scroll down to the **Username Normalization** section.&#x20;
7. To enable Username Normalization, click the radio button next to **Simple**.
8. Click the **Save Changes** button at the bottom of the properties page to enable the change.

If you have any more questions, feel free to let us know. We’re happy to help you address this concern.

***


---

# Agent Instructions: 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:

```
GET https://suntracer2030.gitbook.io/phillip-wilkerson-technical-writing-portfolio/writing-sample-6.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.