> For the complete documentation index, see [llms.txt](https://docs.salesmania.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salesmania.id/website-guidebook/advanced-features/limit-akses-sales-per-product.md).
# Limit Akses Sales per Product
Fitur limit product berguna untuk membatasi akses sales agar hanya bisa melihat dan menjual product yang menjadi bagiannya saja dan tidak bisa mengakses daftar product lain.
Untuk melakukan pembatasan akses sales ke product, Anda dapat membuat **tags** terlebih dahulu melalui `settings` -> `product` -> `tambahkan nama tags` (nama tags bisa disesuaikan dengan kebutuhan perusahaan)
Setelah menambahkan tags yang dibutuhkan, Anda dapat membuka nama sales yang bersangkutan, lalu menambahkan tags tersebut di kolom **Limit to Product Tags**. Contoh pada gambar sales dibatasi berdasarkan kategori product, jadi sales atas nama Celine hanya bisa mengakses product yang memiliki limit tags yang sama dengan yang diberikan pada dirinya yaitu tags **Snack**
Lalu di bagian product juga diberikan tags yang sama dengan yang diberikan pada sales, seperti pada gambar dibawah, di bagian kolom **tags** ditambahkan tags **Snack**
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.salesmania.id/website-guidebook/advanced-features/limit-akses-sales-per-product.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.