Scopes and Role Templates in SAP BTP
The concept name is not defined and the provided source snippet does not contain enough context to identify or describe a specific SAP developer concept. A valid definition cannot be produced without a named concept and sufficient supporting source material.
Docs explaining this concept
Prerequisites
- Concept Roles in the Cloud Foundry Environment The concept name was not provided, so a precise definition cannot be generated from the available sources. Based on the sources, the closest identifiable concept appears to be a **Cloud Foundry Space** — a logical environment within a Cloud Foundry org on SAP BTP that developers use to deploy and manage applications and services. As described in [Managing Spaces](https://help.sap.com/docs/btp/sap-business-technology-platform/5209d55d8dd84228897112b0655d999b?locale=en-US&state=PRODUCTION&version=Cloud), spaces contain resources such as apps and service instances, and access is controlled by assigning roles to space members. Developers can manage space membership — including adding or removing users and their roles — directly in the SAP BTP cockpit, as outlined in [Delete Space Members](https://help.sap.com/docs/btp/sap-business-technology-platform/78b20cf8ae584498822dbd5c30e75b52?locale=en-US&state=PRODUCTION&version=Cloud).
- Concept Application Security Descriptor File (xs-security.json) The concept name was not provided (marked as "undefined"), and the supplied source snippets cover several distinct topics — including role collections, token policy configuration, redirect URIs, and principal propagation — without a single unifying concept that can be reliably identified and defined. A precise, source-grounded definition cannot be written without knowing which specific concept is intended.