> 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/it/what-would-you-like-to-learn-about/creator-edit-configuration/product-catalog/schedule-a-collection.md).

# Programma una collezione

{% hint style="warning" %}
This article covers configuring your [Creator Edit portal](https://help.impact.com/brand/what-would-you-like-to-learn-about/creator-edit-configuration/creator-edit-overview.md). [Contact us](https://app.impact.com/support/portal.ihtml?createTicket=true&) to learn more.
{% endhint %}

Dopo aver creato una raccolta, puoi programmarne la pubblicazione e la scadenza automatiche in date e orari specifici. Questa opzione è utile per pianificare in anticipo raccolte stagionali, promozionali o soggette a scadenze.

1. Vai a **\<your name> \[Menu a discesa]** nell’angolo in alto a destra e seleziona **Amministrazione**.
2. Nel menu di navigazione a sinistra, seleziona **Catalogo prodotti** e vai a *Raccolte curate*.
3. Nella colonna *Azioni* della raccolta che vuoi programmare, seleziona **Modifica**.
4. **\[Attiva] Attiva** per rendere attiva la raccolta.

{% hint style="success" %}
**Nota:** Affinché la programmazione funzioni, la raccolta deve essere impostata su *Attiva* anche se la data di inizio è futura.
{% endhint %}

5\. Nella sezione *Programmazione* imposta *Data di inizio*, *Data di fine*.

* Puoi anche scegliere l’ora e il fuso orario.
* Le date di inizio e di fine devono essere future.

6\. Seleziona **Invia**.


---

# 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/it/what-would-you-like-to-learn-about/creator-edit-configuration/product-catalog/schedule-a-collection.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.
