> 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/setup-location-sharing-notice.md).

# Setup Location Sharing Notice

When an employee's **Tracking** is set to **PINGS** in **Setup Attendance App Users**, the **Logic Workforce** app shares their location while they are on duty - but only after they have read and agreed to a notice in the app. **Setup Location Sharing Notice** is where HR writes that notice and sees who has agreed.

The standard notice has two blanks in its text: **\[Company name]** and **\[HR contact]**. The app does not show the notice, and nobody can agree to it, until both are filled in.

***

### **Step 1: Open the screen**

* Navigate to **Payroll Setups** and open **Setup Location Sharing Notice**.
* The line at the top shows the notice's **version** and the date it was created, whether the app shows it, and what saving a change will do.
* On the right is the list of employees on location sharing, with each one's answer.

***

### **Step 2: Fill in the notice (new company)**

* Type the **Company name** and the **HR contact** - a named person or desk, with a phone number or e-mail, for questions and complaints.
* Click **Fill in notice**. The blanks in the **Notice text** (and in the **Title**, if you added one there) are replaced with what you typed. If you typed only one of the two, the other blank stays.
* Read the notice, change the wording if needed, and click **Save**. The screen does not save a notice that still has a blank.
* Once nothing is left to fill in, the button shows **Already filled in** and the two boxes are greyed out.

***

### **Step 3: Start again from the standard wording**

* Click **Default notice** to put the standard title and text back in the boxes, with the two blanks.
* When the boxes hold other text, the screen asks first (the answer it offers is **No**). When they are empty, the standard notice goes straight in; when they already hold it, the screen just says so.
* Nothing is saved until you click **Save**. Fill in the company name and HR contact again (Step 2) and save.
* When there is no notice yet, start here: click **Default notice**, fill it in and save. It becomes version 1.

***

### **Step 4: Change the wording**

* Edit the **Title** (up to 100 characters) or the **Notice text** and click **Save**. You need modify rights on the screen. A notice that has not changed is not saved.
* **Nobody has answered the notice yet:** the change is saved into the same version.
* **Someone has already answered it** (agreed or withdrawn): the change is saved as a **new version**. The screen asks first, because **every** employee on location sharing must then agree again - their location is not shared until they do.
* Each save is recorded in the change log.

> **Example - a new HR contact**
>
> Version 1 of the notice names Meena, 98100 12345, as the HR contact, and 40 employees have agreed to it. Meena leaves, so HR opens the screen and, in the **Notice text**, changes her name and number to Arjun's, 98100 67890. (**Fill in notice** shows **Already filled in**, as the notice has no blanks left.) HR clicks **Save**; the screen warns that this adds version 2 and that everyone will be asked again, and HR clicks **Yes**. The line at the bottom reads *Saved as version 2 - employees on location sharing are asked to agree again.* In the list, the 40 employees now show **Agreed to version 1 - asked again** until each one agrees to version 2 in the app.

***

### **Step 5: See who has agreed**

* The list shows every working employee who can use the app and has **Tracking** set to **PINGS**: **SNO.**, **EMPLOYEE**, **BRANCH**, their **ANSWER** and when they answered (**ON**).
* **ANSWER** is one of:
  * **Agreed (version …)** - agreed to the current notice.
  * **Agreed to version … - asked again** - agreed to an older version; the app asks them to read the new one and agree.
  * **Withdrawn** - withdrew their consent in the app (**More** > **Location sharing**).
  * **Not answered yet**.
* The line above the list counts each kind, for example *Employees on location sharing: 42 - 38 agreed, 2 to agree again, 1 withdrawn, 1 not answered*.

***

### **On the web**

* The same screen is on the web. On a phone or other narrow screen, a switch shows the **Notice** or the **Consents**, one at a time.


---

# 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/setup-location-sharing-notice.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.
