> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-console/authorization/signing-up-for-dt-console.md).

# Signing Up for DT Console

A DT Console account allows you to access DT products. Once the DT Team approves and activates your account, you can [sign in](/dt-console/authorization/signing-in-to-the-dt-console.md) to the DT Console.

To sign up for a DT Console account:

1. From the [DT Console](https://console.fyber.com/sign-up), click **Sign Up**.\
   The sign-up page opens.

<div align="left" data-with-frame="true"><figure><img src="https://2949766846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLbREhkP3WlLtP6TNVZ2Q%2Fuploads%2FILa2zXGFy3hMyqeUp3IN%2FSigning%20Up.png?alt=media&amp;token=7ac588d1-3727-4bc4-a51f-3dc42ec984c1" alt="" width="500"><figcaption></figcaption></figure></div>

2. Enter the required information. Use an official company email address
3. Click **Confirm**.
4. Check for a confirmation email from DT. Your email filters may affect the delivery of this email. Once you receive this email, you can [sign in](/dt-console/authorization/signing-in-to-the-dt-console.md) to the DT Console.


---

# 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.digitalturbine.com/dt-console/authorization/signing-up-for-dt-console.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.