---
title: Adding global unprotected resources
description: Create a new global unprotected resource in PingAccess.
component: pingaccess
version: 9.0
page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_adding_global_unprotected_resources
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_user_interface_reference_guide/pa_adding_global_unprotected_resources.html
revdate: February 6, 2023
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Adding global unprotected resources

Create a new global unprotected resource in PingAccess.

## About this task

|   |                                                                                                                                                                                                                                                                                                                                                                |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | The following steps describe how to globally make resources unprotected. Because any resource captured by the wildcard path of any entry is left unprotected for all applications, you must carefully plan these entries. To make a resource unprotected for a specific application, see [Adding application resources](pa_adding_application_resources.html). |

## Steps

1. Click **Applications**, then go to **Applications > Global Unprotected Resources**.

2. Click **[icon: plus, set=fa]Add Global Unprotected Resource**.

3. In the **Name** field, enter a name for the entry.

4. **Optional:** In the **Description** field, enter a description for the entry.

5. **Optional:** If you want to record access requests for this resource in the audit store, select the **Audit** check box.

6. In the **Path Pattern** field, specify the path pattern that identifies the global unprotected resource.

   This entry must start with a forward-slash (/) and can contain one or more wildcard characters (`*`), such as:

   * `/*.jpg`

   * `/resources/*.css`

   * `/*/resources/favicon.ico`

     |   |                                                                                                                                                                                                                                                              |
     | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
     |   | Global unprotected resource paths are relative to the application context root. Reserved paths such as `/pa`, `/pa/`, or `/pa/*` are allowed at the global level, but will not be evaluated for applications that are configured with a context root of `/`. |

7. To enable the global unprotected resource, select the **Enabled** check box.

8. Click **Save**.