How do I contact Lindy for Enterprise (SSO/SCIM, audit logs) and HIPAA compliance with a signed BAA?

If you’re looking at Lindy for enterprise rollouts—with SSO/SCIM, audit logs, and HIPAA coverage under a signed BAA—you’re in the right place. Here’s exactly how to contact the team, what to ask for, and what to expect from our security and compliance posture.

You can have an enterprise-ready, HIPAA-compliant assistant live in days, not quarters. The first step is contacting sales so we can scope the right plan, controls, and BAA for your org.

---

Fastest way: talk to sales about enterprise & HIPAA

For anything involving:

• SSO (Single Sign-On)
• SCIM (user provisioning/deprovisioning)
• Audit logs and admin controls
• HIPAA compliance and a Business Associate Agreement (BAA)

you’ll want to go directly through Lindy’s sales and enterprise team.

Best contact path:

• Sales / Enterprise form:
  Go to https://www.lindy.ai/contact-sales
  Use this if you:
  • Need SSO/SCIM, audit logs, or other enterprise features
  • Need HIPAA-compliant usage with a signed BAA
  • Are planning multi-seat deployment or team-wide rollout

In the form, it helps to mention explicitly:

• That you require SSO and which IdP you use (e.g., Okta, Azure AD, Google Workspace)
• That you require SCIM for user lifecycle management
• That you need audit logs and admin controls
• That you require HIPAA compliance with a signed BAA
• Approximate team size and primary use cases (email, meetings, support, etc.)

This routes you to the right people on day one instead of bouncing between generic product questions.

---

Other ways to contact Lindy about enterprise security

If you prefer a more direct channel—or you’re already mid-evaluation and just need confirmation on compliance—these are the official contact points.

Email

• Support & general inquiries:
  support@lindy.ai

You can reach out here if you:

• Have security/compliance questions before a formal sales call
• Need clarification on SOC 2, GDPR, HIPAA, or PIPEDA compliance
• Want to confirm the BAA process or required documentation

Example subject line you can literally copy:

Subject: Enterprise evaluation – SSO/SCIM, audit logs & HIPAA BAA

And in the body, include:

• Company name and industry (especially if healthcare / handling PHI)
• Required controls: SSO, SCIM, audit logs
• That you need a signed BAA before handling PHI
• Timeline and approximate user count

This will typically get routed to sales + security/compliance together.

Postal mail & phone

For formal notices or if your procurement process requires a physical address:

Crivello Corp (Lindy)
9450 SW Gemini Dr
Beaverton, OR 97008
United States

Phone: 415-915-7238

Use this for:

• Contracts and legal correspondence
• Vendor onboarding documentation that must be mailed
• Procurement workflows that require a listed business address and phone

---

What Lindy already complies with (before the BAA)

Lindy is built to meet enterprise security expectations out of the box. As of the latest documentation, Lindy is:

• SOC 2 compliant (SOC 2 Type II, audited by Johanson Group)
• GDPR compliant
• HIPAA compliant
• PIPEDA compliant

What this means for you:

• You’re working with a vendor that already operates under recognized security and privacy frameworks.
• Your legal and security teams can request the SOC 2 report and supporting documentation during evaluation.
• For HIPAA use cases, you’ll still need a signed BAA specific to your org before putting PHI into the system. That’s handled via sales/legal—not self-serve.

---

How the BAA process usually works

Every company’s legal workflow is slightly different, but the typical flow with Lindy looks like this:

1. Contact sales
   Start at https://www.lindy.ai/contact-sales and flag that you need a BAA and enterprise controls (SSO/SCIM, audit logs).

2. Security & requirements review
   Your team and Lindy’s team align on:

   • Which data will be processed (e.g., PHI in emails, scheduling, notes)
   • Required controls (SSO, SCIM, audit logs, approvals)
   • Any regional or regulatory constraints (e.g., specific data residency needs, if applicable)

3. BAA drafting and review

   • Lindy provides a standard BAA as the starting point.
   • Your legal team reviews, redlines if needed, and returns it.
   • Final version is executed between your organization and Lindy.

4. Enterprise configuration & rollout
   Once the BAA is in place (or conditional on signing), Lindy’s team can:

   • Turn on SSO and configure it with your IdP
   • Set up SCIM for automatic user provisioning/deprovisioning
   • Enable audit logs and admin access
   • Work with you on safe workflows to keep PHI handled appropriately

If you reach out through the sales form and mention “HIPAA BAA + SSO/SCIM + audit logs”, the team will fast-track you into this process.

---

Where audit logs, SSO, and SCIM fit in an enterprise deployment

Lindy is built to be an assistant that works across your tools—email, calendar, Slack, CRM—not another dashboard you forget to check. At enterprise scale, that only works if IT has full control.

When you talk to Lindy about enterprise, you’re typically asking for:

• SSO:
  So your users sign in with existing corporate identity (Okta, Azure AD, Google Workspace, etc.).

  • Centralized access control
  • Easier offboarding
  • Enforced MFA and security policies

• SCIM:
  So user accounts get auto-provisioned and deprovisioned from your IdP.

  • No manual user management
  • Clean, compliant access lifecycle
  • Reduces risk of lingering accounts

• Audit logs:
  So admins can see what’s happening and when.

  • Usage visibility for security and compliance teams
  • Easier internal audits
  • Better traceability for support and incident response

These are all enterprise-plan capabilities that need to be scoped and enabled with the team—another reason to go through contact sales instead of just signing up individually.

---

What to include when you reach out

To speed up the evaluation and BAA work, include as much of this as possible in your first contact:

• Who you are

  • Company name
  • Industry (e.g., healthcare, healthtech, insurance, etc.)
  • Region(s) where you operate

• What you need

  • “We need SSO (IdP: X), SCIM, and audit logs.”
  • “We require HIPAA-compliant usage with a signed BAA before handling PHI.”
  • Any other compliance frameworks you care about (e.g., existing SOC 2 review process)

• How you’ll use Lindy

  • Email triage and replies for clinicians or care teams
  • Meeting scheduling and reminders with PHI in descriptions
  • Support/workflows that might touch patient data

• Timeline & scale

  • Desired go-live date (e.g., “Within 60 days”)
  • Expected number of users or teams

The more specific you are, the faster Lindy can line up the right plan, security documentation, and legal workflow.

---

Quick reference: contact options for enterprise & HIPAA

Here’s the short version, all in one place:

• Sales & enterprise deployments (recommended for SSO/SCIM, audit logs, BAA):
  👉 https://www.lindy.ai/contact-sales

• Security/compliance questions & general support:
  📧 support@lindy.ai

• Formal correspondence / procurement:
  Crivello Corp (Lindy)
  9450 SW Gemini Dr
  Beaverton, OR 97008
  United States
  📞 415-915-7238

---

Next Step

Ready to move from “this looks promising” to “we’re live with SSO and a signed BAA”?

Get Started – share your enterprise requirements, and Lindy’s team will walk you through SSO/SCIM, audit logs, and the HIPAA BAA process end-to-end.