24 March on TEST on Production 31 MarchRegarding the user import feature, we’ve introduced a new property called hasInactiveSince for customers using the integration API:POST /users/import
This field allows customers to activate or deactivate users through the import flow. The intention is to add a safe control layer so that users are only activated or deactivated when explicitly intended.
Current payload
{ "authConfigId": "ObjectId", "users": [] }
New payload
{ "authConfigId": "ObjectId", "hasInactiveSince": true, "users": [] }
The default value of hasInactiveSince is false.
- When hasInactiveSince = false:
- The import API will ignore the inactiveSince field during updates. This means that even if inactiveSince is included in the user payload, it will be skipped entirely.
- When hasInactiveSince = true:
- The import API will take the inactiveSince value into account:
- If inactiveSince is undefined or null, the user will be treated as active. If the user was previously deactivated, they will be reactivated.
- If inactiveSince contains a valid timestamp, the user will remain deactivated if already inactive.
- If the user is currently active, they will be deactivated using the provided timestamp value.
- The import API will take the inactiveSince value into account:
This approach ensures that activation and deactivation through user import only happen when explicitly enabled.