> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/shift-roster/using-these-screens-on-the-web-and-phone.md). # Using These Screens on the Web and Phone **Available on:** Web · Phone Every screen in the shift roster, organisation, attendance app and attendance register set has a **web page**; open it from the web menu. The steps are the same as on the desktop; this page lists where a web page looks or works differently. On this page, **on a phone** means a narrow screen: some screens also use the phone layout on a tablet. ## Screen by screen | Screen | Desktop | Web | On the web | | ------------------------------- | ------- | --- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Setup Week-off Patterns | ✓ | ✓ | On a phone, a switch shows the patterns, the off-days or the preview, one at a time | | Setup Payroll Shifts | ✓ | ✓ | As on the desktop. Time cells open a list of times — see below | | Setup Shift Rotations | ✓ | ✓ | On a phone, a switch shows the rotations, the steps or the preview | | Allocate Roster | ✓ | ✓ | A switch (Employees, Assign, Lines) shows one part at a time — on a phone **and** on a desktop | | Generate Roster | ✓ | ✓ | As on the desktop | | Roster Calendar | ✓ | ✓ | Choosing a block and the right-click menu work differently — see **Roster Calendar on the web** | | Setup Designations | ✓ | ✓ | As on the desktop | | Setup Org Units | ✓ | ✓ | On a phone, a switch shows the tree or the units | | Assign Employees to Org | ✓ | ✓ | On a phone, tap **Change ticked employees** to open the bar that sets the ticked employees | | Setup Attendance App Branches | ✓ | ✓ | On a phone, a switch shows the branches or the sites. Three ways to set a site's position — see **Site positions on the web** | | Setup Attendance App Users | ✓ | ✓ | On a phone, tap **Change ticked employees** to open the bar that sets the ticked employees | | Setup Attendance Approval Rules | ✓ | ✓ | On a phone, a switch shows the rules, the levels or **Try it** | | Attendance App HR Review | ✓ | ✓ | The four lists are a switch (Left for HR, Flagged, Auto-absent, Requests), on a phone and on a desktop. On a phone, Branch, the dates and **Refresh** fold behind **Branch and dates** | | Change Log Viewer | ✓ | ✓ | On a phone, the list of changes and the list of fields sit one above the other | | Attendance Register | ✓ | ✓ | On a phone, two tabs: **Employees** and **Attendance** — see **Attendance registers on the web** | | Attendance Register Month Wise | ✓ | ✓ | Choosing a block and the menu work differently — see **Attendance registers on the web** | ## Everywhere on the web * **On a phone**, **Save** and **Close** stay at the bottom right. (Attendance Register has **Close** on both of its tabs — see below.) * **The switch** above the grids shows one list at a time; the list you switch to fills the screen. * **Time cells** that take a 12-hour time, such as **Shift Time In** and **Shift Time Out** on Setup Payroll Shifts, open a list of times in **15-minute** steps. Pick a time, or type one — *9:30 pm* is accepted. * **Closing with unsaved changes** asks first on [Setup Attendance App Branches](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-branches.md), [Setup Attendance App Users](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-users.md) and [Setup Attendance Approval Rules](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-approval-rules.md): **Yes** closes and drops the changes, **No** goes back so you can save. [Attendance App HR Review](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-app-hr-review.md) asks when a New Status has been picked but not saved. The other screens close without asking, so save first. ## Roster Calendar on the web Load the calendar as on the desktop: choose the employees with **Select Employees** or **All Rostered Employees**, then press **Refresh**. The button that chose the employees turns blue. **Refresh** turns amber until the calendar on screen is the one you asked for — including after you change the year or the period. On a screen narrower than a desktop (a phone or a tablet), the **Change days** bar is folded away: tap **Change days** to open it. **Block from here** is in that bar. ### **Choose the days** * **One day:** tap or click its cell. * **A block with a mouse:** drag over the cells. * **A block on a phone:** tap one corner, press **Block from here** (it turns yellow), then tap the opposite corner. Press it again to cancel. **Selected**, under the grid, shows what the change covers — for example *Selected: 3 employee(s) x 3 day(s) = 9*. ### **Make the change** * **The Change days bar:** pick a shift, or tick **Week-off** or **Half-day off**, then **Apply** — or press **As Rostered**. * **Right-click** the cells (long-press on an Android phone) and pick from the menu: **Shift** (then the shift), **Week-off**, **Half-day off**, **As Rostered** or **Block from here**. With a corner marked, the last entry reads **Clear the marked corner**. Then press **Save**. * A right-click **inside** the block changes the whole block. With a corner marked, the cell you press becomes the other corner. Anywhere else, only the cell you press changes. * A block is used once: after a change, the block and the **Selected** count clear. * On an **iPhone** a long-press does not open the menu; use the **Change days** bar. * On a phone, the year, period and employee buttons fold behind **Year, period and employees**, so the calendar has room. Tap it to bring them back. > **Example —** On a phone, Meena gives three employees a week-off on 12, 13 and 14 November. She taps **Change days** to open the bar, taps the first employee's 12 November cell, presses **Block from here**, then taps the third employee's 14 November cell. **Selected** shows *Selected: 3 employee(s) x 3 day(s) = 9*. She ticks **Week-off**, presses **Apply**, then **Save**. ## Site positions on the web On [Setup Attendance App Branches](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-branches.md), select the branch, then the site row (the blank last row for a new site). Three buttons sit above the sites: | Button | What it does | Good for | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | | **Show on Map** | Opens the selected site in Google Maps — the Maps app on a phone, a new tab on a computer | Checking a site's spot | | **My Location** | Puts the device's own position on the site row; the line under the grid says how accurate it was, for example *accurate to about 18 m* | Standing at the site with a phone | | **Pick on Map** | Opens a map over the page with the branch's other sites drawn as circles. Tap the spot, check the circle (the site's radius, or 100 m when none is set), then **Use This Point** | Setting a site from anywhere | * Pasting a position copied from Google Maps into **Latitude** or **Longitude** still works; a *latitude, longitude* pair can be pasted into either cell. * A position set any of these ways is not kept until you **Save**. * **My Location** works only when the page is opened over a secure (**https**) address. It asks for permission the first time; allow it. * A phone's position is less accurate indoors. Check the spot with **Show on Map** before saving. ## Attendance registers on the web On a wide screen both registers look and work as on the desktop. On a phone they are laid out for one hand. ### **Attendance Register on a phone** The screen has two tabs, **Employees** and **Attendance**. 1. On **Employees**, search and tap an employee. **Attendance** opens with their name at the top, then Present / Absent, the times grid and the buttons. 2. Enter the times and press **Save**. The next employee opens straight away; after the last one in the list you are back on **Employees**. 3. With **Multi Employee**, tapping and ticking stay on **Employees**; open **Attendance** to save, and it goes back to the list. **Close** is on both tabs. The search waits until you stop typing, and no longer jumps into the times grid. ### **Attendance Register Month Wise on the web** * **Choose a block:** drag across days and employees. Click an employee's **S.No.** to take their whole month, or press **Select all** for everyone and every day. The count above the grid shows what is chosen, for example *Selected: 3 employee(s) x 5 day(s) = 15*. * **Set Attendance** opens the panel for the block, as on the desktop. **Double-click** a day to open the panel for that one day. * **Right-click** the block for **Present** and **Absent** (each with its kinds of day), **Set Attendance...**, **View Leave Balance**, **Delete Attendance** and **Block from here** (with a corner marked, **Clear the marked corner**). On a phone: * **Month and options** folds the year, month and buttons away to give the grid room; tap it again to bring them back. The **Select all** / **Block from here** bar stays in view. * To choose a block, tap one corner day, press **Block from here**, then tap the other corner. * **Press and hold** a day for the menu. It opens in two steps: tap **Present** or **Absent**, then the kind of day (**Back** returns to the first list). * A swipe scrolls the grid; it does not open the menu. **Full Day + Overtime Hrs** needs the hours typed in, so it is only on the panel, not on the menu. --- # 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/shift-roster/using-these-screens-on-the-web-and-phone.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.