> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/editer-le-registre/establish-your-record.md).

# Establish your record

Learn how to design and manage your processing activity record using Dastra.

## To set up your record in Dastra, there are two possibilities:

* Either you already have a record, in which case you can import it into Dastra
* Or you don't have one, and you must create it from scratch and use the proposed processing models as a guide

## Upload your existing record

With Dastra, you can easily upload your existing processing activity record instead of having to manually enter it, regardless of the current format - excel, text or csv.

{% content-ref url="/pages/-MBInjuj88JTGEFUbXRB" %}
[Export / import the record](/en/features/editer-le-registre/upload-your-existing-record.md)
{% endcontent-ref %}

{% hint style="info" %}
Don't forget to publish your data processing activities if you want them to be reflected in the dashboard.
{% endhint %}

## Create a new processing activity record from scratch

With Dastra, a record is automatically created as soon as the workspace is defined. If you don't want to download an existing record, you can start filling in the default one immediately when creating your first processing activity. If you want to know how, click on the following link:

{% content-ref url="/pages/SfET9imfcYryS8JcO4LP" %}
[Declare a processing activity](/en/features/editer-le-registre/declare-a-treatment.md)
{% endcontent-ref %}


---

# 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://doc.dastra.eu/en/features/editer-le-registre/establish-your-record.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.