> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/login.md).
# Login
## Overview
The **Login** screen provides different options for users to securely access DinePlan and record their attendance.
Users can access DinePlan using the following options:
* **Login with PIN** – Enter the assigned PIN to access the application.
* **Biometric Login** – Use the configured biometric authentication method to log in.
* **Attendance** – Record attendance when starting the work session.
The Login screen provides the required options for accessing DinePlan and managing the user's login and attendance activities.
## **Purpose**
* It authenticates restaurant staff before they can access DinePlan.
* Depending on restaurant configuration, users can log in using a PIN or a registered biometric fingerprint.
* Besides authentication, the screen also provides access to attendance marking, cloud synchronization, business date information, and application exit.
## **Login Using PIN**
1. Open the DinePlan application.
2. Enter your “PIN”.
3. Select “Enter”.
3. You are logged in to the application.
## **Login Using Biometric Authentication**
1. Open the DinePlan application.
2. Select “Scan”.
3. Place your registered finger on the biometric scanner.
4. Wait for the fingerprint to be verified.
5. Once the fingerprint is successfully verified, you are automatically logged in to the application.
## **Record Attendance**
1. Select “Attendance”.
2. Log in using one of the following methods:
1. Biometric Finger Scan
1. Place your registered finger on the biometric scanner.
2. Your attendance is recorded after successful fingerprint verification.
3. PIN
1. Select “PIN”.
b. Enter the "PIN"
c. Select “Enter”.
4. Employee Code
1. Enter the “Employee Code”.
1. Select “OK”.
2. Your attendance is recorded.
5. Your attendance is recorded.
## **Screen Elements**
**PIN Login**
* Log in using your assigned employee PIN.
**Biometric Login**
* Log in by scanning your registered fingerprint using the biometric scanner.
**Attendance**
* Record cashier attendance before starting work.
**Pull**
* Pulls the latest data and configuration updates from DineConnect.
* Use this option when:
* New menu items are added
* Prices are updated
* Configuration changes are made
* You are instructed to sync the POS
**Business Date**
* Displays the active business date used for restaurant transactions.
**Exit**
* Closes the DinePlan application.
## Accessing the Dashboard
Once the user successfully logs in to DinePlan, the **Dashboard** is displayed. The Dashboard provides access to the main modules and features available to the user based on their permissions.
The following section explains the Dashboard and the features available in it.
---
# 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://help.rbsgo.com/dineplan/login.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.
