> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/admin-management/permission-management.md).
# Permission Management
## 1. Setting Account Permissions
* Administrators can also set relevant permissions and visibility levels for other employees in the system. For example: Only the employee can manage employees, approve salary and other items without permission.
* In addition to giving colleagues access and editing permissions for the entire template, the system also provides the option of subdividing permissions; for example, if the administrator wants to assign an employee to only edit changes for colleagues, but cannot edit or add attendance rules/attendance groups, the administrator can Through the sub-permission function, only the colleague is given the permission to enter the "Shift Management" page.
* After making the above settings, when employees log in to the management backend, they will only see the pages assigned to them by the administrator.
---
# 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.coreway.com/coreway-hr/admin-management/permission-management.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.
