Using the PingOne console, configure and manage your PingOne organization. The organization is the top-level identifier and defines your entire enterprise within the platform.

The following image shows the home page for an environment.

A screen capture showing the PingOne home screen

Within the organization are one or more environments. Environments contain populations, which provide the structure to manage groups of similar users within the environment so that your customers, employees, and partners can use PingOne to access the applications that they are authorized to use.

Environments encompass:

A population defines a set of users, similar to an organizational unit (OU). In a given environment, you can use populations to simplify the management of users. For example, you can create a population for similar types of users and apply a password policy to that population. You must create at least one population before you can create users. For more information, see Populations.

An individual user can't belong to more than one population at the same time, but can be moved to a different population.

A user is a unique identity that interacts with the applications and services in the environment to which the user is assigned. An identity is the full representation of a user profile, including relationships, roles, and attributes. Users are associated with populations instead of being defined within a population. For more information, see Users.

Application resources define the connection between PingOne and the actual application, also known as a client connection. Connections to external resources use open standards protocols. Client connections define the configuration for OpenID Connect (OIDC) and OAuth clients.

Application grants describe which grant type the application can request. Scopes define the permissions for the application. For more information, see Applications.

Activities are collections of user-activity information, such as sign-on attempts, password reset attempts, and total active user counts. This audit data can be exported, reported on, or streamed out to customer SIEM (Security Information and Event Management) solutions. For more information, see Audit.
Branding and images
User interface branding elements are defined in the branding resource. This resource contains configuration properties for customizable elements of the PingOne user interface. All end user interfaces are branded according to the theme defined in the branding resource. For more information, see Branding and themes.
Password policies
Password policies define the strength and complexity requirements for a password for users within an environment. For more information, see Password policies.

About Organizations

The PingOne platform uses an organization-based model to define tenant accounts and their related entities. The organization is the top-level identifier. It defines your entire enterprise within the platform. On completion of creating a trial organization, you automatically have:

  • One Trial license.
  • Two environments:
    • Administrators
    • End User Sandbox

    In the PingOne admin console, the environment name appears in the top left corner. You can find the environment ID and other details in Settings > Environment Properties.

  • One population within the Administrators environment named Administrators Population.
  • Two populations within the End User Sandbox environment:
    • Sample Users
    • More Sample Users

    Each population contains 20 users.

  • One admin user with all the roles to manage the organization.

For optimum performance, select the data center closest to your geographic region.

The examples in this topic use the URLs for the North America data center.

If you create your organization using the Europe or Asia Pacific data centers, use the following URLs instead.

UI/Endpoint Type Canada Europe Asia Pacific

Admin console

User self-service

Management API endpoints

Authentication and authorization API endpoints


You can create more Environment Properties, Populations and Users through the UI or API.

For API documentation, see the PingOne Platform API Reference.