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.
Tutorials that teach this
Docs explaining this concept
- Doc (Experimental) Exporting MTA Operation Logs to SAP Cloud Logging
- Doc Add Space Members
- Doc Add Space Members Using the Cloud Foundry Command Line Interface
- Doc Audit Log Retrieval API Usage for Subaccounts in the Cloud Foundry Environment
- Doc Bind an Application to a Service
- Doc Create Spaces
- Doc Deploy an Application
- Doc Edit Space Members
Prerequisites
- Concept Cloud Foundry Roles and Authorization In the Cloud Foundry environment on SAP BTP, [roles determine which features users can access and which actions they can perform](https://help.sap.com/docs/btp/sap-business-technology-platform/09076385086b4da3bd1808d5ef572862?locale=en-US&state=PRODUCTION&version=Cloud) at the org and space levels. Developers use these roles to control authorization by assigning or removing them for org and space members via the SAP BTP cockpit or the Cloud Foundry command line interface. Deleting all roles of an org member removes that member's access entirely, while editing roles allows fine-grained control over what each user can do within a given org or space.
- 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 Environment Instance The concept provided is undefined, and the supplied sources cover general SAP Business Technology Platform (BTP) topics — such as the [Cloud Foundry environment](https://help.sap.com/docs/btp/sap-business-technology-platform/40a8f8f6f1724e0ca0fd2a8777f45504?locale=en-US&state=PRODUCTION&version=Cloud), the ABAP environment, and BTP account setup — without identifying a specific named concept to define. No definition can be accurately produced without a clearly stated concept, as fabricating one would go beyond what the provided sources support.
- Concept SAP BTP Cockpit The concept name was not provided and the supplied source snippets do not define or describe a single, identifiable SAP developer concept — they cover a range of unrelated SAP BTP topics such as Kyma environment setup, Cloud Foundry org deletion, subaccount management, and service instances. A focused definition cannot be grounded solely in these sources without a clearly stated concept to define.
- 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 on SAP BTP The concept name was not provided and the supplied sources — covering MCP Server troubleshooting, FAQs, and the Subscription Management Dashboard for SAP BTP — do not contain sufficient information to define an unnamed or "undefined" concept. A meaningful, source-grounded definition cannot be written without a valid concept name and relevant supporting material.
- Concept Member Management on SAP BTP The concept name is not defined in the provided sources, so a precise definition cannot be grounded. Based on the available sources, [platform users](https://help.sap.com/docs/btp/sap-business-technology-platform/440131674b0147a09e696053a53832d5?locale=en-US&state=PRODUCTION&version=Cloud) on SAP BTP are typically developers, administrators, or operators who deploy, administer, and operate applications and services. [User and member management](https://help.sap.com/docs/btp/sap-business-technology-platform/cc1c676b43904066abb2a4838cbd0c37?locale=en-US&state=PRODUCTION&version=Cloud) on SAP BTP takes place at all levels, from the global account down to subaccounts, allowing administrators to control access across the platform.
Concepts that build on this
- Concept Cloud Foundry Space and Application Events Monitoring
- Concept Space Developer Role Assignment
- Concept SAP Web IDE for SAP HANA
- Concept Application Logs Display Component
- Concept Cloud Foundry Service Bindings
- Concept Org Member Management
- Concept Cloud Foundry Container-to-Container Networking
- Concept Cloud Foundry Routes Management in BTP Cockpit