---
title: Configuring the application portal
description: Configure the PingOne application portal.
component: pingone
page_id: pingone:applications:p1_configuring_the_application_portal
canonical_url: https://docs.pingidentity.com/pingone/applications/p1_configuring_the_application_portal.html
revdate: May 22, 2025
section_ids:
  steps: Steps
---

# Configuring the application portal

You can configure branding and theme options for the application portal and choose a sign-off method for end users.

## Steps

1. In the PingOne admin console, go to **Applications > External Applications**.

2. To apply the active environment theme to the application portal, select the **Apply active theme to Application Portal** checkbox. Learn more in [Branding and Themes](../user_experience/p1_branding_themes.html).

   |   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
   | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | You can add links to resources your users might find helpful, such as status pages, user guides, and applications that aren't accessible through single sign-on (SSO) *(tooltip: \<div class="paragraph">&#xA;\<p>The process of authenticating an identity (signing on) at one website (usually with a user ID and password) and then accessing resources secured by other domains without reauthenticating.\</p>&#xA;\</div>)*. Learn more in [Adding resource links to the application portal](p1_adding_resource_links_to_application_portal.html). |

3. For **Sign Off Method**, choose either of the following for PingOne to use when end users sign off from the application portal:

   * **OIDC Logout** (default): Allow the end user to sign off from the application portal using OpenID Connect (OIDC) *(tooltip: \<div class="paragraph">
     \<p>An authentication protocol built on top of OAuth that authenticates users and enables clients (relying parties) of all types to request and receive information about authenticated sessions and users. OIDC is extensible, allowing clients to use optional features such as encryption of identity data, discovery of OpenID Providers (OAuth authorization servers), and session management.\</p>
     \</div>)* relying party (RP)-initiated logout. This option invalidates access tokens, refresh tokens, and ID tokens associated with the session. When selected, PingOne doesn't send SAML 2.0 single logout requests to SAML identity providers or applications.

     Learn more in the [OIDC RP-Initiated Logout 1.0 documentation](https://openid.net/specs/openid-connect-rpinitiated-1_0.html).

   * **SAML 2.0 Single Logout**: Initiate SAML 2.0 single logout when the user signs off from the application portal. Access tokens, refresh tokens, and ID tokens obtained during the session remain valid until they expire or are revoked.

4. Click **Save**.