Space Developer Role Assignment
The concept name was not provided (marked as "undefined"), and the supplied source snippets do not contain enough substantive content — only tutorial and page titles are visible, with no descriptive body text — to accurately define a specific SAP developer concept. A reliable, source-grounded definition cannot be written without either a valid concept name or readable source content.
Tutorials that teach this
- Tutorial Managing Space Members
- Tutorial Create Users with Suitable Roles to Build Your Add-on Product
- Tutorial Configure Users and Product Registration to Facilitate Add-On Build
- Tutorial SAP HANA - Create a Space in XS Advanced
- Tutorial Enable an Add-on Product for SaaS Subscription With Standard Configuration Using the Maintain Solution Application
- Tutorial SaaS Enable Your Add-On Product With Standard Configuration Using The Maintain Solution Application.
Docs explaining this concept
Prerequisites
- Concept Cloud Foundry Space Developer Role The concept name was not provided, and the available source snippets cover a range of distinct SAP BTP topics — including Cloud Foundry spaces, route mapping, application restaging, audit log retrieval, and deployment service integration — without a shared concept that can be reliably identified and defined. A meaningful, source-grounded definition cannot be produced without knowing which specific concept to define.
- 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 Cloud Foundry Spaces and Subaccounts The concept name is not defined in the provided sources, and the available snippets cover distinct topics — such as [creating routes](https://help.sap.com/docs/btp/sap-business-technology-platform/9fddeea396b34b528bc8d286f3d5d9cf?locale=en-US&state=PRODUCTION&version=Cloud), [managing Cloud Foundry spaces](https://help.sap.com/docs/btp/sap-business-technology-platform/5209d55d8dd84228897112b0655d999b?locale=en-US&state=PRODUCTION&version=Cloud), and creating service keys — without a shared concept tying them together. Because the concept to be defined is explicitly marked as "undefined" and no single coherent concept can be grounded solely in the provided sources, a reliable definition cannot be produced.
- Concept Role-Based Access Control The concept submitted is **undefined**, so no specific SAP developer concept was provided to define. Based on the available sources, the closest identifiable topic is **Identity and Access Management (IAM)** on SAP Business Technology Platform. [Identity and Access Management (IAM)](https://help.sap.com/docs/btp/sap-business-technology-platform/f25f9108740442c3804370f2d88a9bdd?locale=en-US&state=PRODUCTION&version=Cloud) enables developers to control who can access applications and what actions they are permitted to perform. The [SAP Authorization and Trust Management Service](https://help.sap.com/docs/btp/sap-business-technology-platform/649961f8d4ad463daca33b3a20deba4c?locale=en-US&state=PRODUCTION&version=Cloud) is a core component of this, allowing developers to manage user authorizations and establish trust with identity providers in the Cloud Foundry environment. Developers use these capabilities to secure applications by defining roles, assigning permissions, and controlling access at both the organization and application level.