Once multiple applications start provisioning groups into the Identity Directory, administrators face a common challenge: How do you tell where groups come from?
In November 2026, SAP Cloud Identity Services introduced the application-level group prefix. Prefixes can now be configured directly on an application in the SCI administration console, in addition to being defined on the provisioning system. This is primarily intended for SAP-managed provisioning scenarios, where the provisioning system configuration is not visible to administrators.
While the new feature gives administrators more flexibility where prefixes are configured, it also raises the question: When should you use a prefix, when should you use application ID, and when should you use both?
Two mechanisms. Multiple configuration points. Similar goals, but different outcomes.
Let's look at how they differ and how to choose the right approach.
To illustrate the differences, we'll start with two source systems, each configured to provision one group to the Identity Directory:
- SAP Integrated Business Planning (IBP): IPS_TEST_ROLE_1
- SAP Field Service Management (FSM): Test_Group__SECOND-COMPANY
The Starting Point: No Distinction
In this case, no special configuration is applied. Neither group prefixes nor application IDs are configured in the provisioning systems using the corresponding properties:
- fsm.group.prefix=<prefix> and ibp.group.prefix=<prefix>
- ips.application.id=<application_ID>.
As expected, both groups arrive in the Identity Directory with their original display names. Nothing in the group name indicates whether it comes from FSM or IBP.
The Classic Approach: Group Prefixes
On the provisioning system (Properties tab)
This option is intended for customer-managed provisioning scenarios. In the following example, the properties are configured for the FSM and IBP source systems:
- fsm.group.prefix=FSM_
- ibp.group.prefix=IBP_
Following a provisioning job, the result is straightforward. The origin of each group can be easily identified by its prefix.
On the application (Provisioning tab)
This option is introduced primarily for customers using SAP-managed provisioning, where the provisioning systems are configured and maintained by SAP and are not visible in the administration UI.
In this scenario, administrators cannot configure a prefix through the provisioning system's Properties tab. Instead, the Group Prefix field under Applications & Resources → [Your Application] → Provisioning provides an alternative way to control group display names.
If a group prefix is configured at both levels, the application-level prefix takes priority.
In the example below, the provisioning system uses FSM_ , but the provisioned group receives FSM_DEV_ from the application.
The new feature is not limited to SAP-managed provisioning. Customers using customer-managed provisioning can also configure the group prefix from the application. For this to work, the application ID must be set for the ips.application.id property on the provisioning system from which groups are read, and a read job must be run on that system after the application-level prefix is configured.
Setting the application ID property actually turns the groups into application-specific groups. For more information, see The Modern Approach section below.
Use group prefixes when visibility is your primary goal. They can also control which groups are provisioned to a target system. If a prefix is configured on the target, only groups with that prefix are provisioned.
The Modern Approach: Application-Specific Groups
Instead of relying on a naming convention, this approach links groups directly to their source application by attaching the application ID as a group attribute.
When the ips.application.id property is configured on a source system, every provisioned group is associated with the ID of the corresponding application. In the Identity Directory, this association is resolved to the application name and displayed in the Application column under Users & Authorizations → Groups.
The biggest advantage of this approach is the event-driven provisioning. Once groups are associated with an application, changes to their membership or attributes automatically trigger provisioning to target systems, provided that Central Store-Based Provisioning is enabled for the application. No manual execution or scheduled provisioning job is required.
In our test scenario, ips.application.id was configured along with the existing prefixes. The groups retain their prefix and are linked to the application.
Use application-specific groups when automation and real-time provisioning is your primary goal. Group prefixes have no event-driven capabilities and provisioning only happens when a job runs.
Know the Name. Know the Source. Know the Behavior.
So, when the next hundred groups land in your Identity Directory, you won't just know their names. You'll know where they come from, how they are managed, and how they move across your landscape.
A simple rule of thumb: Use group prefixes for visibility. Use application-specific groups for automation. Use both when you want the best of both worlds.
