Role Collection Assignment
The concept name is not defined in the provided sources, so a precise definition cannot be grounded in the available material. The sources cover related SAP BTP topics such as managing users and role collections and assigning permissions for SAP Business Application Studio, but no specific concept is identified for definition.
Tutorials that teach this
- Tutorial Integrate Your UI Integration Card from the Content Package Into Your Site
- Tutorial Create a Content Provider in Launchpad Service
- Tutorial Start Using SAP HANA Cloud Free Tier Service in SAP BTP Cockpit
- Tutorial Set Up SAP Build Work Zone, standard edition Using the Free Tier Model for SAP BTP
- Tutorial Establish Trust Configuration between SAP S/4HANA Cloud, public edition and SAP BTP Subaccount
- Tutorial Subscribe to SAP Build Process Automation
- Tutorial Assign the User Roles
- Tutorial Establish Trust Configuration between SAP S/4HANA On-premise and SAP BTP
- Tutorial Create a Content Provider in Launchpad Service
- Tutorial Test CAP Service and its Destination
- Tutorial Create a Cloud Foundry Subaccount with a Booster
- Tutorial Configure SAP Build Work Zone, Standard Edition
- Tutorial Getting Started with SAP Document Management Mobile Application
Docs explaining this concept
- Doc Add Members to Your Global Account
- Doc Assigning Permissions for SAP Business Application Studio
- Doc Assigning Role Collections to Users or User Groups
- Doc Creating an Identity Provider Group for Developers
- Doc Delete Users from Role Collections
- Doc Find Users and Their Role Collection Assignments
- Doc Initial User Onboarding
- Doc Managing Users and Their Authorizations Using the btp CLI
Prerequisites
- Concept BTP Cockpit Administration The concept name was not provided, so a precise definition cannot be produced. Based on the available sources, the content relates to SAP Business Technology Platform (SAP BTP) account administration — covering tasks such as [managing subaccounts using the cockpit](https://help.sap.com/docs/btp/sap-business-technology-platform/55d0b6d8b96846b8ae93b85194df0944?locale=en-US&state=PRODUCTION&version=Cloud), configuring entitlements and quotas for directories, administering orgs and spaces in the [Cloud Foundry environment](https://help.sap.com/docs/btp/sap-business-technology-platform/c4c25cc63ac845779f76202360f98694?locale=en-US&state=PRODUCTION&version=Cloud), and managing authentication, authorization, and roles. Developers and administrators use these capabilities to structure their global account hierarchy, control access through roles, and allocate service entitlements and quotas across subaccounts and directories.
- Concept SAP BTP Subaccount Cockpit Overview The concept provided is **undefined** — no valid concept name was supplied, and the available source snippets cover a range of loosely related SAP BTP topics (such as accessing SAP Web IDE, managing org members, resource providers, and service availability) without converging on a single, identifiable concept. A meaningful definition cannot be accurately or responsibly written without a clearly stated concept to define. Please provide a specific concept name (for example, "Resource Provider," "Org Member," or "Service Instance") so a grounded definition can be produced.
- Concept CAP Integration with Cloud Foundry on SAP BTP The **SAP Cloud Application Programming Model (CAP)** is a framework of languages, libraries, and tools for building enterprise-grade services and applications on [SAP Business Technology Platform](https://help.sap.com/docs/btp/sap-business-technology-platform/00823f91779d4d42aa29a498e0535cdf?locale=en-US&state=PRODUCTION&version=Cloud). Developers use it to define data models, services, and business logic that can be deployed to targets such as SAP HANA Cloud or SAP BTP. CAP supports both Node.js and Java runtimes, and integrates with tools like SAP Business Application Studio and SAP Continuous Integration and Delivery to streamline the full development lifecycle.
- Concept BTP Destination Configuration for API Testing A **destination** in SAP Business Technology Platform (SAP BTP) is a configuration object that defines the connection parameters needed to enable communication between an application and a remote service or system. Developers create and manage destinations in the [SAP BTP cockpit](https://help.sap.com/docs/btp/sap-business-technology-platform/eb1d0a34b7c1411ba18401c07203020a?locale=en-US&state=PRODUCTION&version=Cloud) to connect to external resources such as on-premise systems, OData services, or other subaccounts. Destinations can be configured to support various authentication methods — such as SAML assertion authentication — and connectivity scenarios, including [on-premise connectivity via HTTP or RFC](https://help.sap.com/docs/btp/sap-business-technology-platform/9b6510edf4d844a28f022b3db41f3202?locale=en-US&state=PRODUCTION&version=Cloud).
- Concept 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.
- Concept BTP Role Collection Assignment The provided sources do not contain sufficient information to write a grounded definition for an **undefined** concept. Please provide a valid concept name and relevant source snippets so an accurate, source-grounded definition can be written.
- Concept SAP BTP Business Roles A **Business Catalog** is a grouping of related apps, services, and authorizations that can be assigned to business roles in SAP BTP. Developers and administrators use business catalogs to control which capabilities and tasks — such as [development tasks](https://help.sap.com/docs/btp/sap-business-technology-platform/a9f42789fd5743edbf1de20d6c571cb2?locale=en-US&state=PRODUCTION&version=Cloud) or [communication management](https://help.sap.com/docs/btp/sap-business-technology-platform/c26a67fb8bdc46ab9a7d6dc621fde366?locale=en-US&state=PRODUCTION&version=Cloud) — are accessible to users assigned a given business role. Deprecated business catalogs are those that have been replaced and are no longer recommended for use, and administrators are expected to migrate away from them.
- Concept SAP BTP Service Instance and Binding Creation The provided sources do not contain sufficient information to write a grounded definition for an **undefined** concept. Source [S1] references a troubleshooting scenario involving the SAP Service Manager binding on SAP BTP, while the remaining sources ([S2]–[S8]) are tutorial titles only, with no descriptive content. Without a clearly identified concept name and supporting source content, a factually grounded definition cannot be produced.
- Concept SAP BTP Subaccount and Entitlement Setup The provided sources do not contain sufficient information to define this concept. The concept name is "undefined" and none of the source snippets supply grounded content that could be used to write an accurate, sourced definition.
- Concept SAP BTP ABAP Environment (Steampunk) The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a concept by that name. Based on the available source snippets — which cover topics such as the [XCO Library](https://help.sap.com/docs/btp/sap-business-technology-platform/c154dffe892b4d9ea4566722f0bcd5f1?locale=en-US&state=PRODUCTION&version=Cloud), ATC configurations, abapGit, and the Cloud Connector — no grounded definition can be written for an "undefined" concept. Please provide a valid SAP developer concept name so an accurate, source-grounded definition can be produced.
- Concept CAP Cloud Deployment The concept name provided is "undefined," which does not correspond to a identifiable SAP developer concept supported by the provided source snippets. The sources reference topics such as Node.js business application development on SAP BTP, CAP services, and deployments to Cloud Foundry and Kyma runtimes, but none of them define or describe a concept called "undefined." A valid concept name is required to produce an accurate definition grounded in the provided sources.
- Concept SAP Build Work Zone configuration The provided sources do not contain enough information to define this concept, as the concept name is listed as "undefined" and the source snippets do not converge on a single, clearly identifiable SAP developer concept. Please provide a valid concept name or additional source content to generate an accurate definition.
- Concept Subaccount Management The concept name was not provided, but based on the sources, the subject appears to be **SAP BTP Subaccounts**. A subaccount is a structural unit within a global account on SAP Business Technology Platform (SAP BTP) that developers and administrators use to organize resources, environments, and users. Using the [SAP BTP cockpit](https://help.sap.com/docs/btp/sap-business-technology-platform/55d0b6d8b96846b8ae93b85194df0944?locale=en-US&state=PRODUCTION&version=Cloud), you can manage subaccounts by configuring [entitlements and quotas](https://help.sap.com/docs/btp/sap-business-technology-platform/5ba357b4fa1e4de4b9fcc4ae771609da?locale=en-US&state=PRODUCTION&version=Cloud), enabling environments such as Cloud Foundry, adding users, and viewing usage analytics. Subaccounts support multi-environment setups, allowing developers to enable or create environment instances and create orgs in order to use Cloud Foundry within a subaccount.
- Concept SAP BTP SaaS Application Subscription The provided sources do not contain enough grounded information to define a specific SAP developer concept, as the concept name is listed as "undefined." Based on the available source snippets, the content relates to subscribing to SaaS solutions and managing consumer subaccounts on [SAP Business Technology Platform](https://help.sap.com/docs/btp/sap-business-technology-platform/975bd3e54cbe4e52af346740658d1a4a?locale=en-US&state=PRODUCTION&version=Cloud), but no single named concept can be accurately defined without additional context.
- Concept SAP BTP Account Model (Global Accounts, Subaccounts, Spaces) The concept name provided is "undefined," which does not correspond to a identifiable SAP developer concept. Based on the available sources — which cover topics such as global account administration, subaccount creation, the Cloud Foundry environment, and SAP BTP account management — there is insufficient information to produce a grounded definition for a concept labeled "undefined." Please provide a valid SAP concept name so an accurate and source-grounded definition can be written.
- Concept SAP Fiori Launchpad Administration The concept provided is **undefined** — no specific SAP developer concept was supplied for definition. Based on the available sources, these snippets cover topics such as maintaining business roles and business users, creating communication arrangements in the ABAP environment, developing and deploying [SAP Fiori applications](https://help.sap.com/docs/btp/sap-business-technology-platform/97df0a6022a14ce180440d6fae1dd3cd?locale=en-US&state=PRODUCTION&version=Cloud) using tools like Visual Studio Code and SAP Business Application Studio, and [providing access to SAP Fiori applications](https://help.sap.com/docs/btp/sap-business-technology-platform/b569abb158934306a65f3eb38f86ffba?locale=en-US&state=PRODUCTION&version=Cloud) through role assignments. Please supply a specific concept name so an accurate and grounded definition can be written.
- Concept Identity and Access Management on SAP BTP The concept name was not provided and cannot be determined from the available source snippets, which cover [Identity and Access Management (IAM) on SAP BTP](https://help.sap.com/docs/btp/sap-business-technology-platform/5b6290112008456b9e9400faebb8cd33?locale=en-US&state=PRODUCTION&version=Cloud) and related topics such as business user management and role assignment. Please supply a valid concept name so that an accurate, source-grounded definition can be written.
- 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 SAP BTP trial and free tier account setup The concept name was not provided (marked as "undefined"), and the supplied sources do not converge on a single, clearly identifiable SAP developer concept. The sources reference a variety of topics — [Trial Accounts and Free Tier](https://help.sap.com/docs/btp/sap-business-technology-platform/046f127f2a614438b616ccfc575fdb16?locale=en-US&state=PRODUCTION&version=Cloud) and [Getting Started with SAP BTP](https://help.sap.com/docs/btp/sap-business-technology-platform/144e1733d0d64d58a7176e817fa6aeb3?locale=en-US&state=PRODUCTION&version=Cloud) — without a shared concept to define. A valid concept name is required to produce an accurate, grounded definition.
- Concept CAP Framework (Cloud Application Programming Model) The concept name was not provided, so a precise definition cannot be determined. Based on the available sources, [SAP Business Technology Platform (SAP BTP)](https://help.sap.com/docs/btp/sap-business-technology-platform/c2fec62b49fa43b8bd945c85ecc2e5bd?locale=en-US&state=PRODUCTION&version=Cloud) is a platform on which developers build and run business applications, choosing from development environments, tools, APIs, and [programming models](https://help.sap.com/docs/btp/sap-business-technology-platform/042061da2e964b7eab3c7ec2a5cc7ece?locale=en-US&state=PRODUCTION&version=Cloud) such as ABAP Cloud and the SAP Cloud Application Programming Model (CAP). Developers use it to create full-stack business applications, following best practices to select the approach that best suits their requirements.
- Concept BTP Subaccount Security Tab The provided sources do not contain sufficient grounded content to write a reliable 2–4 sentence definition for an **undefined** concept. The snippets reference tutorial titles and a troubleshooting symptom, but none supply substantive explanatory text about a clearly named concept. Please provide a valid concept name and richer source snippets so an accurate, grounded definition can be written.
- Concept Identity Provider (IdP) Trust Configuration The concept provided is **undefined**, and the available source snippets do not contain sufficient grounded content to produce a reliable, accurate definition. All sources relate to trust configuration, SAP BTP setup tutorials, or SAP Document AI — none of which define a specific named developer concept. Without a valid concept name and supporting source material, a documentation-quality definition cannot be responsibly generated.
- Concept BTP Identity and Access Management SAP BTP Identity and Access Management (IAM) provides mechanisms for controlling who can access resources and what actions they are permitted to perform on SAP Business Technology Platform. Developers and administrators use it to manage business user groups, including the ability to [import and export business user group configurations](https://help.sap.com/docs/btp/sap-business-technology-platform/c3d16efe55894fe1ae76b2e6fe90ac15?locale=en-US&state=PRODUCTION&version=Cloud) to streamline the administration of access across environments.
- Concept BTP Authorization Development for Business Users The provided sources do not contain sufficient content to define a specific SAP developer concept, as the source snippets only include page titles and brief introductory fragments without substantive explanatory detail. A accurate, source-grounded definition cannot be produced from the available material.
- Concept SAP BTP Cloud Foundry Deployment via MTA The concept provided is `undefined` and the supplied sources do not contain a named or describable concept to define. A meaningful reference definition cannot be written without a valid concept name grounded in the provided source snippets.
- Concept Role Collections and Authorization Artifacts The concept name provided is "undefined," and the available source snippets do not contain sufficient grounded information to define a specific, identifiable SAP developer concept. A meaningful definition cannot be written without a valid concept name and supporting source content.
- Concept SAP BTP Cockpit Security Configuration The concept name was not provided, and the available source snippets cover several distinct SAP BTP topics — including trusted identity providers, role collections, application troubleshooting, and token policies — without describing a single, identifiable concept. A accurate and grounded definition cannot be produced without knowing which concept to define.
- Concept BTP Business Users A **business user** in SAP BTP is a person whose user account enables them to log on to SAP BTP, access subaccounts, and use applications. As described in the [Business Users](https://help.sap.com/docs/btp/sap-business-technology-platform/3a3f0e1eca5f4962bc7ff436424cc048?locale=en-US&state=PRODUCTION&version=Cloud) documentation, these accounts are distinct from other user categories on the platform, each of which serves different purposes and carries different capabilities. Developers and administrators manage business users by assigning roles and, where needed, applying [mass changes](https://help.sap.com/docs/btp/sap-business-technology-platform/49f24c7dd980412094f5e993e55f2f3b?locale=en-US&state=PRODUCTION&version=Cloud) to update multiple user records at once.
- Concept SAP BTP Multi-Runtime Deployment (Cloud Foundry & Kyma) The concept name provided is "undefined," which does not correspond to a identifiable SAP developer concept supported by the provided source snippets. The sources cover topics such as namespace-level and instance-level mapping with SAP Service Manager, the btp CLI, SAP Event Mesh, and SAP S/4HANA Cloud Extensibility — none of which define a concept called "undefined." A meaningful definition cannot be written without a valid concept name grounded in the available sources.
- Concept BTP Authorization and Role Assignment The concept name was not provided and the supplied sources do not contain enough specific, attributable information to produce a grounded, accurate definition. A valid concept name and sufficient source content are required to generate a reliable reference definition.
- Concept SAP BTP Role Collections A **role collection** in SAP Business Technology Platform is a grouping of roles that a developer or administrator assembles to define a set of authorizations. Developers use role collections to organize and assign access rights to users by [assigning users to role collections](https://help.sap.com/docs/btp/sap-business-technology-platform/c5766765bda74ad59fe656977c8fa4d6?locale=en-US&state=PRODUCTION&version=Cloud) or by [mapping role collections](https://help.sap.com/docs/btp/sap-business-technology-platform/9e1bf57130ef466e8017eab298b40e5e?locale=en-US&state=PRODUCTION&version=Cloud) to user groups or attributes from a trusted identity provider. Role collections can be created from scratch or by copying existing ones, and roles built from application role templates can be added to them to control access within SAP BTP subaccounts.
- Concept Trust configuration between SAP Cloud Identity Services and SAP BTP The provided sources do not contain enough information to define a specific, named SAP developer concept, as the concept supplied is "undefined." The sources relate to custom identity providers on SAP BTP, but without a concrete concept name or sufficient descriptive snippets, a grounded definition cannot be accurately composed.
- Concept SAP BTP Cockpit Destination Configuration The concept name was not provided and the supplied sources do not contain enough detail to identify or define a specific SAP developer concept. The sources reference SAP BTP Destination Service, client certificate authentication, and S/4HANA connectivity tutorials, but without a concept name or substantive source content, a grounded definition cannot be written.
- Concept SAP BTP Cockpit User Management The concept name is not defined in the provided sources, and the available source snippet does not contain enough detail to ground a complete, accurate definition. Without a clearly identified concept and sufficient supporting source content, a documentation-quality definition cannot be responsibly written.
- Concept Kyma Runtime deployment The concept name is undefined and cannot be determined from the provided source snippets. The sources reference SAP BTP Kyma runtime, Docker containers, and related deployment tutorials, but do not define a specific named concept that can be documented. A meaningful definition cannot be written without a valid concept name grounded in the sources.
- Concept Business Users on SAP BTP The concept name is missing or undefined, and the single source snippet provided describes **Business Users** — people who use applications deployed to SAP BTP. Without a clearly defined concept to document, a precise and grounded definition cannot be written. Please provide a valid concept name to generate the reference definition.