> For the complete documentation index, see [llms.txt](https://digitals-private-organization.gitbook.io/rizones45678.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitals-private-organization.gitbook.io/rizones45678.org/mobile-app-guide/log-in.md).

# Log in

Sign in with the mobile number registered with Rotary. There is no password.

You sign in with the mobile number registered with Rotary. There is no password, only a one time OTP sent by SMS.

{% stepper %}
{% step %}

### Open the app and accept the terms

You are asked only the first time.
{% endstep %}

{% step %}

### Stay on the Member tab

On the **Welcome Back** screen, **Member** is selected by default. The other tab is **Family**.
{% endstep %}

{% step %}

### Choose your country and enter your mobile number

Country defaults to **India (+91)**. Enter the number registered with Rotary, then tap **Continue**.
{% endstep %}

{% step %}

### Enter the OTP

On the **OTP Verification** screen, type the six digit code sent by SMS, then tap **Verify & Continue**. If it does not arrive, use **Resend** once the timer runs out.
{% endstep %}

{% step %}

### You land on the Home screen

That is it. You are signed in.
{% endstep %}
{% endstepper %}

> **Screenshot slots:** the Welcome Back sign in screen, and the Enter OTP Code screen.

{% hint style="warning" %}
**No OTP arriving?** Check that the number you entered is the one registered with your club. A Club Admin can correct it in **Directory**, then you can try again.
{% 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://digitals-private-organization.gitbook.io/rizones45678.org/mobile-app-guide/log-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.