Attention

The Corma and Attention integration keeps Attention seats, roles and connections in line with your revenue team. Attention describes itself as enterprise-grade AI for sales that automates work out of sales conversations: its notetaker joins calls and the product syncs with your CRM. Because it records customer conversations, who holds a seat, who can see calls and whose accounts power the CRM sync all matter.

Key takeaways

• Each Attention member has one role, one team and one seat type, and the seat type, Recording or Listener, decides whether the notetaker records their meetings.
• A deactivated Attention member can no longer sign in, but the calls and snippets they created stay in the workspace.
• Attention's Salesforce sync acts with the permissions of the one Salesforce user who connects it, and that user needs Modify All Data.
• Attention supports SSO through Google, Okta and Microsoft Entra ID, and SCIM 2.0 with a setup guide for Okta.

What does Attention keep after someone leaves?

Recording depends on each person's own calendar link, so access and data follow people. Deactivating a member stops them from signing in while their calls and snippets stay in the workspace, and since November 2025 admins can transfer ownership of calls to another member. Shared call links need a check too: a shared link is public by default, anyone with it can watch, and it works until someone deletes it.

Connections are the other half. Attention acts with the permissions of the Salesforce user who connects it, and that user needs API Enabled, Customize Application and Modify All Data, so the CRM sync rests on one person's account. Organization-level API keys have full access and are not bound to a user, while user-level keys carry their owner's roles and teams.

How Corma governs Attention

• Seats in view: the Attention subscription and its renewal sit in SaaS subscription management, and Corma flags inactive members before you renew.
• Offboarding with a handover: a leaver workflow in the IT Workflow Builder asks an admin to transfer the person's calls, and to reconnect the Salesforce sync if they were the connecting user, before deactivation.
• Admins and keys under review: admin roles, which manage members and CRM integrations, go into automated access reviews, and org-level API keys are non-human identities that need a named owner.
• Requests with a seat type: new reps ask for Attention in the self-service app store, and the approver confirms a Recording or Listener seat.

Frequently asked questions

Does Attention support SSO and SCIM?

Yes. Attention supports single sign-on through Google, Okta (OIDC) and Microsoft Entra ID (SAML), and SCIM 2.0 with a setup guide for Okta, where unassigning a user deactivates the account without destroying data. SCIM setup needs an organization-level API key created by an Admin. Read what SCIM automates.

How does Corma connect to Attention?

Through Attention's API, which can list, create, update and delete users, or through Corma's browser-based agents in Attention's settings. Corma governs other conversation intelligence tools the same way, 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 to know whose accounts keep your call recordings flowing? Book a Corma demo.