Based on the knowledge sources, scopes in Ory OAuth2 and OpenID Connect are used to specify the level of access a client has to protected resources, and each scope typically maps to a specific set of claims or permissions. The standard OpenID Connect scopes like profile and email are mapped to specific user information (e.g., profile gives access to name, username, website, etc.)[Customize OpenID Connect scope and claims](https://www.ory.sh/docs/oauth2-oidc/openid-connect-claims-scope-custom). There is no mention in the documentation of a built-in mechanism where a custom scope (such as "driver") can automatically inherit or include the claims of another scope (such as "profile"). Scopes are evaluated individually, and the claims included in tokens are determined by the scopes explicitly requested and granted during the consent process. If you want a custom scope like "driver" to provide access to the same information as "profile," you would need to customize the claims mapping logic—potentially using Ory's webhooks or consent UI to add the desired claims when the "driver" scope is present. However, the knowledge sources do not provide explicit instructions or examples for this scenario, so you would need to refer to the documentation on custom claims and consent UI for further guidance[Customize OpenID Connect scope and claims](https://www.ory.sh/docs/oauth2-oidc/openid-connect-claims-scope-custom). In summary: No, there is no automatic inheritance between custom scopes and standard scopes like "profile" in Ory by default. You would need to implement custom logic to achieve this behavior, and the knowledge sources do not provide a direct example of how to do so.