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

  • Administrative consoles for your Ping products and PingOne services
  • Documentation, API, 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 scope for those permissions, such as environments, populations, and organizations

Scopes determine 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 scopes 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.