> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/logging-into-structural-for-the-first-time.md).

# Logging into Structural for the first time

When you go to Tonic Structural for the first time, you create an account. How you create an account depends on the type of user you are.

A new Structural user can be one of the following:

* [A completely new user who is starting a Structural 14-day free trial.](/app/quick-start-guide.md) Free trial users use Structural Cloud to explore and experiment with Structural before they decide whether to purchase it.
* [A new user on a self-hosted Structural instance.](/app/structural-user-access/user-access-new-account.md#getting-started-new-user-self-hosted) Self-hosted instances are installed on-premises. The customer administers the Structural users.
* [A new user in an existing Structural Cloud organization.](/app/structural-user-access/user-access-new-account.md#getting-started-new-user-hosted) New users are added to existing organizations based on their email domain.


---

# 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.tonic.ai/app/logging-into-structural-for-the-first-time.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.