> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/glass-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/glass-documentation/user-guides/administration-guide/2-granting-permission.md).
# 2 - Granting Permission
### View Glass Documentation - Custom Permission
After installation you can control access to the app by using a custom permission, called the **View Glass Documentation** permission.
Without View Glass Documentation permission users will see the following message:
Content that is created by Glass is only accessible to Users / Groups / Other Actors that have the **View Glass Documentation** permission.
Administrators can configure the **View Glass Documentation** permission in the **Permission Scheme** project settings in Jira:
### Avoid using Dynamic Actors
{% hint style="warning" %}
Adding any of the below actors to the View Glass Documentation permission will result in the same as adding "Any Application User" to the permission - **Glass Documentation will be visible for everyone**:
* Reporter
* Current Assignee
* Any Custom User picker (single or multi user)
* Any Custom Group picker (single or multi group)
{% endhint %}
### View Read-Only Workflow permission
This permission is needed to be able to read Workflow and export.
---
# 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.meta-inf.hu/glass-documentation/user-guides/administration-guide/2-granting-permission.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.