> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/supplier-setting/supplier-permissions.md). # Supplier Permissions ### Supplier Group

Supplier groups with configured names hidden.

Manage supplier groups to categorize suppliers by type, region, or role. Each group has a **Group API Name** (used for integrations) and a **Group Name** (display name). Click **+ New** to create a group. Use the three-dot menu on each row to edit or delete. ### User and Supplier Group Mapping

Assign users to supplier groups to control which employees can access and manage specific sets of suppliers. Each group is shown as an expandable section listing its assigned users with a member count. Click **+ New** within a group to add a user mapping. Use the three-dot menu to remove a mapping. --- # 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://docs.docbits.com/administration-and-setup/settings/supplier-setting/supplier-permissions.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.