> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/assessments/editing-forms/edit-questions.md).

# Edit Assessment Questions

Depending on the Organization setting, Administrators are able to edit existing Assessment questions.

Depending on the Organization setting, Administrators are able to edit existing Assessment questions. When editing questions that have already been published to a Form, a warning message will appear at the top of the page.

![edit-assessment-questions-1-0.png](https://e02.insite.com/files/sites/e02/edit-questions/edit-assessment-questions-1-0.png)

This warning message is to advise admins that there are existing exam forms using the question and how many submissions have been received for the question they are about to edit. If a change is made to the question, and it can potentially affect previous submissions, you will be directed to the Regrade Attempts screen after making your changes.

Depending on the change that was made to the question, an Admin can choose if they want to regrade the question or update the question without regrading.

**Example:** If the incorrect option was setup as the correct answer, and a admin corrects the mistake, they can choose if the fix should be applied to previous attempts or not by selecting one of the Regrade Options provided

![edit-assessment-questions.png](https://e02.insite.com/files/sites/e02/edit-questions/edit-assessment-questions.png)

Any questions being edited will be available for learners who have not started a exam. If changes are made to a question, while a exam is in progress, the change will not be available to the learners.

Additional information about question configuration settings can be found here


---

# 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.shiftiq.com/help/assessments/editing-forms/edit-questions.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.
