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

# Skipping Welcome Emails

> How to bring members into Outpost, in bulk or one at a time, without firing your standard welcome flow

<AccordionGroup>
  <Accordion title="How do I import members without sending them welcome emails?">
    Two things stop the welcome flow on an import: keeping each member's original creation date, and labeling them `#Ignore_Welcome`.

    1. **Match the creation date in the CSV/import.** Outpost only fires the welcome flow for members who appear to be new subscribers. If your import into Ghost from another system preserves each member's original creation date, those members come in as historical and the welcome flow won't run. This is the cleanest approach and gives you better analytics later. Members who have creation dates that fall within the welcome flow span OR who have no creation date will go into the Welcome Flow.
    2. **Add `#Ignore_Welcome` as a label on the import.** This system label tells Outpost to skip the welcome flow for any member that carries it. Add it as a tag on the CSV row or just use the Ghost interface when importing members into Ghost. See the [labels reference](/features/label-reference) for the full list of system labels.
    3. **Pull the new members into Outpost right away.** Ghost notifies Outpost about one-off signups but not bulk imports. Outpost checks for these regularly but if you want to work with them immediately: After the import, go to **Publication details → Refresh** with the **Site data** switch on so Outpost picks up the new members immediately. On big imports, this can take a little time to pull in members. See [publication details](/features/publication-details) for more on Refresh.
    4. **Test with a small batch first.** Import about 10 members in Ghost, run the Refresh in Outpost. Then check the [Activity Log](/features/activity-log) to confirm these members were picked up by Outpost and that no welcome emails went out to them. When the test looks right, run the full import or run a bigger slice.

    Want to send this imported list its own welcome series? See [Sending a Different Welcome Series](/faq/sending-a-different-welcome-series).
  </Accordion>

  <Accordion title="How do I add a single member without sending them a welcome email?">
    When a member comes in one at a time — through a signup button on another site, a manual add, an integration, or the API — Outpost treats them as a new signup and fires the welcome flow. To stop that on a per-member basis:

    1. **Apply the `#Ignore_Welcome` label to the member.** This system label tells Outpost to skip the welcome flow for that member. It works no matter how the member enters Outpost: an embedded signup button, the **Add Member** screen, an integration, hand-adding them or the API. See the [labels reference](/features/label-reference) for the full list of system labels.
    2. **For signup buttons on another site**, configure the button (or the Ghost embed tool) to add `#Ignore_Welcome` label to every signup it produces.
    3. **Test it once before pointing real traffic at it.** Sign up a test member, then check Ghost and the [Activity Log](/features/activity-log) to confirm they got the `#Ignore_Welcome` label and did not receive your standard welcome flow.

    Want to send these members a different welcome series instead? See [Sending a Different Welcome Series](/faq/sending-a-different-welcome-series).
  </Accordion>
</AccordionGroup>