> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/reference/your-account/creating-an-account.md).
# Creating an account
To create a new account, select **Sign in** at the top of any page. You can create an account using your academic institution's login credentials, any google account, or passwordless authentication through any email. Your account can then be managed from [your workspace](/reference/your-account/workspace.md).
{% hint style="info" %}
It is strongly encouraged that each individual has only one Redivis account. Your identity on Redivis should map to your real world identity. You should [add multiple logins](/reference/your-account/managing-logins.md) to one account, such as your personal email, university email, or visiting-scholar university email.
{% endhint %}
By creating an account on Redivis, you can gain access to hundreds of restricted datasets and powerful querying tools. There is no cost to creating an account and you may permanently delete your account at any time.
Your account tracks all of your workflows, queries, collaborations, and data approvals with different organizations. After creating an account, you are able to apply for membership with various organizations on Redivis and request access to their restricted data.
---
# 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.redivis.com/reference/your-account/creating-an-account.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.
.png?alt=media&token=43de6fda-04ed-4c05-a01c-8b60a2fe8f2d)