Populations
A population defines a set of users and can help you make user management simple.
For example, you can create a population for similar types of users, such as those in a particular region or job function, and assign those users a unique password policy.
All users are assigned to a population, and you must have at least one population before you can create users. You can move individual users to a different population, but an individual user can’t belong to more than one population simultaneously.
To work with populations, see Managing populations.
Default populations
You can configure any population as the default population. When creating a user through the console or API, PingOne will add the user to the default population unless you specify a population. For more information, see Adding a population.
Roles and populations
You can assign administrator roles for managing populations. For example, you can give an administrator user the Identity Admin role for a particular population so that the administrator can manage identities in that population but not in other populations. For more information, see Administrator Roles.