
Corma now integrates with Claap!
Claap is a video recording and meeting notes tool teams use for async communication. You can now:
Collect licenses: centralize Claap users and licenses in Corma, including pending invites
Provisioning & deprovisioning: invite and revoke Claap users directly from Corma

Corma now integrates with Sentry!
Sentry is an error monitoring platform engineering teams use to track and fix bugs. You can now:
Collect licenses: centralize Sentry members in Corma, with their organization role and last activity
Provisioning & deprovisioning: invite and remove members, set or reset their organization role, and add or remove them from Sentry teams, directly from Corma

Corma now integrates with Metabase!
Metabase is a business intelligence tool teams use to explore data and build dashboards. You can now:
Collect licenses: centralize Metabase users in Corma, with their role (Admin or User) and last login
Provisioning & deprovisioning: create and deactivate users, and add or remove them from Metabase groups, directly from Corma

Corma now integrates with Leapsome!
Leapsome is a people management platform for performance reviews, goals and engagement. You can now:
Collect licenses: centralize Leapsome users and seats in Corma
Provisioning & deprovisioning: create and deactivate users, and add them to Leapsome groups, directly from Corma

Corma now integrates with Malibou!
Malibou is a French payroll software for small and medium businesses. You can now:
Identity: collect employees from Malibou and list them in Corma to keep your user directory up to date
Get HR data: enrich user profiles in Corma with manager, team, employment dates and email addresses from Malibou

Slack actions: you can now invite a guest (Slack Enterprise plan), give or remove admin rights, and remove a user from groups.
Workflows have a new trigger, Ticket status updated.
The Get application data workflow step now returns purchased, assigned and available seats per license type.
Google Workspace account creation can now fill the employee type and other standard profile fields from your mapping.
Lucca list fields, such as career path or team, can now be mapped in Settings > HR Properties.
The "Professional email" field is now called "Primary email" in data mapping.
When a user's email changes in its source, Corma now updates their primary email at the next sync.
Microsoft syncs now keep employee type changes you made manually in Corma.
Corma now tells you whether the credentials work each time you connect an integration.
When Corma cannot revoke a Microsoft user because of their admin role, it now explains why.
The Applications review page now has bulk actions, shows what each match did, and no longer lists Microsoft first-party apps.
The country picker of a dynamic group rule now offers every country.
The workflow builder has a smoother grid scrollbar and readable zoom controls in dark mode.
Offboarding running the deprovisioning steps twice has been fixed.
A workspace signup blocking access to other workspaces has been fixed.
Users being created with a blank name has been fixed.
Duplicate entries in the merge audit log have been fixed.
A failed one-off action creating a ticket with no assignee has been fixed.
The Add new app button doing nothing has been fixed.
An error when updating a contract seat item has been fixed.
The HR sync skipping a person with two worker records has been fixed.
Adobe sub-licenses not syncing has been fixed.
Microsoft license syncs timing out has been fixed.
Google group removal stopping at the first refused group has been fixed.
An unclear error when Atlassian refuses an API token has been fixed.
Qonto's Create account action failing has been fixed.
Celonis Make license syncs failing for some regions have been fixed.
Datadog activity syncs failing for large organizations have been fixed.
Lucca and HiBob sync failures have been fixed.
Tab focus issues and lost edits in the workflow builder have been fixed.
Public API changes: connector ids are now connection ids, and requests support a workspace scope. Writes to managerEmail and managerRemoteId now return invalid_mapping. A PUT …/bulk/user request that sets data.customFields is now refused instead of succeeding with no effect. Update any integration that relied on the old behavior.