Scopes specify what access privileges are being requested as part of the authorization. For example, the
If you need scopes in addition to the reserved scopes provided, you can create them. Custom scopes can have corresponding claims that tie them to some sort of user information.
In the Admin Console, navigate to Security > API.
On the Authorization Servers tab, select the name of the Authorization Server, and then select Scopes.
Select Scopes, and then Add Scope.
Enter a Name, Display phrase, and Description.
Note: The Display phrase is what the user sees in the Consent dialog box.
Select Require user consent for this scope to require that a user grant consent for the scope.
Note: You can configure individual clients to ignore this setting and skip consent.
Select Set as a default scope if you want to allow Okta to grant authorization requests to apps that don't specify scopes on an authorization request. If the client omits the scope parameter in an authorization request, Okta returns all default scopes in the access token that are permitted by the access policy rule.
Select Include in public metadata if you want the scope to be publicly discoverable.
Scopes that you add are referenced by the Claims dialog box.
If you set a scope as a default scope, then it is included by default in any tokens that are created. Depending on which flow you are using, it might also allow you to exclude the
scope parameter from your token request.