> 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/publish-exam-form.md).

# How to publish an assessment form

1\. Navigate to the Exam Form in the Form Tab.

1. Navigate to the Exam Form in the **Form** Tab.
2. Select the **Form** tab.
3. Click on **Action** button and select **Publish**.
4. Select the **Publication** settings for the Assessment Form being Published:
   * **Candidate Feedback** - Allow exam candidates to submit feedback on the questions in this exam. (**Required Field**)
   * **Instructor Rationale** - Show (to candidates) the rationale behind the questions in this exam for correct and/or incorrect answers.
   * Set **Access** for the Exam:
     * As part of a **Training Program** - The exam is delivered in the context of a specific e-learning module.
     * As a **Standalone** Assessment - The exam is delivered directly to candidates.
     * If **Standalone** is selected, select which group(s) should have access to this exam (Note: If the group does not currently exist, a new Permission List should be created ([**Create a New Group and Adding People to the Group**](https://github.com/InSite/docs/blob/master/ui/help/portal/contacts/adding-new-group/README.md)).
5. Enter **Tile Tag** (The text to be used for the program tile on the portal home page) and **Icon Choice** (The [FontAwesome](https://fontawesome.com/icons?d=gallery) icon to be used for the program tile on the portal home page).
6. After all setting for the Assessment Form has been selected, click the **Publish** button.


---

# 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/publish-exam-form.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.
