Merge two users into one

When the same person ends up twice in Corma, you can now merge the two records into one without losing anything.

• Two ways to start: select exactly two users on the Users page and click Merge in the selection bar, or open a user and choose Merge in the actions menu.

• Preview before you confirm: a comparison shows both users side by side, which email addresses and how many licenses the merged user will have, and lets you switch which user is kept.

• Everything moves to the user you keep: licenses, groups, owned apps and workflows, tickets, notes, and audit history. If both users have the same license, it is kept once.

• Unsafe merges are blocked: Corma tells you why and does not merge, for example when one of the two users has an onboarding or offboarding in progress, or when both are linked to the same identity or HR integration.

• Admins only, and traceable: only admins can merge users, and each merge is recorded in the audit log.

This means a duplicate created by a rehire, a typo in an email or a second sign-in method can be cleaned up in one step, with the history and ownership kept.

Data that is calculated or tied to a single device, such as activity totals and desktop agent reports, is not carried over. Totals are recalculated after the merge, and the preview warns you when the user being merged has such data.

Invite an app owner by email to connect an app

When the person who needs an app connected is not the one who can connect it, an admin can now send the app owner an invitation from Corma.

• Invite admin button: it appears on connectors that are not connected yet, in the connector catalogue and on the connector card of an app's page. Connected connectors still show Manage.

• Check before sending: a window shows who will receive the email and a preview of it. If the app has no owner yet, you pick one first. You can only choose people who are already users in your workspace.

• Send invite link: the email comes from Corma and links the person to the app's page, where they sign in as usual and click Connect on the connector.

• The owner is updated: choosing someone different from the current owner makes them the app's owner, and the window says so before you confirm.

This means you no longer need to chase the right person on Slack to get an app connected.

See the Employee guides for how app owners connect and manage their apps.

License alerts now live on the Licenses page

The Underused licenses and Orphaned licenses tabs of the Contracts page are gone. The same information now sits as alerts on the Licenses page.

• Five alerts, one click each: user terminated, user disabled in IdP, underused licenses, accounts unmatched and missing license type. Each shows a count of live licenses and applies the matching filter to the table when you click it.

• Filters you can see and remove: the filters an alert applies show in the Licenses toolbar.

• Old links keep working: the old Underused and Orphaned addresses, and the links on the Overview Licenses usage card, open the Licenses page with the right filter.

This means you find the licenses to reclaim, from people who left or whose account is disabled, in one place.

Improvements

• The Users page now has a Source filter, like the Applications page. It lists the sources that can create or update users, such as identity providers, HR systems and SSO apps, and shows users created or updated by the source you pick.

• The Create user form now includes your custom user fields, and its sections are clearer.

• Payfit and Rippling can now be mapped to Corma fields in Settings > HR Properties, including Rippling's custom fields.

• The Sync now option is back on BambooHR and on the other HR connectors that run through the orchestrator.

• The Datadog connector now works with custom data mapping for account creation.

Fixes

• The Clear button in Edit saved filters not removing the filters has been fixed.

• Removing the owner of an app from its settings failing has been fixed.

• Deleting an app whose licenses appear in the audit log failing has been fixed.

• Deleting a user timing out has been fixed.

• The HubSpot Attribute license action failing has been fixed.

• Changing a license's billing status or type blocking the page has been fixed.

• An error appearing when you click a ticket or approval that someone else already handled has been fixed.

• Microsoft and Google license revocation sync failure have been fixed.

• Microsoft sub-license revocation syncs failing have been fixed.

• The tables for API keys, labels and admins being cropped have been fixed.

You can now decide where each piece of user data in Corma comes from, and what Corma writes into the accounts it creates in your apps. It works in both directions: inbound (from your HR system and identity provider into Corma) and outbound (from Corma into your apps).

Inbound: choose where each Corma user field gets its value

Settings > HR Properties now has a Mapping card, so you decide which source feeds each Corma user field.

• One row per Corma user field: each row has a source picker, so you choose where the value comes from.

• An expression editor: combine or reshape values before they are saved, for example to join two fields or clean up a format.

• Your own user fields: create custom fields on users, and edit them from the same card.

• Custom fields in workflows: the Get user data step now returns every custom field of your workspace, so later steps can use them by the label you gave them.

• More sources: Okta can now be a source for inbound mapping, the Personio department field is supported, and the Silae connector works with the mapping.

Outbound: choose what goes into the accounts Corma creates

The same control now applies in the other direction. In the settings of an app that supports it (Google, Microsoft, Okta and Slack), the new Fields creation tab lets you choose which Corma fields go into the account Corma creates in that app.

• You pick the fields: decide which Corma user fields are written into a new account, instead of relying on a fixed set.

• Leave a field unmapped: you can choose not to map a field, and it is left out of the account.

This means the way Corma reads your HR system, and writes into your apps, follows your own data model from start to finish.

If your workspace did not use this before, nothing changes until you add a mapping: Corma keeps reading your sources the way it did.

Silae Integration

Corma now integrates with Silae!

Silae is a leading cloud-based payroll and HR management software designed to automate complex payroll workflows and manage employee administrative data. You can now:

• Collect HR users: centralize Silae users directly within Corma to keep your user directory accurate and up to date.

• Collect HR profiles: enrich user profiles in Corma by syncing detailed HR attributes and employee details from Silae.

• Sync Custom fields: pull in custom organization attributes and metadata to maintain complete visibility over your workforce structure.

  

Improvements

• Custom agents now report their health like every other connector.

• Long lists no longer stop at a page of rows: keep scrolling and Corma loads the next ones.

• Your workflows can now create and read licenses, close tickets and clean up Atlassian access on their own.

• You can now show a Criticality column on the Applications page from the display properties, and sort by it.

• The help center now has its own button in the sidebar, and Audit log has moved out of the user menu into the sidebar.

• In Settings > Access requests, an admin can now choose who may submit an access request on someone else’s behalf. The choice applies to the employee portal and to the Slack command.

• Corma now reads the organization roles of your GitHub users when it syncs licenses.

• The Zoom license sync no longer overwrites the license types you set by hand.

• Create user steps for Google, Microsoft, Okta and Slack now reuse an account that already exists instead of failing, for example when someone is rehired.

• The Slack add to channels step no longer fails when the user is already in the channel.

• Notifications have a new look, with a coloured icon and a smaller close button, and stay clickable when a window is open on top of the page.

• The notification shown after you create an app, a user or another item now names it and links to it.

• Bulk revokes, concluding an access review and matching licenses to a user now close their dialog straight away and show a notification that follows the progress until the result.

• After you change a license’s billing status or type, edit a contract or change your currency, a notification says your totals are being recalculated, and the numbers update when it is done, with no reload.

• Errors that were previously not shown, such as an expired session, now appear as notifications.

• You can now open a saved view’s filters from Edit saved filters in the three dots menu next to its name, and change them without adding a new filter first.

• The Sources hows whether a user signed up with Google, Microsoft or SAML, tells an action run by a workflow apart from a one-off action, names and links the workflow, shows who ran it, and marks records.

• License pills with a count of zero are now hidden on the Licenses page.

• Atlassian syncs now bring in each user’s plan, role and last activity for every Atlassian app, and now find the users of organizations where they previously found none.

• The Invoices page search now also finds invoices by supplier name, and its filter bar is no longer cropped.

• The Safari extension now uses the new Corma icons.

Public API: the action IDs custom_integration.provision, custom_integration.deprovision and custom_integration.agent.licenses.get_licenses no longer exist. Each custom agent operation now has its own ID. Call GET /actions to get the current IDs, and update any integration that used the old ones.

Public API: filtering licenses with filters[userId][notIn] now also returns unassigned licenses.

Fixes

• Connecting 1Password failing with a 404 has been fixed.

• Google and Microsoft SSO app syncs failing or stopping partway has been fixed.

• Token URLs being cut off has been fixed.

• The token count in a user’s details being wrong has been fixed.

• License types being removed after each sync has been fixed.

• Spare seats on the Contracts table being overstated has been fixed.

• Failure to find apps in a bundle has been fixed.

• Deleting a large app, such as Google, from its page failing has been fixed.

• Deleting a user who held a license with audit log history failing has been fixed.

• The “See my request” link in access request emails not working has been fixed.

• Employees mistakenly seeing the blocked page has been fixed.

• Removing a user from Cursor during an offboarding failing has been fixed.

• Atlassian syncs failing on large organizations has been fixed.

• Failure to add a newly invited GitHub user to teams during has been fixed.

• Error connecting Zoho has been fixed.

• Misalignment on applied filters row has been fixed.

• The Public API registry actions endpoint returning an error has been fixed.

Every connector now has its own page

Click any connector on the Connectors page to open a page that holds everything about it, with its sync history alongside.

• Three tabs: Reads and writes, Syncs and Settings, under a header that shows the connector's status, connection method and last check.

• Reads and writes saves as you click: switch an individual read or write on or off and the change is saved straight away, with no Save button.

• Every sync run in the Syncs tab: each run is listed by day with its status and duration, and the top of the tab shows the last successful run and how many runs failed.

• Skipped runs say why: a run that did not happen tells you the reason, so a paused connector no longer looks broken.

This means you can check whether a connector is healthy, and fix it, from one page.

A Connectors page that shows what you use

The Connectors page now lists only the connectors you have connected. Everything else is one click away.

• Your connectors only: the grid shows the connectors your workspace has connected, with their status.

• Suggestions stay visible: suggested connectors still appear in a band above the grid, as smaller cards that link to the connector's page.

• Simpler filters: the Type filter now has two values, API and Agent, and the Status filter only offers statuses that apply to connected connectors.

This means the page opens on what needs your attention, not on hundreds of apps you have not connected.

Open Corma straight from your identity provider

If your workspace signs in with SAML SSO, your team can now open Corma from the Corma tile in their identity provider's dashboard.

• One click from the tile: click Corma in Okta, Microsoft My Apps or the Google app launcher and you land in your workspace, signed in.

• Nothing to reconfigure: existing SAML connections support it automatically. If you hid the Corma tile earlier, show it again.

• Microsoft Entra ID: leave Sign on URL empty in your Corma enterprise app, so the tile signs users in directly.

• Same security as before: a tile click goes through the same checks as the Corma sign-in page, including enforced SAML.

This means your team opens Corma the same way they open every other app in your stack.

Import invoices from a CSV file

You can now add invoices to Corma in bulk from a spreadsheet, not only from PDF files.

• A new import option: open Import invoices on the Invoices page and choose From a CSV file, available on every plan.

• Your columns, your formats: start from the template or your own file, map your columns to Corma's fields, and pick your date and amount formats.

• No duplicates: invoice numbers already in your workspace, or repeated in the file, are skipped, so importing the same file twice is safe.

• Matched to your apps: each invoice is matched to an app from its supplier name. Unmatched ones wait under Unmatched invoices for you to attribute.

This means you can bring months of invoices from your accounting tool into Corma in one step.

Redesigned user and app pages

The page for a single user and the page for a single application have a new layout, so the details you check most are visible as soon as the page opens.

• Everything in tabs: an application's page is split into tabs for Overview, Activity, Licenses, Contract, Tokens, Requests and Notes, each showing how many items it holds.

• Key details in a side panel: connectors, status, criticality, app owner, access owner and labels now sit together in a panel on the right, next to whatever tab you are viewing.

• Desktop agent status on user pages: see whether the desktop agent is set up for a user directly from their page.

This means you can see who uses an app, how it is connected and who owns it without leaving a single page.

Improvements

• Onboarding and offboarding steps now run side by side, app by app, so a slow step handled by an agent no longer delays the steps that run through an app's API.

• Onboarding thousands of users at once is faster, with many steps processed in parallel instead of one at a time.

• You can now launch an offboarding through the public API. It appears in the list of available actions.

• The filter bar and column picker now also cover Workflows, Shadow IT policies, Access reviews and SSO tokens, so you can filter field by field, including with "is not", and choose your columns on those pages too.

• Sub-pages and tables shown inside other pages now use the new filter bar, and the previous filters have been removed everywhere.

• Completed access reviews are no longer hidden by default on the Access reviews page. Filter them out, or save a view that excludes them, to get the previous list back.

• The Users table now shows each person's main email under their name, and their department in its own column.

• You can now filter the Users page by group membership, with "is part of any" and "is part of all".

• License tables have a new App account details column, showing the name, email and account ID as they appear in the app, even when the license is matched to a Corma user.

• You can now select several tickets on the Tickets page and Mark as complete, Archive or Export them in one go from the selection bar, or use Select all to act on every ticket at once.

• Bulk actions on access reviews, onboardings, offboardings and workflows now work on selections of more than 200 rows. They run in the background and show their progress, instead of asking you to narrow your filter.

• Google organizational units now show their full path, such as BDR_user/France, when you pick one in a bundle, so units with the same name can be told apart.

• The Get user data workflow action now returns the manager's ID and email, so you can pass the manager to another Get user data step or use their email as a recipient.

• Lucca now syncs users, teams and licenses as separate operations, so you can switch each one off on its own and follow its runs in the Syncs tab.

• Resolving a ticket manually now works when the action was already done in the app, for example a license that was already revoked.

• Settings > Security now links to the SAML SSO setup guides on the help center.

• The Sources hovercard now shows each source's own date.

• The audit log now tells an action run by an agent apart from the same action run through the app's API.

• The message shown when a saved view contains outdated filters is now clearer.

Public API: the Users endpoints now return department and departmentKey instead of team and teamKey. Requests that create or update users still accept teamKey, but sending both keys with different values returns an error. If your integration reads team, update it to read department.

Fixes

• Microsoft applications missing from Corma's catalogue has been fixed.

• Qonto user syncs failing has been fixed.

• Resolving a ticket freezing the page has been fixed.

• Marking a provisioning ticket complete from Slack failing has been fixed.

• "Skip & create a ticket" not creating the ticket has been fixed.

• Tickets not reaching the fallback owner in new workspaces has been fixed.

• Start and end date triggers missing users whose date arrived late has been fixed.

• The Sub-pages tab staying empty on an app's Analytics page has been fixed.

• A duplicated bundle sharing its workflow with the original has been fixed.

• The bulk delete count including items that cannot be deleted has been fixed.

• Some Google and Microsoft SSO tokens not being collected has been fixed.

• Searching SSO tokens by part of a scope has been fixed.

• Deel connections showing as invalid right after connecting has been fixed.

• The Slack /request-access-corma command timing out has been fixed.

• The AI contract import losing its progress message has been fixed.

• Custom agent cards disappearing after connecting has been fixed.

• The filter bar overlapping the table has been fixed.

Saved views, custom columns and better filters

You can now shape a table once and come back to it, on Applications, Accounts and Licenses, Identities and Users, Tickets, and Contracts.

• Save a view: name a set of filters and columns, then pick it again from the views dropdown whenever you need it.

• A rebuilt filter bar with new operators: build conditions field by field, with operators that suit the field, including "is not" to exclude rather than only include.

• Share views to your workspace or keep them to yourself : saves views either as workspace view so any other admin can see it, or save it as a personal view for yourself only.

• Define a default view: set on each page a view as a default view and come back to it every time you loads Corma.

• Choose your columns: show the fields you care about, hide the rest, and keep that choice per view.

• Table or board: switch view mode, and send a link that opens the table exactly as you left it.

This means the filtering you rebuild every morning becomes something you set up once.

Capacities are now reads and writes, with history logs

What a connector does is no longer described as capacities. Each connector now tells you plainly what it reads from an app and what it writes back, and lets you control each one.

• Reads and writes replace capacities: the same underlying operations, named for what they actually do. Reads are the data Corma pulls in, writes are the changes Corma can make.

• Counts on every connector: see how many operations a connector reads and how many it writes before you connect it, not after.

• Turn any single operation on or off: open Manage on a connected connector and switch an individual read or write without disconnecting the whole integration.

• See what ran and when: each operation shows the outcome of its last run beside it, so a failing sync is visible next to the operation itself instead of buried in a log.

• Writes say when they fire: provisioning and deprovisioning actions are tagged as onboarding or offboarding actions, with a line explaining what triggers each one.

This means you can tell exactly what Corma does with an app, in the words you would use yourself, and change it one operation at a time.

Contracts and invoices are now in the public API

You can now manage contracts, invoices and tickets programmatically, alongside the users, licenses and groups already available.

• Contracts and invoices: list, create, update and delete both. Contract responses include seat items with their cost and billing period, plus fixed items and subscription details.

• Tickets replace tasks and access requests: the API now matches the product, where those two became tickets. A new Create action endpoint takes over from the legacy Tasks endpoint.

• Documented in the API reference: every new endpoint, its parameters and its error cases, in the Dev center.

This means your contract and ticket data can flow into your own finance and ITSM tooling without an export step.

Improvements

• Corma now collects more of your Google SSO and SAML applications, including their last activity dates, so more of your stack shows up without extra setup.

• Row actions have moved out of the three dots menu at the right of tables and into the selection bar, with 17 new bulk actions across 8 more entities so nothing is lost.

• Password reset and creation steps for Google Workspace, Microsoft and AWS now share one recipients picker, with optional subject and message fields, so you can send your own wording along with the temporary password.

• Application page cards now cover every status, including restricted, to review and decommissioned, instead of grouping everything into Official and Shadow IT.

• The Authentification checkboxes on applications are now labels, so authentication methods work like every other label and can be filtered the same way.

• You can now see and edit an employee's personal email from the HR Properties panel on their page.

• The main search modal now shows its keyboard shortcuts in a footer.

• Public and Internal labels now always appear after your own labels, so yours are the ones shown first in tables.

• HubSpot seats are now the source of truth for license types on that integration, so removing a seat in HubSpot updates Corma.

• Updating a single license is faster.

Fixes

• Google SAML applications not appearing in your SSO applications, and so not being matchable, has been fixed.

• A nightly job marking non-Microsoft SSO applications as deleted has been fixed, and the affected records have been repaired.

• "Sync members" on a Google or Microsoft identity provider group reporting success while doing nothing has been fixed.

• Date-reached workflow triggers never firing when the date landed on the day itself has been fixed.

• CSV import failing on users who already exist, instead of updating them, has been fixed.

• Nightly Kelio user syncs timing out on large tenants has been fixed.

• A declined sync pass showing as a completed run has been fixed, and sources are now ordered by freshness everywhere.

• A contract renewal date sent as empty being stored as 1970, and producing renewal reminders dated in the past, has been fixed.

• Assigning a country code through the public API when no other user in the workspace had that country has been fixed.

Sign in to Corma with SAML SSO

Corma now supports SAML 2.0 single sign-on, so your team logs in with your own identity provider alongside the existing Google and Microsoft sign-in methods.

• One connection per workspace: a workspace admin connects your provider once from Settings > Security > SAML, using the provider's metadata URL or XML file.

• Presets for the providers you already use: pick Okta, Google Workspace, Microsoft Entra ID, Keycloak or OneLogin from the provider dropdown, or connect any other SAML 2.0 provider through the "Other" option.

• Automatic provisioning on first sign-in: anyone your identity provider authenticates joins your workspace automatically as an employee, with no invitation and no seat to prepare in advance.

• Optional enforcement: once your connection is verified, "Enforce SAML for all members" blocks password, Google and Microsoft sign-in and sends everyone through your identity provider instead.

This means access to Corma itself can follow the same identity rules as the rest of your stack.

Enforcement requires an active SAML connection, and deleting the connection resets it, so a workspace can never lock itself out.

Start here: SAML SSO and How to set up SAML SSO, or go straight to your provider: Okta, Google Workspace, Microsoft Entra ID.

A more complete picture from Okta

Corma's Okta sync now keeps every field Okta returns, instead of discarding some of them along the way.

• Apps land in the right category: apps that were previously miscategorized, or that failed to match against Corma's catalog, now come through correctly.

• User groups come across too: with the new scopes in place, Corma can collect your Okta user groups.

• User Roles are now synced

• Corma can now provision and deprovision Okta users

This means what you see under Connectors > Okta now lines up with what you see in Okta.

Improvements

• Workflows and Audit logs are out of beta, and Workflows now sits in a new "Power up" section in the sidebar.

• Workflows have a new action: add a user to a bundle.

• Updating a license status is faster.

• Contract line items load faster and are more reliable.

Fixes

• Activating a workflow sending it back to draft has been fixed.

• Duplicating a workflow losing its branches and its trigger has been fixed, and a duplicated workflow now starts as a draft.

• CSV exports timing out on large files has been fixed.

• Several Cormie reliability issues, including actions failing to run, have been fixed.

Introducing Labels

You can now create your own custom labels for Apps, Users, and Licenses — a flexible way to organize your workspace beyond Corma's built-in fields.

• Create labels your way: name a label, pick a color from 10 presets (or enter a custom hex), and choose whether it applies to Apps, Users, or Licenses.

• Apply them anywhere: add labels directly from an app or user's page, or right from the Applications, Users, and Licenses tables.

• See them at a glance: labels show up as colored pills in your tables, with a hover card listing everything if more than one is applied.

• Filter by label: find everything tagged with a specific label across your tables.

• Manage them centrally: a new Labels page in Settings lists every label, how many items it's applied to, and when it was last used.

  This gives you a flexible way to organize and find what matters to your company, on top of everything Corma already tracks.

  

  ---

  Improvements

  • Public API keys can now be created as read-only, in addition to full-access.

  • Custom agents can now ask for login credentials mid-chat, instead of requiring them all upfront.

  • The Bitwarden integration now works with self-hosted Bitwarden workspaces, not just Bitwarden Cloud.

  • Provisioning now has a "No action" option, matching the existing deprovisioning behavior.

  • CSV imports for users and licenses no longer time out on large files.

  • The Security page's "Restricted apps in use" card is back, with apps sorted by last activity.

  Fixes

  • Extension activity data no longer updating has been fixed.

  • Some Modjo license syncs failing has been fixed.

  • Licenses missing account ID after custom agent provisioning has been fixed.

  • Workflow runs getting stuck "in progress" has been fixed.

  • Dropdowns inside modals being cut off has been fixed.

  • Session cookies growing too large and causing login errors has been fixed.

  • Okta sometimes misclassifying catalog apps as custom apps has been fixed.

Temporary access requests

Employees can now request access for a limited time instead of indefinitely, and Corma revokes it automatically once that time is up.

• Add access lengths per app: in an app's Requests settings, turn on Temporary access and add the durations employees can choose from — hours, days, weeks, or months.

• Choose from Employee App Store or Slack: employees pick their access length from the same dropdown, whether they request through the App Store or Slack.

• Decide if indefinite access stays allowed: turn off indefinite requests entirely if every request for an app should be time-bound.

• Automatic revocation: once the duration passes, access is revoked automatically and the employee is notified — if they still need it, they submit a new request.

This means access can be granted for exactly as long as it's needed, without anyone having to remember to clean it up afterward.

Shadow IT policies

Your Security page has a new look, and you can now define your own policies for how employees are stopped from using unauthorized apps:

• Warning or Blocked: choose whether employees see a dismissible warning or a full-page block when they open an app covered by a policy.

• Applies to a list of apps: one policy can cover several apps at once, and each app can belong to only one policy.

• Exclude specific teams: leave out any user groups who should be allowed to use the app.

• Write your own message and call to action: customize what employees see, with optional buttons pointing them to an approved alternative.

• Enforced through the browser extension: policies apply the moment an employee opens the app in their browser.

This gives admins real, granular control over Shadow IT, instead of relying on an app's status alone.

Improvements

• Okta integration can now sync HR data (department, job title, country, and more), not just identity.

• Sorting added for the Extension and Desktop agent columns on the Users table.

• Password requirements (length, character rules) for the Reset Password action are now configurable in Settings.

• App details, previously hidden behind clicking an app's logo, now live in their own dedicated Settings tab.

• Custom agent connections now show their creation and connection date, current credential method, and can be renamed — disconnecting and reconnecting no longer wipes your existing configuration.

• Integration connections can now be disconnected directly from their card, without losing existing automations.

Fixes

• Slack ticket messages losing their action buttons and outcome has been fixed.

• Non-admin users seeing settings controls they shouldn't has been fixed.

• Kelio syncs timing out and failing to import data has been fixed.

• A Shadow IT policy edge case with certain domains has been fixed.

• Offboarding suggestions missing for distant termination dates has been fixed.

• The "Re-assign license" button not opening its modal has been fixed.

• The Google "transfer email" workflow action failing has been fixed.

Bring custom agents to your internal apps

You can now build a custom agent for your own internal applications, not just apps in Corma's public catalog.

• Full coverage, even for homemade tools: if your company built or uses a tool that isn't in Corma's 50,000+ apps catalog, you can now train a custom agent for it the same way you would for any other app.

• Same provisioning and deprovisioning automation: internal apps get the exact same custom agent capabilities as public ones, no more manual exceptions for the tools built in-house.

This means you can reach closer to full automation across your entire stack, including the tools that are unique to your company.

Microsoft Teams notifications

Corma can now send workflow and access management notifications directly to Microsoft Teams, alongside existing Slack support.

• Stay informed in Teams: get notified about workflow runs and access events without needing to check Corma or Slack.

This means teams that use Microsoft Teams instead of Slack no longer have to miss out on real-time notifications.

See how to conifgure it here: Enable Microsoft Teams notifications on Corma 

Yooz Integration

Corma now integrates with Yooz!

Yooz is an AP automation and invoice-processing platform that helps finance teams digitize and streamline their accounts payable workflows.

You can now:

• Collect licenses: centralize Yooz users and licenses in Corma

• Provisioning & deprovisioning: automatically assign and revoke Yooz access directly from Corma to effortlessly manage your licenses use

Improvements

• Custom agent setup no longer disconnects when switching tabs, and you can now see a log of custom agent runs and their status.

• Apps that already have a custom agent connected are now shown as disabled with an explanatory tooltip, instead of disappearing from the creation modal.

• Start and termination dates can now be cleared once set, with an improved date picker.

• Offboarding no longer creates noisy duplicate manual tasks for child products under aggregated vendors like Microsoft, Atlassian, and Google.

• User CSV import now supports a personal email column, alongside the professional one.

• New filters on the Applications page: filter by User Group or by Country.

• The App filter on license tables now supports an "is not" operator, letting you exclude specific apps instead of only including them.

• Activity extraction added for Cursor & Claude

Fixes

• Onboardings sometimes getting stuck in "Ongoing" status has been fixed.

• Admin invitations by email sometimes failing has been fixed.

• CSV export emails being wrongly suppressed when email notifications were disabled has been fixed.

• Search sometimes treating similarly-named tickets or users as identical results has been fixed.

• Termination dates set more than 30 days in advance are no longer hidden and can be nulled

• Access owners losing the ability to manage their apps from the employee portal has been fixed.