> 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/approval-management/approval-record-management.md). # Approval Record Management ## 1. Function Description * Administrators can view, transfer, export and download approval records in the system. ## 2. View Approval and Records * Operation steps: \[Approval] > \[Approval Records] * It is convenient for administrators to view, print, export and download past records. * At the same time, you can also click on each approval title to view the project details, including leave duration, type, approval status, etc. * The system also has a filtering function, and you can enter the corresponding type, status, time, etc. as needed. It helps administrators find approval records more accurately and quickly, saving time.

## 3. Transfer Unapproved Approvals * If the approval that allows to be transferred, the approval application can be transferred to other people for approval. * Operation steps: \ Method ① \[Approval] > \[Approval Records] > Click "Forward" under the unapproved operation \ Method ② On the self-service platform, click "Approval Work"

--- # 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/approval-management/approval-record-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.