Skip to content
Identity and Access Management

04 May 2026

Production release: 04 May 2026
Staging release: 27 April 2026

04 May 2026

Section titled “04 May 2026”

Features

Section titled “Features”

  • Pending Issues of DataRegion Switch Handling Addressed: Resolved issues related to data region switch handling, including filtering of create events and missing fields during data porting.

  • Incremental Capture of New Accounts for EDW Data Product: Ensures that newly created accounts are captured incrementally for downstream consumers.

  • Static Dataset Generation for Existing Accounts: A one-time dataset of the existing account base has been generated for analytical purposes.

  • API for Listing Customer Accounts of Organizations: Introduced an API to list customer accounts of organizations based on account type. GET /organizations/{organizationId}/accounts

  • API for Updating Organization Verification Status: Added an API to update the verification status of customer-to-organization relationships. PUT /organizations/{organizationId}/accounts/{accountId}

  • API for Removing Customer Accounts from Organizations: Introduced an API to remove customer accounts from organizations with proper authorization checks. DELETE /organizations/{organizationId}/accounts/{accountId}

  • API for Adding Customer Accounts to Organizations: Added an API to add customer accounts to organizations with detailed authorization requirements. POST /organizations/{organizationId}/accounts

  • Device Applications Enhanced with Account ID: Device applications now include account ID during creation and updates for better account-device association.

  • Reverse Sync for Specific Device Models: Implemented reverse sync for specific device models to ensure compatibility with legacy systems like WorksManager.

  • Authorization Changes for Blocklisted Devices: Updated authorization for device-related APIs to restrict operations on blocklisted devices.

  • API for Marking Devices as Blocklisted or Stolen: Added an API to mark devices as blocklisted or stolen with detailed validation and authorization rules.

  • GraphQL API for Listing Team Join Requests Across Accounts: Administrators can now list all user join requests across groups and accounts for streamlined approval or rejection.

  • Region-Based User Listing Using mTLS Fetch: Enabled region-based user listing by combining data from multiple regions using mTLS bulk-fetch endpoints.

  • Applications GraphQL Resolvers Added to Groups BLU: Updated Groups BLU handler to resolve applications within the Group type.

  • DataRegion Switch Handling for User Migration: Implemented handling for user data region switching, including deletion and recreation of user data across regions.

  • API for Adding Users to Organizations: Introduced an API to add users directly to organizations, supporting non-hierarchical asynchronous processes.

  • Apollo Lambdas Deployed in Production Mode: Apollo lambdas are now configured to deploy in production mode for enhanced performance and reliability.

  • GraphQL Across Account Changes Validation: Validation implemented for GraphQL changes across accounts to ensure data integrity.

  • Expanded Group Service Layer Method for Request Type: The get_user_ref_from_group method now includes the requestType field in the User-Group relation, improving group management functionality.

Bug Fixes

Section titled “Bug Fixes”

  • SonarQube Critical Issues Resolved in Accounts BLU: Fixed four critical issues identified in SonarQube for the Accounts BLU module.

  • Address Addition Bug Fixed for Accounts: Resolved an issue where adding a new address to an account resulted in a 400 error after updating an existing address.

These updates enhance system functionality, improve user experience, and address critical issues for seamless operations.