> 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/getting-started/sign-up-and-sign-in.md).

# Sign up and sign in

Creating a Heisenware account, logging in to it, and taking up an invitation as a member.

Everything you build belongs to an [account](https://docs.heisenware.com/app-manager/app-manager/account.md): your organization on Heisenware. You either create one, or someone invites you into theirs.

## Create an account

Sign up at [heisenware.cloud](https://heisenware.cloud/manager/authentication/sign-up). It is one screen:

{% stepper %}
{% step %}

### Choose the account name

**Account name** is your organization's name on Heisenware, and on the cloud also its address: `acme` becomes `acme.heisenware.cloud`. It takes lower-case letters, digits and dashes, 3 to 63 characters; what you type is folded to that as you type. The screen says at once whether the name is still free, and the name never changes afterwards.
{% endstep %}

{% step %}

### Say who you are

**Continue with Google**, or an **Email** and a **Password** of at least 8 characters with a letter and a digit. Agree to the terms, then create the account.
{% endstep %}

{% step %}

### Verify your email

You get an email with a link. Following it marks your address as verified, which is what the **Verified** column on the [Members](https://docs.heisenware.com/app-manager/app-manager/members.md) screen shows.
{% endstep %}
{% endstepper %}

The account starts with one [workspace](https://docs.heisenware.com/app-manager/app-manager/workspaces.md), `default`, and you are the owner of the account. What a new account gets is written on the sign-up screen: on the Heisenware cloud a trial of the Pro plan with credits for the assistant, on your own server the Free plan until a licence is uploaded.

## Log in

Go to your account's address, `acme.heisenware.cloud`, or to [heisenware.cloud](https://heisenware.cloud/manager/authentication/sign-in) and name the account there.

1. Enter the **Account name**.
2. **Log in with Google**, or your **Email** and **Password**.

Forgotten your password? Fill in the account name and the email, then click **Forgot password?**. The email that arrives leads to a screen where you choose a new password.

## Accept an invitation

A member of an account invites you by email. The link opens **Accept the invite**, which asks for your first and last name and a password, or for Google. Google works only under the address you were invited as.

Taking up the invitation puts you straight into the App Manager, in the workspaces the invitation granted. A link that was replaced by a newer invitation, or that someone already used, says so: ask for a fresh one, or log in if you set a password with it.

{% hint style="info" %}
An invitation to use an App is something else: it makes you an App user, not a member, and it leads into the App rather than into the App Manager. See [App users and access](https://docs.heisenware.com/app-manager/app-manager/users-and-access.md).
{% endhint %}

## On your own server

A [self-hosted](https://docs.heisenware.com/self-hosting/self-hosting.md) installation differs in two ways:

* **No Google**: the sign-in and sign-up screens offer email and password only, unless the installation was given a Google client of its own.
* **Sign-up may be off**: then the sign-up page says so, and the way in is an invitation from a member of an existing account.

The account name is a name there, not an address: the installation has one address, the one your IT gave it.

## Where to go next

* Let the assistant plan and scaffold your Apps: [Your first App with the assistant](https://docs.heisenware.com/getting-started/first-app-with-the-assistant.md).
* Or build one yourself, step by step: [Your first App by hand](https://docs.heisenware.com/getting-started/first-app-by-hand.md).


---

# 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/getting-started/sign-up-and-sign-in.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.
