> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2022/spring-22-release/quick-view-and-edit.md).
# Quick View & Edit
The new Quick View and Edit panel provides a faster way to see Item details and update them.
Clicking on a row will open the panel, which displays all the information on the Full Item page without the player and configurator, including: Item Name, Description, Referenced Assets, tags, Metadata, Attributes, and Rules.
To edit, click on any of the fields.
Clicking the green chevron next to Asset references opens that Asset in a new tab.
Metadata can be added and edited.
Global and Local attributes can be added. Existing attributes can be modified.
New Rules can be added and existing Rules can be toggled, cloned, and deleted.
The header is always visible to give you access to the Save button, which turns green if there are changes to be saved.
The three-dot menu provides access to the Full Item Page with the Player view, Configurator, and additional Item options.
---
# 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://community.threekit.com/releases/2022/spring-22-release/quick-view-and-edit.md?ask=&goal=
```
`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.