> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/pdf-converter-for-notes/getting-started/pdf-converter-terminology/archiving-jobs.md).

# Archiving jobs

The SWING PDF Converter's automated archiving feature provides a way of converting Notes documents or emails in selected databases to PDF format without manual intervention.

The PDF files created in this way can be saved in a network shared folder or in a third-party document repository such as SharePoint, Alfresco etc.

In order to run an archiving job, you'll need to create a new archiving job configuration document and select the following job parameters:

1. **Source content** (the databases or mailboxes that are to be processed, and optionally specific folders/views within such databases)
2. **Output settings** (the location where the generated PDF files will be saved, such as a shared network folder or a supported third-party document repository)
3. **Conversion settings** (e.g. PDF page size settings, attachment settings, metadata settings etc.)
4. **Schedule** (an Archiving may run on a schedule (e.g. daily) or it may be started manually)


---

# 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.swingsoftware.com/pdf-converter-for-notes/getting-started/pdf-converter-terminology/archiving-jobs.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.