> ## 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).

# How to Reject a Pending Registration

# How to Reject a Pending Registration

**In this article:**
* Overview
* Rejecting a registration
* What happens when you reject
* Things to keep in mind
* FAQs
* Who can do this

## Overview
When your registration page requires approval, sign-ups arrive as pending requests for you to review. If a request shouldn't be granted access, you reject it. Rejecting doesn't create an account — it simply declines the request and emails the person to let them know. You can optionally include a reason, which is shared with them in that email.

The approvals queue is under **People → Pending**. For the approve side of the review, see "How to Approve a Pending Registration".

## Rejecting a registration
1. Go to **People**, then click **Pending** to open the **Pending Registrations** queue.
2. Find the pending request you want to decline, then click **Reject** on that row. Approve and Reject only appear on rows that are still pending.
3. A confirmation appears: **This rejects {name} and notifies them by email.**
4. Optionally, type a **Reason (optional)**. Anything you enter here is shared with the registrant in the rejection email.
5. Click **Reject** to confirm, or **Cancel** to close without rejecting.

![](https://storage.googleapis.com/superpath-help-centre/how-to-reject-a-pending-registration/01-reject-confirm-modal_76afbce2.png)

## What happens when you reject
* No account is created for the person.
* They're sent a rejection email. If you entered a reason, it's included in that email.
* The request moves to **Rejected** in the queue, showing who rejected it and when. If you gave a reason, it's visible from the information icon beside the status.

## Things to keep in mind
* Rejecting works one request at a time — there are no bulk actions in the queue.
* The reason is optional, but it's the only message the registrant receives about why they were declined, so a short note is often helpful.
* A rejected request can't later be approved. If someone was declined in error, ask them to register again through your registration link.

## FAQs
**Is the reason shown to the registrant?**
Yes. Anything you type in the reason field is included in the rejection email sent to them. Leaving it blank simply sends the rejection without a reason.

**Does rejecting create or delete any account?**
No. Rejecting a pending request never creates an account — the person was never added in the first place. It only declines the request and emails them.

**Can I undo a rejection?**
No. A rejected request stays rejected and can't be approved afterwards. Ask the person to register again if you decline them by mistake.

## Who can do this
**Owners** and **Admins** can review and reject pending registrations from **People → Pending**, reached through the **Pending** button on the People page. **Managers**, **People Managers**, **Content Managers**, **Instructors**, **Employees** and **Restricted** users cannot — they don't see the queue.