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

# Account management

A Heisenware account is the top-level container for your organization's members and workspaces. All work happens within an account.

## Create a new account

1. Go to the [Heisenware sign-up page](https://heisenware.cloud/manager/authentication/sign-up).
2. Follow the on-screen instructions to choose an account name and sign up with your email or Google account.

## Log in to an existing account

1. Go to your account's unique URL, which follows the format `[your-account-name].heisenware.cloud`.
2. Log in with your credentials.

{% hint style="info" %}

#### Note on URLs

On request, we can also make Heisenware available under your own domain (full white-label). [Contact us](mailto:support@heisenware.com) to discuss.

The URL format above applies to accounts on the Heisenware cloud. If your organization [self-hosts](/account/hosting-and-architecture.md#self-hosted-on-premises) its own instance, the login URL may differ. Ask your internal administrator for the correct address.
{% endhint %}

## Deleting your account

To permanently delete your Heisenware account and all associated data, send a deletion request to our [support team](mailto:support@heisenware.com).

## Managing members

Members are the developers and admins who build and manage Apps in your account. To invite, manage, or remove members, see the [Members](/app-manager/members.md) article.


---

# 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.heisenware.com/account/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.