> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-customization/indicator-layouts.md).

# Indicator Layouts

Learn about indicator view layouts in Cortex XSOAR 6.15.

{% hint style="info" %}
The indicator Full View is not available for new customers who have not purchased a TIM license.
{% endhint %}

Each indicator type has a unique set of data relevant to that specific indicator type. It is important to display the most relevant data for users.

For each indicator type, there are two views:

* Indicator Summary
* Quick View

You can customize how the information is displayed for existing indicators by modifying the sections and fields for each view.

You can access the Indicator Quick View when you click an indicator on an incident page or on the canvas.

### **Inline Value Fields**

By default, when editing the following inline values in a indicator, the changes are not saved until you confirm your changes (clicking the checkmark icon in the value field).

* Dropdown values
* Text values

These icons are designed to let you have an additional level of security before you make changes to the fields in threat indicators, incidents, and intel reports.

To change the default behavior, set the `inline.edit.on.blur` server configuration to `true`, which enables you to make changes to inline fields without clicking the checkmark. The changes are automatically saved when clicking anywhere on the page or when navigating to another page. For text values, you can also click anywhere in the value field to edit.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-customization/indicator-layouts.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.