A-Leads

The Corma integration for A-Leads puts your sales team's contact data tool under the same access rules as your CRM: Corma knows who holds an A-Leads login, which role they have and when they should lose it. It is designed for companies where sales or growth teams bought A-Leads themselves and IT inherited the accounts.

Key takeaways

• A-Leads is priced in credits rather than seats, and workspace admins can track how many credits each user consumes.
• A-Leads has three user roles (Admin, Standard and Viewer), and only Admins can add or deactivate users in a workspace.
• A-Leads limits single sign-on to its Custom plan, documents no SCIM provisioning, and its API covers data search and enrichment, not user management.

How is access controlled in A-Leads?

A-Leads is a B2B contact and company data platform operated by Alva Intelligence LLC. Users search and enrich leads with work emails, direct phone numbers and company data, then export them to CSV or push them to tools such as HubSpot and Instantly.

Inside a workspace, an Admin invites users and gives them the Admin, Standard or Viewer role. Deactivation cuts access immediately. Because nothing links A-Leads to your identity provider below the Custom plan, every one of these steps is manual.

Why does a sales data tool need offboarding?

The risk in A-Leads is not an idle seat, it is a live login that can still spend credits and export personal data. A contact list holds the names, emails and phone numbers of real people, and A-Leads' terms of service treat your company as the controller of that data under GDPR. A former sales rep who can still export a list is a data protection issue before it is a cost issue.

Tools like this often arrive on a team credit card, which is how shadow IT grows in sales and marketing stacks.

What Corma does for A-Leads

• Discovery: A-Leads shows up in your inventory even when it was bought outside IT, through Corma's SaaS visibility layer.
• Leaver deactivation: the departure in your HR tool triggers deactivation in A-Leads, carried out by Corma's AI agents since the API does not manage users.
• Role hygiene: Admin rights stay with a named owner and everyone else defaults to Standard or Viewer, in line with the principle of least privilege.
• Renewal decisions: login activity and the per-user credit view help decide who still needs access before the plan renews.
• Evidence: every grant and removal is logged, ready for a GDPR or ISO 27001 review.

A-Leads integration FAQ

Does A-Leads support SSO or SCIM?

A-Leads lists single sign-on on its Custom plan only and offers Google and Microsoft sign-in on its login page. No SCIM or SAML support is documented, so accounts are managed in the workspace settings. For the general method, read our guide to managing apps without SCIM, SAML or SSO.

Can the A-Leads API remove users?

No. The API, available on every plan with an API key, covers search, enrichment and email verification. User management stays in the A-Leads interface.

Where does A-Leads host data?

A-Leads' terms of service state that the service is hosted by Azure and Hetzner in the European Union unless agreed otherwise, with a data processing agreement based on standard contractual clauses. Corma runs on AWS inside the EU.

Want sales tools like A-Leads covered by the same leaver process as your CRM? Talk to the Corma team.