> 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/records/achievements/define-achievement.md).

# Create New Achievement Template

On the Admin Home Page, select Records Toolkit

#### There are 2 ways of creating a New Achievement

#### Option 1

On the **Admin Home Page**, select **Records** Toolkit

Under the **Achievements** heading, click on the **Achievement Template** counter.

Click the **Add New Achievement** link at the top of the page.

* Add **Title** of Achievement
* Add **Tag** (The descriptive Tag for this achievement)
* Add **Description** of the Achievement
* Select the **Achievement Expiry** (If achievement expires, select whether this is a fixed date or relative to when issued)
  * No Expiry
  * Fixed Date: Add the date the Achievement expires
  * Relative Date: Set the duration the Achievement is valid for
    * Months
    * Years<br>

#### Option 2

On the **Admin Home Page**, select **Records** Toolkit

Under the **Achievements** heading, click on the **Achievement Template** counter.

Select any **Title** on the Achievement Templates search page.

Click the **New** button on the top right side of the page. Proceed as directed above.<br>


---

# 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/records/achievements/define-achievement.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.