Avoma

The Corma and Avoma integration keeps your meeting recorder's seats and roles in line with the sales and customer teams who use it. Avoma describes itself as an all-in-one AI meeting assistant with conversation and revenue intelligence, automating note-taking, scheduling, call coaching and CRM updates. Because it records customer conversations, access to it deserves the same care as your CRM.

Key takeaways

• Avoma charges a paid seat only for users who record and transcribe meetings, and viewers and collaborators are always free.
• Avoma admins remove a user by deactivating them in Settings → Members, and removing a Recorder Seat takes effect at the next billing cycle.
• Only Avoma org admins can create, view or revoke API keys, with up to 10 keys per organization and one of three scopes per key.
• When the user tied to a user-scoped Avoma API key is deactivated, calls with the key return an error, but the key is not deleted automatically.

What does an Avoma admin need to watch?

Recording runs through each user's own calendar. Once a user connects a Google or Outlook calendar, Avoma joins and records that user's meetings as a participant, based on their recording preferences. Since October 12, 2026, Avoma can record Zoom meetings only if Zoom is connected, either once by an admin for the whole company or by each user. The CRM connection is made once, by one user who is an admin in both Avoma and the CRM.

Admins cannot see other users' Private meetings unless those users have shared them, and Avoma does not document what happens to a deactivated user's recordings. Avoma's API key article adds that legacy keys can still read every meeting in the organization, and that any org admin can view key strings on the Developer page. Avoma documents no expiry for API keys.

How Corma governs Avoma

• Recorder seats in the budget: paid recorder seats and their renewal sit in SaaS subscription management, so unused seats can be reviewed and released before the next billing cycle.
• Leavers with a key check: a leaver workflow in the IT Workflow Builder asks an admin to deactivate the person in Avoma, revoke any user-scoped API key issued to them and decide what happens to their recordings.
• Admins under review: Admin and Super Admin roles, which control seats, API keys and CRM integrations, go into automated access reviews.
• API keys with an owner: Avoma API keys are non-human identities, so each one needs a named owner, and legacy keys with organization-wide read access come first.

Frequently asked questions

Does Avoma support SSO and SCIM?

Avoma's Okta and Rippling SSO guides require the Organization plan or higher, while the pricing page lists Single Sign-On (SAML/OIDC) on the Enterprise card only. Once SSO is on, users can log in only through SSO, and Avoma sets it up for you. SCIM Provisioning appears only as a pricing table row checked for Enterprise. Read what SCIM automates.

How does Corma connect to Avoma?

Avoma's public API spec lists users and their roles but shows no endpoint to deactivate them, so Corma can read users through the API where it fits and its browser-based agents can handle deactivation in Settings → Members. See also how Corma covers conversation intelligence tools such as Gong.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want every Avoma leaver deactivated and their API keys revoked? Book a Corma demo.