> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/campaigns/achievements/managing-achievements.md).

# Managing Achievements

In this article, you will get familiar how to manage the achievements in Open Loyalty

## Editing achievements

{% hint style="success" %}
**To edit the Achievement:**

1. Go to **Achievements**
2. Click the context menu of the selected Achievement
3. Click **Edit**
4. After making changes click **SAVE ACHIEVEMENTS**

{% hint style="danger" %}
Changing core achievement settings or rules can reset member progress. Segments using this achievement will also stop working and need to be recreated. Only basic achievement settings and trigger conditions can be updated without resetting member progress.

![](https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/zQlwBjzjP8GrSzmTG9kj/image.png)
{% endhint %}
{% endhint %}

***

## Duplicating achievement

{% hint style="success" %}
**To duplicate the Achievement:**

1. Go to **Achievements**
2. Click the context menu of the selected Achievement
3. Click **Duplicate achievement**
4. Click **SAVE ACHIEVEMENTS**
   {% endhint %}

***

## Duplicating rule in the achievement

{% hint style="success" %}
**To duplicate a rule the Achievement:**

1. Go to **Achievements ->** specific **Achievement**
2. Scroll down to the **Rules** click the context menu of the rule
3. Click **Duplicate rule**

<img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/2FBfOCnVMcvpUHZ3t03K/image.png" alt="" data-size="original">

1. Click **SAVE ACHIEVEMENT**

{% hint style="danger" %}
If the achievement already has members, duplicating a rule can reset member progress. This may also impact segments that depend on achievements. A warning appears before you save.

![](https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/q0AH401z8tH1gBJzclVI/image.png)
{% endhint %}
{% endhint %}

## Achievement export/import

In the Achievements section, you can export and import achievements. These actions require a file in a `.json` format.

{% hint style="info" %}
You can export/import up to 50 achievements at once (in one file).
{% endhint %}

### Exporting achievements

{% hint style="success" %}
**Exporting achievement/s how-to**

<img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/ty1O7S7JZU9UoAfUhPJd/image.png" alt="" data-size="original">

To export a single achievement or several achievements:

1. Go to **Achievements**&#x20;
2. Click **SELECT TO EXPORT**

After clicking this button you will see the checkboxes next to the achievement name.

<img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/i3GSaU7KiCMHxLqKhnTz/image.png" alt="" data-size="original">

3. Select the achievements you want to export to the JSON file&#x20;
4. Click **EXPORT TO .JSON FILE (X)** to download the achievement file
   {% endhint %}

### Importing achievements

{% hint style="success" %}
**Importing achievement/s how-to**

<img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/FUjtU5mrrNEZhS2Co1JF/image.png" alt="" data-size="original">

1. Go to **Achievements**&#x20;
2. Click **Add achievements -> Import achievements**

After clicking this button you will see the pop-up window to upload the JSON file

<img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/HwJbUdyQfxrTVcoE7Dut/image.png" alt="" data-size="original">

3. Follow the instructions from the popup window.
4. Click **IMPORT** to download the file with achievements
5. After importing, the achievement you will see the list of all successful and/or achievements that require the action to edit.
   {% endhint %}

### Duplicating Achievements to a different tenant

{% hint style="success" %}
**Exporting achievements to a different tenant how-to:**

<img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/ty1O7S7JZU9UoAfUhPJd/image.png" alt="" data-size="original">

To export achievement(s):

1. Go to **Achievements**&#x20;
2. Click **SELECT TO EXPORT**

After clicking this button you will see the checkboxes next to the achievement name.

<img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/i3GSaU7KiCMHxLqKhnTz/image.png" alt="" data-size="original">

3. Select the achievements you want to export to the different tenant
4. Click **Export achievements to 'Different tenant' ->** Select the targeted tenant

![](https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/hOcZ850Gi8CAvld0ubTt/image.png)

5. To complete the action click **Copy achievement(s) and view target tenant.**

![](https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/fUrW6eFc6v8hKKgFbKrJ/image.png)

6. After importing the achievement(s) you will see the list of all successful and/or campaigns that require the action to edit.
   {% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/campaigns/achievements/managing-achievements.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 `build a script that syncs our docs to a CMS` 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.
