With this experience, you have one-click access to:

  • Administrative consoles for your Ping products and PingOne services
  • Documentation, APIapplication programming interface (API) A specification of interactions available for building software to access an application or service., code examples, data sheets, and videos for each product and service
  • Interactive wizards that make it easy to build custom solutions and configure the Ping platform for any cloud environment scenario

To access the PingOne portal, sign on to your account from either pingidentity.com or support.pingidentity.com, and complete a few simple steps. See Accessing the admin console home page for details.

Your Environments home page

On the Your Environments home page, you see the environments to which you have access and the products and services each contains. If you have an Organization admin role, you'll see all of the environments in your organization, as shown in this example.

A screen capture of the environments home page, which shows your environments and the products and services each contains.

To access the environment home page for a particular product or service, hover over the icon for that product or service. If the icon turns into a rocket, click it. Clicking the rocket takes you to the administrative console for that service.


If the icon doesn't turn into a rocket, the product or service hasn't been set up.

When you select an environment, the dashboard for that environment opens.

Source environments

In PingOne, every identity resides in a single source environment, the environment where the identity exists or was created. For example, if you create an identity in the Administrators environment, then the Administrators environment is that identity’s source environment.

For most cases, you should create all administrator identities in the Administrators environment to make it easier to manage them and to help prevent privilege escalation.


Identities don't have to reside in the same environments that they have access to, and you can manage these identities best from one Administrators environment.

End users and customers should reside in a separate environment from your administrator identities.

In some scenarios, you might not have admin access to your identity’s source environment (where your identity resides). In this case, your source environment is different from the environment you can work in, but you only authenticate to your source environment.

Administrators of admin identities, for example, are the only users who have access to their identity’s source environment to manage other admins and their roles. Other types of admins do not have access to their source environment.

Different admins could have different roles that determine what that identity has access to and where. A role has two components:

  • A set of permissions
  • The level for those permissions, such as environment, population, or organization

The level at which a role is assigned determines the environments your role has access to in the admin console while permissions determine what actions you can take. PingOne includes various roles with different applicable levels for each role. For more information, see Roles.

As a PingOne administrator, you can have multiple administrator identities across multiple environments in a single organization, across different organizations, or a combination of both.

A diagram showing an administrator with access to three environments: Administrators, Test, and Production. The Administrators environment is the source environment.

For some complex use cases, you might need multiple administrator identities to configure multiple organizations. An example use case is a contractor working with more than one company to configure environments. In this scenario, the contractor would need an administrator identity in each company’s organization.


You cannot have multiples of the same identity in a single environment. For these complex use cases, those identities must be created in multiple environments.

If you have multiple administrator identities associated with the same email address, you can select which organization you want to authenticate to after signing on. You’ll need to choose the identity with the right permissions based on what actions you intend to take.

A diagram showing an administrator with two PingOne identities and the environments in each organization.

Environment dashboards

Each dashboard provides:

  • A list of the products and services included in the environment
  • A graph showing the activity that has occurred within the environment (if the environment contains PingOne services)
  • Links to documentation, APIs, and code examples for each product and service in the environment

The menu options on the left side of the page vary depending on which products and services are included in the environment.

In the following example, you see all of the services and most of the top-level menus.

A screen capture of an environment dashboard that provides an overview of the activity within the environment.

The following list explains all possible menus:

This menu provides access to the dashboards for the services in the environment. You can also use this menu to set up alerts and establish auditing parameters.

See Monitoring for details.

Update information about the users who have access to this environment using this menu. You can assign roles and attributes to users and add users to groups and populations, which you manage in PingOne.

See Directory for details.

Use this menu to manage your connections to applications and resources, and access the Application Portal and Application Catalog.

See Applications for details.

Use this menu to manage your connections to identity providers, Ping products, identity stores, gateways, and items used to define these connections.

See Integrations for details.

User Experience
Use this menu to manage your end users' experiences. Set up notification policies, and define the look and feel of the experience by modifying branding and themes, the self-service experience, notification templates, agreements, forms, and languages used.

See User Experience for details.

If you have a license for PingOne DaVinci, you can launch the DaVinci console from this menu option. DaVinci enables you to build, test, and optimize identity experiences using a drag-and-drop interface and no-code orchestration to weave together Ping identity services and capabilities.

See Introduction to PingOne DaVinci for details.

Manage your authentication, password, MFA, and FIDO policies from this menu. Additionally, access and configure your MFA settings.

See Authentication for details.

Threat Protection
Use machine learning and analytics to detect malicious activity with PingOne Protect, which is accessible through this menu.

See Getting up and running for details.

Identity Verification
Enable secure user verification based on a government-issued document, live face capture (a selfie), and voice biometrics, ensuring users are who they claim to be with PingOne Verify, which is accessible through this menu.

See Introduction to PingOne Verify for details.

Digital Credentials
Allow issuers to create verifiable credentials that can be sent to a compatible wallet app with PingOne Credentials, which is accessible through this menu.

See Introduction to PingOne Credentials for details.

Control what end users can see and do inside of applications and APIs with PingOne Authorize, which is accessible through this menu.

See Introduction to Authorization for details.

Use this menu to manage your current environment. You can modify the environment properties, such as the name, description, license, and environment type. You can also manage certificates and key pairs, custom domains, and your organization's SMTP server.

More information

For information about the PingOne APIs, see PingOne Platform API Reference.

For information about configuring applications, see Editing an application.

For information about authorization flows, see Authorization flow by grant type, OpenID Connect/OAuth 2, and Flows.