> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.superpath.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Centralised Learning Requests

# Centralised Learning Requests

**In this article:**
* Overview
* Why use Centralised Learning Requests
* What you can manage
* Related articles
* Who can do this

## Overview
Centralised Learning Requests brings all your learning-related workflows — **learning requests**, **approvals** and **assessment requests** — into one unified place in SuperPath: the **Requests** page. Instead of tracking requests through email or scattered notifications, approvers and administrators get a single hub with full visibility across the organisation.

${frame}[](https://www.loom.com/embed/12378a8942ad45ffa53bb05a1a012c24)

## Why use Centralised Learning Requests
Managing learning workflows can quickly become complex. Bringing everything together helps you:

* **Streamline workflows** by keeping every request in one place.
* **Improve visibility** across all requests and their statuses.
* **Speed up approvals** with quick actions from a single list.
* **Reduce admin overhead** by removing manual, email-based tracking.
* **Empower Admins** with broader oversight when the optional account setting is enabled.

## What you can manage
The **Requests** page is organised into tabs so each type of request has its own space:

* **Learning Requests** — where a learner has to request a Learning that requires approval before it can be assigned, and a nominated approver signs it off.
* **Approval Requests** — where a learner has submitted evidence on a step or assignment that requires approval, and an approver reviews and approves or declines it.
* **Assessment Requests** — where an assessor completes an evaluation step on the learner's behalf.

Each tab can be searched and filtered by status (for example **Awaiting Review**, **Approved** or **Declined**), so you can find and action what needs your attention.

## Related articles
For the step-by-step flows, see:

* *How to Request a Learning That Needs Approval* — the learner's side.
* *How to Approve or Decline a Learning Request* — actioning learning requests as an approver.
* *How to Action an Approval Request* — reviewing submitted evidence and approving or declining it.
* *Learning Requests* — enabling and configuring which learnings require approval.

## Who can do this
The **Requests** hub is available to the people responsible for approving learning: **Owners**, **Admins**, **Managers**, **People Managers** and **Instructors**. Within those roles, each person only sees the requests for the learnings they are a nominated approver of — except that **Admins** and **Owners** can see requests across all learnings when **Allow Admins to approve and assess all learnings** is switched on for the account. The **Learning Requests** tab appears only when **Enable Learning Requests** is turned on. **Content Managers**, **Employees** and **Restricted** users don't action requests here (though any learner can raise a learning request from the Library).