> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/account/management.md).

# Account Management

Learn how to keep your Trybit account secure.

Your Trybit account is your profile in the system: you log in with email and password, and within it you can run several projects (see [Adding a Project](/getting-started/add-project.md)), invite team members, and configure notifications.

### Login and access recovery

Email is the only way to log in and recover access. How to register, change your password, and what to do if emails don't arrive — on the [Registration and Account Access](/getting-started/sign-up.md) page.

### What belongs to the account vs. the project

The account is the top-level record: email, password, two-factor authentication, team member access, notifications, balance, and transaction history across all projects. All settings for a specific payment-acceptance method (currencies, fees, integration, payment page) belong not to the account but to an individual project within it — see [Project Settings](/getting-started/project-settings.md).

{% hint style="success" %}
If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support).
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.trybit.com/account/management.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.