SCIM user provisioning seat_type mapping
As part of the Mitti rebrand, seat_type mapping examples were updated to the mitti:2.0 namespace. The API doesn’t support mitti:2.0 for this attribute yet, so the mapping was silently ignored and the user was provisioned onto a full seat instead. This corrects the Microsoft Entra ID and Okta examples back to the safetyculture:2.0 namespace.
Developer impact: Any SCIM configuration mapping seat_type through the mitti:2.0 namespace has been provisioning every user as a full seat regardless of the intended seat type, which may have caused unexpected full-seat consumption or billing.
Action required: Update your seat_type attribute mapping to useurn:ietf:params:scim:schemas:extension:safetyculture:2.0:seat_type (Entra ID) orurn:ietf:params:scim:schemas:extension:safetyculture:2.0 with external name seat_type (OOkta). No other SCIM mapping needs to change.