When provisioning groups via SCIM, Firstup applies internal normalization rules to ensure group identifiers remain consistent. These rules differ from how group names behave when created manually in Studio.
SCIM group names (not display names) are normalized internally before storage. Normalization includes:
- Converting to lowercase
- Converting punctuation characters such as hyphens (-) and underscores (_) into a uniform equivalent
- Stripping other characters that do not affect uniqueness
If two display names normalize to the same internal value, the second group creation request will fail with a 409 uniqueness violation, even if the display names appear different.
In Studio, similar names may be allowed because Studio automatically appends suffixes to ensure uniqueness. SCIM does not modify or mutate names to make them unique.
Deleting a SCIM-provisioned group in Firstup places it into an archived state rather than permanently removing it.
If a SCIM client sends a POST request to create a group whose normalized name matches an archived SCIM group, the existing archived group will be re-activated, not duplicated.
This is expected behavior and helps ensure identity systems remain the source of truth.
Creating a New Group With the Same Normalized Name
If you need to create a new group with a name that conflicts with an existing archived group:
- Rename the existing group (via SCIM PUT or from the Firstup UI).
- Delete the renamed group.
- POST the new group.
If the identity provider does not allow renaming deleted groups (e.g., some Microsoft Entra cases), this restriction may require adjusting the naming scheme to avoid collisions.