---
title: Access services through scopes and roles
description: Explains how PingOne self-management scopes and administrator role assignments determine access to platform resources
component: pingone-api
page_id: pingone-api:foundations:pingone-roles-scopes-and-permissions/access-services-through-scopes-and-roles/index
canonical_url: https://developer.pingidentity.com/pingone-api/foundations/pingone-roles-scopes-and-permissions/access-services-through-scopes-and-roles/index.html
llms_txt: https://developer.pingidentity.com/pingone-api/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-08-11
---

# Access services through scopes and roles

User applications rely on self-management scopes to grant users access to a subset of PingOne resources. For more information about scopes, refer to [Resource scopes](../../../platform/resources/resource-scopes/index.html). Conversely, administrator applications use role assignments to determine the actions a user or client can perform. For more information about roles, refer to [Roles](../../../platform/roles/index.html) in the *PingOne Platform APIs*.

For detailed information about scopes, refer to the following topics:

* [PingOne self-management scopes](pingone-self-management-scopes.html)

* [OpenID Connect (OIDC) scopes](openid-connect-oidc-scopes.html)

* [Custom scopes](custom-scopes.html)