> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/mobile-app/ios-outsmart-app/core-functionalities/sign-in-and-switch-users.md).

# Sign in and switch users

Log in with your account, a QR code, or biometrics, and switch users.

## Sign in and switch users

### Sign in and switch users

The opening screen shows a tutorial for new users. Returning users see **Welcome back**.

### Log in with your account

{% stepper %}
{% step %}

#### Choose a sign-in method

Tap **Log In with Username**. Use Face ID or Touch ID when enabled.
{% endstep %}

{% step %}

#### Authenticate

Enter your credentials or confirm with biometrics.
{% endstep %}
{% endstepper %}

### Log in with a QR code

{% stepper %}
{% step %}

#### Start QR login

Tap **Log In with QR Code**.
{% endstep %}

{% step %}

#### Scan the magic link

Allow camera access. Scan the OutSmart Magic Link QR code.
{% endstep %}
{% endstepper %}

### Switch users

Tap **Switch User** before another person uses the device. The app warns about unsynced data before removing it.

### Keep in mind

* Signing in requires an internet connection.
* Enable Face ID or Touch ID after your first login.
* Only valid OutSmart Magic Link QR codes work.


---

# 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://knowledge.out-smart.com/mobile-app/ios-outsmart-app/core-functionalities/sign-in-and-switch-users.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.