> ## Documentation Index
> Fetch the complete documentation index at: https://docs.migma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Permission-Based Sending

> Permission-based email guidelines for campaigns, newsletters, lifecycle emails, and transactional messages

Migma is built for permission-based email. Every marketing contact you email should have opted in to hear from you through your website, sign-up forms, checkout flow, product account, or another clear consent path.

<Info>
  Migma is not for cold email. Use it for newsletters, lifecycle emails, product updates, and customer communications to people who asked to hear from you.
</Info>

## Documentation Index

Fetch the complete documentation index at [/llms.txt](/llms.txt). Use this file to discover available pages before exploring further.

***

## What Fits

Use Migma for emails people expect from your brand.

<CardGroup cols={2}>
  <Card title="Newsletters and digests" icon="newspaper">
    Send recurring updates to subscribers who joined your list.
  </Card>

  <Card title="Product announcements" icon="bullhorn">
    Share launches, feature updates, and company news with your audience.
  </Card>

  <Card title="Promotional campaigns" icon="tags">
    Send offers and seasonal campaigns to contacts with marketing consent.
  </Card>

  <Card title="Lifecycle automations" icon="diagram-project">
    Create welcome flows, onboarding sequences, reactivation emails, and post-purchase follow-ups.
  </Card>

  <Card title="Transactional messages" icon="receipt">
    Send account, order, billing, or security messages the recipient expects.
  </Card>

  <Card title="Customer communications" icon="comments">
    Keep existing customers informed about products, services, and changes they care about.
  </Card>
</CardGroup>

If someone signed up, purchased from you, created an account, requested updates, or explicitly agreed to receive marketing, you are in the right territory.

***

## What Does Not Fit

Cold outreach is not permitted.

That includes:

* Scraped email addresses
* Purchased, rented, or borrowed lists
* LinkedIn exports
* Guessed addresses
* Role-based addresses without clear consent, like `info@` or `sales@`
* CRM contacts who never opted in to receive marketing email
* Event attendees or prospects added to newsletters without clear permission

Beyond policy, cold email hurts your sending reputation. If recipients did not ask to hear from you, they are more likely to ignore, unsubscribe, bounce, or mark messages as spam. That can make legitimate newsletters and customer emails harder to deliver.

***

## The Consent Test

Not sure whether a contact belongs in Migma? Ask:

<Card title="Did this person take a deliberate action to receive email from us?" icon="circle-check">
  A clear form submission, checkout opt-in, preference-center choice, or account notification setting counts. Being connected on LinkedIn, appearing in a CRM, or matching your target customer profile does not.
</Card>

### Consent Examples

<Tabs>
  <Tab title="Good">
    <Check>Newsletter form with clear copy: "Send me product updates and newsletters."</Check>
    <Check>Checkout checkbox for marketing emails, unchecked by default where required.</Check>
    <Check>Account setting where the user selects product update emails.</Check>
    <Check>Event registration form that clearly says attendees will receive follow-up emails.</Check>
  </Tab>

  <Tab title="Bad">
    <Warning>Pre-checked newsletter consent for EU or UK subscribers.</Warning>
    <Warning>Adding sales-call contacts to a newsletter without permission.</Warning>
    <Warning>Importing a purchased list because contacts match your audience.</Warning>
    <Warning>Using a scraped founder, LinkedIn, or directory list for promotional email.</Warning>
  </Tab>
</Tabs>

***

## How Migma Helps

Migma gives you tools to create better email and reduce sending risk, but your list quality still matters.

<CardGroup cols={2}>
  <Card title="Preference center" icon="sliders" href="/audience/preference-center">
    Let subscribers manage topics, frequency, and unsubscribe choices.
  </Card>

  <Card title="Suppression lists" icon="ban" href="/sending-domains/suppression-list">
    Keep unsubscribed, bounced, and blocked contacts from receiving marketing sends.
  </Card>

  <Card title="Email preflight" icon="check-double" href="/email-editor/email-preflight">
    Review links, content quality, compliance basics, and deliverability risks before sending.
  </Card>

  <Card title="Sending domains" icon="globe" href="/sending-domains/overview">
    Authenticate your domain so inbox providers can trust your mail.
  </Card>
</CardGroup>

***

## Before You Import Contacts

Before uploading a CSV or syncing contacts from another tool, confirm:

<Check>Each contact has a valid consent source or another lawful reason to receive the email.</Check>
<Check>You know whether the contact should receive marketing, transactional, or both.</Check>
<Check>Unsubscribed, bounced, and suppressed contacts stay suppressed.</Check>
<Check>EU and UK newsletter signups use clear consent, with no pre-checked marketing boxes.</Check>

For CSV uploads, see [CSV Upload](/audience/csv-upload). For GDPR newsletter consent, see [GDPR newsletter consent](/compliance/gdpr-newsletter-consent). For CAN-SPAM, see [CAN-SPAM checklist](/compliance/can-spam-checklist).

***

## Related Pages

<CardGroup cols={2}>
  <Card title="Security & Compliance" icon="shield-check" href="/security/compliance">
    Learn how Migma supports GDPR, CAN-SPAM, CASL, and security requirements.
  </Card>

  <Card title="Audience Hygiene" icon="broom" href="/audience/deliverability">
    Keep lists healthy and reduce bounces, complaints, and deliverability issues.
  </Card>

  <Card title="Add a Sending Domain" icon="globe" href="/sending-domains/add-domain">
    Verify DNS records before sending from your own domain.
  </Card>

  <Card title="Email Preflight" icon="check-double" href="/email-editor/email-preflight">
    Catch content, link, compliance, and spam-risk issues before subscribers see them.
  </Card>
</CardGroup>