> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/images/images-edit-image.md).
# Edit Image
You can assign a name and description to an imported image made available to you through the Glance image catalog. You can add metadata to the image in the form of key-value pairs.
You must be a self-service user or an administrator to perform this operation.
To assign a name and description to an image, follow the steps given below.
1\. Log in to Clarity.
2\. Click Images in the left panel.
3\. Click the Imported Images tab.
4\. Select the checkbox for the image that you want to edit.
5\. Click Edit Image.
6\. Provide values for the following fields.
| **Field** | **Description** |
| ----------- | ------------------------ |
| Name | Name of the Image |
| Description | Description of the Image |
7\. Click Add key-value metadata if you want to add metadata in the form of key-value pairs.
8\. Enter the key and corresponding value.
9\. Repeat steps 6 and 7 if you wish to add more key-value pairs for the image.
10\. Click Save to save the details for the image.
The changes made to the image are saved.
---
# 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.platform9.com/managed-openstack/images/images-edit-image.md?ask=&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.
