Affinity

The Corma and Affinity integration keeps Affinity seats and roles aligned with your team as people join, change roles and leave, and makes the personal API keys behind your integrations part of every offboarding. Affinity is a relationship intelligence CRM that helps private equity and venture capital firms source deals, manage relationships and close faster. It syncs email and calendar data from each user's account once that user signs in, which makes each user seat both a cost and a data connection.

Key takeaways

• Affinity is priced per user per year and billed annually, across four tiers: Essential, Scale, Advanced and Enterprise.
• Affinity starts syncing a user's email and calendar data when that user first signs in, so each signed-in user is also a mailbox connection.
• When an Affinity user is deactivated or removed, the API key they generated is deactivated, which affects any native integration using it.
• Custom SSO with SAML 2.0 or OpenID Connect is available on the Affinity Enterprise tier only.

What happens to Affinity data when someone leaves?

Affinity separates deactivation from full removal. Deactivating or removing a user frees the seat, transfers ownership of their private and shared lists to the admin who did it, and removes their personal email and calendar data. Their company email and calendar data is removed only on full removal, which is requested by email to Affinity support. A deactivated analyst can therefore leave synced company data behind until someone completes the removal.

Each Affinity API key is assigned to a person, and changes made through the API are attributed to that person. When the person is deactivated, the key stops working, and so does any integration built on it. Seats also reach beyond the deal team: Affinity pricing is per user, and Collaborator seats for outside read-only access, like Sync Only seats, are paid.

How Corma governs Affinity

• Seats matched to people: Corma flags Affinity seats held by leavers or inactive users so finance and IT can act on them before the next annual bill. See how license reclaim works.
• Offboarding in the right order: a leaver workflow in the IT workflow builder can notify the deal lead, ask an admin to approve moving integrations to another key, then deactivate the Affinity user and remind the admin to request full removal from Affinity support.
• Joiners ready on day one: new investment team members get Affinity access through automated provisioning and onboarding.
• Roles under review: Admin roles and Collaborator access go into automated access reviews, where reviewers confirm that outside access is still needed.

Frequently asked questions

Does Affinity support SSO?

Yes, on the Enterprise tier. Affinity's custom SSO supports SAML 2.0 or OpenID Connect, with identity providers such as Okta or Azure. On every tier, users are invited from the Users and Permissions tab; Essential, Scale and Advanced have two account roles, Admin and Standard, and Enterprise adds Enterprise Admin. Learn what single sign-on covers.

How does Corma connect to Affinity?

Through Affinity's API where it fits, or through Corma's browser-based agents, which carry out admin steps in the Affinity interface. Because Affinity API keys belong to individual users and are revoked when that user is deactivated, check whose key each integration uses before anyone leaves.

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 Affinity seats still match your deal team? Book a Corma demo.