> For the complete documentation index, see [llms.txt](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/getting-started-in-the-vci-and-gci/account-creation-and-login/logging-in.md).

# Logging In

### ClinGen Registered User Login

In both the test (<https://curation-test.clinicalgenome.org/>) and production (<https://curation.clinicalgenome.org/>) versions of the ClinGen curation interfaces, users who have registered an email address can login by clicking “**Login**” in the header.

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2F122dR1ijn6Gcy9F3kgfH%2Fheader%20login.png?alt=media\&token=c9b140c4-6473-427a-8b50-910ed9ab9c68)

### Login Troubleshooting

#### Please confirm that:

1. You've authenticated your email by receiving and entering the sent code. Note, codes may take a few minutes to appear in your email inbox.&#x20;
2. If you do not receive your sent code, please check your spam/trash folders in your email account.
3. You are on the correct site (Test or Production).
4. You are using the right email address with correct capitalization. Note that Username is case-sensitive, so "<Curator@clinicalgenome.org>" is NOT the same as "<curator@ClinicalGenome.ORG>"&#x20;
5. Your account has been activated. Note that new production site accounts require validation in a manual approval process. Please allow up to three business days after registration for account activation.&#x20;

#### If you still need assistance, email us at <clingen-helpdesk@lists.stanford.edu>.&#x20;

{% hint style="info" %}
Helpful information to include: Screenshots of error messages received, timeline of actions with time zone (e.g. when did you try to sign in), and what browser you are using to access the site.
{% endhint %}


---

# 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://vci-gci-docs.clinicalgenome.org/vci-gci-docs/getting-started-in-the-vci-and-gci/account-creation-and-login/logging-in.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.