> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/fr/what-would-you-like-to-learn-about/creator-program/introduction-welcome-to-creator/step-4-add-remove-and-review-campaign-tasks.md).
# Étape 4 : ajoutez, supprimez et examinez les tâches de campagne
Une fois que vous avez décidé de lancer votre campagne et que les créateurs appropriés l'ont rejointe, vous pouvez commencer à leur attribuer des tâches à accomplir.
#### Ajouter ou supprimer des tâches de campagne
Les créateurs participant à votre campagne doivent accomplir des tâches pour être payés. Vous avez créé ces tâches lors de la configuration de votre campagne. Cependant, vous pouvez [ajouter ou supprimer des tâches](/brand/fr/what-would-you-like-to-learn-about/creator-program/creator-campaigns-for-brands/add-or-remove-creator-campaign-tasks-as-a-brand.md) au fur et à mesure de l'avancement de votre campagne.
#### Examiner et approuver les tâches de la campagne
Une fois qu'un créateur a terminé une tâche ou un brouillon, vous pouvez [examiner et approuver](/brand/fr/what-would-you-like-to-learn-about/creator-program/creator-campaigns-for-brands/rename-and-review-creator-campaign-tasks.md) la tâche avant que le créateur ne la publie.
---
# 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://help.impact.com/brand/fr/what-would-you-like-to-learn-about/creator-program/introduction-welcome-to-creator/step-4-add-remove-and-review-campaign-tasks.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.