> For the complete documentation index, see [llms.txt](https://docs.langstack.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.langstack.com/welcome/get-started/learn-langstack/user-management/what-is-a-privilege.md).

# What is a Privilege?

In the Langstack application, a privilege is a set of permissions relevant to the application feature.

For example, the Entity database privilege contains permissions in a set like Create, Edit, Delete, Data manipulation, and Data View. The Create, Edit, and Delete options are for Entities, and Data manipulation and Data View are for entity records. This gives the group privilege to access the Entity database according to the rights defined in that privilege.

{% embed url="<https://media.langstack.com/documentation/media/images/code/training_manual/chapter_3/ch3whatisapriv.png>" %}


---

# 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.langstack.com/welcome/get-started/learn-langstack/user-management/what-is-a-privilege.md?ask=<question>&goal=<endgoal>
```

`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.