> For the complete documentation index, see [llms.txt](https://help.solar-archive.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solar-archive.com/docs/managing-users/creating-data-guardian-user-accounts.md).

# Creating Data Guardian User Accounts

A Data Guardian is, in **Solar Archive**, an email address to which transcripts of administrator access and privileged user searches will be sent. At least one data guardian must be added, before adding any local user accounts.

### Setting up a Data Guardian User

Now that we've setup a privileged user that can search the entire archive, let's setup a Data Guardian to police those actions.

1. Navigate to **Basic Configuration** > **Data Guardians**.
2. Look for the **Data Guardians** Section
3. Enter / Select the required values in the fields. Refer to the below field descriptions.
4. Click **Add**
5. Review all the values and click **Save**.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.solar-archive.com/docs/managing-users/creating-data-guardian-user-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.