> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relyant.app/llms.txt
> Use this file to discover all available pages before exploring further.

# QR Portals

> Let anyone report an issue by scanning a QR code, with or without a Relyant account

QR portals are public pages where people report maintenance issues. Print a portal's QR code and post it around campus. Anyone who scans it can submit a work request, even without a Relyant account.

> [!NOTE]
>
> QR Portals is part of the **Maintenance** module. You need read access to QR portals to open the page, and create or delete access to manage custom portals.

## Types of portals

| Portal | Covers | Where to get it |
| - | - | - |
| **Default Portal** | All locations and all assets | **QR Portals** page |
| **Custom portals** | Locations and assets you choose | **QR Portals** page |
| **Asset or location portal** | A single asset or location | That item's page under **Assets** or **Locations** |

On a single asset or location portal, people choose **Report an Issue**. If the item is bookable and bookings are turned on, they can also choose to book it.

## Create a custom portal

**1. Open QR Portals**

In the sidebar, under **Maintenance**, click **QR Portals**.

**2. Click Create Portal**

Click **Create Portal**.

**3. Name the portal**

Enter a **Name**, for example "Main Campus Portal".

**4. Set the scope**

Under **Locations**, choose **All Locations** or **Specific Locations**. Under **Assets**, choose **All Assets** or **Specific Assets**. If you choose a specific option, select at least one item.

**5. Save**

Click **Create Portal**. The new portal appears in the list with a badge that summarizes its scope.

## Share a portal

For any portal, click **Copy link** to copy its URL, or click **Download QR** to save the QR code image for printing.

To change a custom portal, click **Edit**. To remove it, click **Delete**.

> [!WARNING]
>
> Deleting a portal stops its QR code from working. Replace any printed codes before you delete.

## What people see when they scan

**1. Describe the issue**

The person picks a location, and an asset if relevant, from the options in the portal's scope. They then select a category, add a short summary and description, and attach photos or videos if needed.

**2. Add contact details**

If they aren't signed in, they can click **Login via Email** to track the request from their dashboard, or click **Request as Guest** and enter their name, email, and phone number.

**3. Get a reference number**

After they submit, they see **Request Submitted** with a **Reference Number**. They can click **Submit Another Request** to report more.

New submissions appear under **Maintenance** > **Requests** for your team to review. Everyone who manages work requests gets a "New request" notification for each submission, including guest ones, by email, in-app, or push depending on their notification preferences.

Update emails sent to the requester include a link to a public status page. That page shows the request details, **Progress Updates**, and whether a work order was created.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.