Attio

Attio

Govern Attio with Corma: seats billed whether used or not, Admin and Member roles, per-user mailbox sync and workspace API keys that never expire.

The Corma and Attio integration keeps Attio seats and roles in line with your go-to-market team, from the first invite to the day someone leaves. Attio describes itself as an AI-native CRM platform built for startups and builders, used to unify customer data, automate workflows and build custom solutions. Each user connects their own mailbox, so every member who syncs brings their own email and calendar data into the workspace.

Key takeaways

  • Attio bills per seat, a seat is one active member or pending invite, and billing follows purchased seats rather than active users.
  • Attio has two access levels, Admin and Member, and an outside person added as a member on Pro or Enterprise can still see all records.
  • Suspending an Attio member deletes the emails and calendar events they synced, except events tied to call recordings, unless an admin retains that data, an option on Plus, Pro and Enterprise.
  • SAML SSO, SCIM user provisioning and audit log export are listed as Enterprise features in Attio.

What changes when an Attio member leaves?

Attio never deletes members: it suspends them, so past actions stay attributed. Suspending a member keeps the company and people records created from their synced accounts, and exits any active sequence recipients they were sending to. Unless the admin retains it, the email and calendar data they synced is deleted, except calendar events tied to call recordings. That choice has to be made before the suspension, not after.

Seats are the second point. Attio bills per seat, and billing is tied to the number of seats, not to how many people actively use them, so a suspension alone does not lower the bill. API keys need the same attention: only admins can generate them, each key gets scopes, and keys never expire until someone deletes them. They act for the workspace as a whole, independently of any one member.

How Corma governs Attio

  • Seats matched to the team: Corma flags Attio seats held by suspended or inactive members, so an admin can lower the seat count before renewal. See how license reclaim works.
  • Offboarding with a data decision: on Plus, Pro and Enterprise, a leaver workflow in the IT Workflow Builder asks an admin whether to retain the person's synced email and calendar data before suspending them in Attio.
  • Admins and outside members under review: Admin access and members added for outside collaboration go into automated access reviews.
  • Joiners through requests: new sales and success hires ask for Attio in the self-service app store, and a manager approves before a seat is used.

Frequently asked questions

Does Attio support SSO and SCIM?

Yes, on the Enterprise plan, where Attio lists SAML SSO, SCIM user provisioning and audit log export. With SCIM, adding someone in your identity provider provisions them in Attio and removing them suspends their access, and Attio publishes setup guides for Okta and Microsoft Entra. Read what SCIM automates.

How does Corma connect to Attio?

Through Attio's API where it fits, or through Corma's browser-based agents, which work in the Attio workspace settings like an admin. Corma governs other CRMs the same way, such as HubSpot.

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 see which Attio seats you pay for but no longer use? Book a Corma demo.

Related Integrations

Check out other integrations that could help you on managing your software licences and accesses!