> 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/user-access/logic-global-admin/pos-options/pos-options-1/implement-user-access-rights-in-link-sr.md).

# Implement User Access Rights in Link SR

**YouTube:** [How to Implement User Access Rights for Linking Sale Returns in Sale Bill?](https://www.youtube.com/watch?v=hsZ0ENK6Bpc)

## How to Implement User Access Rights for Linking Sale Returns in Sale Bill?

This tutorial explains how to **restrict access to Sale Return (SR) linkage** based on **defined user rights**, ensuring users can only access sale return entries from authorized account groups.

***

### Access Global Settings in Logic Admin

* Open **Logic Admin**.
* Navigate to **Global Settings**.
* Under **POS Options**, go to the **POS Options 1** section.
* Locate and enable the option labeled as:&#x20;

> **"Implement User Access Rights in Link SR"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F4DI4Kt60vptyLvQJcfJY%2FLink%20SR.png?alt=media&amp;token=8dc3aea8-344d-4884-9f91-ed18e45c605f" alt=""><figcaption></figcaption></figure>

* Click **Save** and **restart the software** to apply the changes.

***

### **Configure Account Group Access**

* In **Logic Admin**, locate the **User Access Rights** module.
* Select the relevant **Company** and **User** from the dropdown lists.
* Then, Navigate to the **Accounts Tab**.
* Under **Account Group**, select the group to which the user should have access.
* Click on **Add Selection** to assign it to the user.
* Then click on **Grant Access** to finalize permissions.

> Only accounts belonging to this group will now be accessible during billing operations involving Sale Return linkage.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FKHx9V4n0SzFqr9yyAYy0%2FAdd.png?alt=media&amp;token=b824fcc0-65cc-4509-933b-2163d3ea8ef2" alt=""><figcaption></figcaption></figure>

* Click **Save** to confirm the settings.
* Restart the software for the changes to take effect.

***

### Implement **the Configuration in Sale Voucher**

* Log in with the **configured user ID**.
* Open the **Sale Voucher** window.
* Complete the transaction details.
* Press **F3** to access the **Link SR (Sale Return)** option.
* Click **Link** to open the pending SR selection window.
* The system will **only display pending Sale Returns** linked to **parties under the authorized account group**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FS6qKGc9MWrJCDGpx9eWE%2FSale.png?alt=media&amp;token=8deb4846-6567-4ace-b3ec-d7339d37abaa" alt=""><figcaption></figcaption></figure>

* Sale returns for unauthorized account groups will **not appear** in the search results.

***

### **Benefits of This Feature**

* Maintains **strict access control** on sensitive customer data.
* Prevents misuse or incorrect application of **sale return vouchers**.
* Supports **role-based permissions** and improves operational accountability.


---

# 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/user-access/logic-global-admin/pos-options/pos-options-1/implement-user-access-rights-in-link-sr.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.
