> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/app-maker/getting-started/signing-in.md).
# Signing In
Signing in to App Maker takes two steps: your email and password, followed by a one-time passcode (OTP) sent to your email. The passcode step runs on every interactive sign-in and cannot be skipped.
## Step 1 — Enter Your Credentials
1. Open the App Maker sign-in page.
2. Enter your **email** and **password**.
3. Select **Login**.
If you've forgotten your password, use the **Forgot password** link to reset it before continuing.
## Step 2 — Verify with a Passcode
After your credentials are accepted, App Maker sends a **6-digit security code** to your email and shows the **Verify** screen. The address the code was sent to is displayed at the top, next to a mail icon.
1. Open the email and note the 6-digit code.
2. Enter it into the six boxes on the **Verify** screen. Verification happens **automatically** as soon as all six digits are entered — there's no separate submit button.
3. Once the code is accepted, you're signed in and taken to your destination in the app.
The screen also shows:
* **A countdown timer** — how many seconds the current code stays valid.
* **Resend code** — sends a fresh code. If you request one too soon, a message tells you to wait before trying again. A new code is only re-timed once the previous one has expired.
* **Change** — returns you to Step 1 so you can sign in with a different account.
## Step 3 — Choose an Organization
If you are a member of more than one active organization, App Maker asks which one to open right after the passcode is accepted: **Choose an organization**. Click one to continue. App Maker remembers your choice in this browser and does not ask again on your next sign-in.
You are not asked when you belong to only one active organization, when you have already chosen one in this browser, or when the page you are signing in to already belongs to an organization. You can switch at any time from the header. See [Switching Organizations](/tutorials/app-maker/getting-started/switching-organizations.md).
## If You Get Sent Back to Login
For your security, App Maker ends the passcode session and returns you to the login screen in a few cases:
* **Too many attempts. Please log in again.** — you entered an incorrect code too many times.
* **Too many resend attempts. Please log in again.** — you requested a new code too many times.
When this happens, start again from Step 1.
## Signing In from the CLI
The steps above cover the web interface. To sign in from the App Maker CLI, make sure you're on the **latest CLI version** — older versions are not compatible with the current sign-in flow and will fail to log in. See the [Setup Existing Project on CLI](/tutorials/app-maker/developer-tools-and-cli/setup-existing-project-on-cli.md) guide for the CLI login and configuration commands. If you belong to more than one organization, the CLI login asks which one to use by default. See [Organizations in the CLI](/tutorials/app-maker/getting-started/switching-organizations.md#organizations-in-the-cli).
---
# 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.akinon.com/tutorials/app-maker/getting-started/signing-in.md?ask=&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.
