> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/platform/issues/issue-settings.md).

# Issue Settings

Customize how issues are handled within your account.

The Issue Settings section allows you to modify how specific issues are handled within your account, including adjusting their severity ratings and automatically applying tags.

## Use Cases

* Adjust issue severity ratings to match your organization's risk tolerance
* Add tags to automatically group and categorize specific issues

## Managing Issue Settings

You can manage issue settings by visiting *Settings →* [Issue Settings](https://app.halosecurity.com/user/settings/issues/) in your account.

1. Navigate to *Settings →* [Issue Settings](https://app.halosecurity.com/user/settings/issues/)
2. Click the **+** icon to add a new setting
3. Search for and select the issue you want to modify
4. Configure the following options:
   1. Custom Severity: Adjust the severity rating (1-5) for this specific issue
   2. Tags: Add tags that will be automatically applied to this issue
5. Click **Save Changes**


---

# 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://docs.halosecurity.com/docs/platform/issues/issue-settings.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.