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

# Is work domain

> Choose which email domains workflow conditions treat as not work, then use those conditions to filter or disqualify leads.

Open **Settings → Domains → Is work domain** to manage the domains that workflow rules treat
as not work. These are exclusion lists: adding a domain makes **is work domain** return false
for that domain.

Use **is work domain** to let work addresses continue, or **is not work domain** to send excluded
addresses to a different branch. The condition checks the domain. It does not disqualify a lead,
update a CRM record, or stop a workflow by itself.

> [!NOTE]
>
> All workspace members can view and search the lists. Only owners and admins can edit them.

## What references what

A condition reads the email field you select and checks its domain against your workspace's lists.
The same lists apply wherever you use these work-domain operators in workflow conditions.

```mermaid theme={null}
flowchart TD
  Settings["Settings → Domains → Is work domain"] --> Custom["Your list: custom exclusions"]
  Settings --> Provided["Provided list: included domains minus removals"]
  Custom --> Check{"Email field: is work domain?"}
  Provided --> Check
  Input["Lead email from a trigger or earlier step"] --> Check
  Check -->|True| Continue["Your work-email branch"]
  Check -->|False| Other["Another matching branch or Else"]
  Continue --> Next["Continue qualification or routing"]
  Other --> Choice["Your configured action: nurture, redirect, or disqualify"]
```

For **is not work domain**, a valid excluded domain returns true instead. Both operators require
a usable email, URL, or domain value. A missing or invalid value does not count as a personal email.

## Manage the lists

* **Your list** contains domains and patterns you add for this workspace.
* **Provided list** contains Default's free and disposable email providers. Select **Remove**
  to exclude an entry from this workspace's checks. Select **Restore** to include it again.
* **Search domains** searches the entire selected list, including rows not currently shown.
* Removing a provided entry does not override a matching rule in **Your list**.

![Is work domain settings with the Provided list selected and gmail.com found through search](https://mintcdn.com/default-b6d0c477/G9ioYXKTvp7WnjbM/images/settings/is-work-domain/provided-list.png?fit=max\&auto=format\&n=G9ioYXKTvp7WnjbM\&q=85\&s=99cafc4e4bd62241b0c064b03f988612)

To add several entries, paste a comma-separated or newline-separated list into **Your list**,
then select **Add domains**. Quoted CSV cells are supported. You can add up to 1,000 unique
entries per paste. If an entry is invalid, correct the paste and try again; no entries from that
paste are saved until it is valid.

```csv theme={null}
example.com,.edu,*.edu.*
```

### Choose a domain pattern

Each row shows what that entry matches, independent of other saved entries.

| Entry | Matches | Does not match |
| - | - | - |
| `example.com` | `example.com` | `sales.example.com` |
| `.edu` | `school.edu` | `school.edu.au` |
| `edu.*` | `edu.com`, `edu.au` | `school.edu.au` |
| `*.edu.*` | `school.edu.au`, `dept.school.edu.au` | `school.edu`, `edu.au` |
| `*.edu` | `school.edu`, `dept.school.edu` | `school.edu.au` |

A dot is literal. An asterisk matches zero or more characters, including dots. `edu.*` is a
literal prefix rule, not a special rule for universities.

## Use it in a Multi-Branch condition

**1. Select the email field**

Add or open a **Multi-Branch** node. In a branch's conditions, select the lead's email field
from the trigger or an earlier step.

**2. Choose the operator**

For a branch that lets work addresses continue, select **is work domain**.
For a disqualification branch, select **is not work domain**.
These operators use the workspace lists; you do not paste the domain list into the condition.

**3. Connect the next action**

Connect the branch to the action you want. For example, route work addresses to sales and
send other addresses to a nurture path. Configure a CRM update if you want to save a
disqualified status. Naming a branch does not update a lead's status.

**Multi-Branch** checks branches in order and takes the first matching branch. **Else** catches
runs that match none. If you combine this check with other conditions, those conditions also
control which branch runs.

With `gmail.com` active in **Provided list** and no matching custom rule:

| Lead email and setting | is work domain | is not work domain |
| - | - | - |
| `lead@gmail.com`, provided entry active | False | True |
| `lead@gmail.com`, provided entry removed | True | False |
| `lead@gmail.com`, provided entry restored | False | True |
| `lead@acme.com`, no matching exclusion | True | False |

## Check the result

Use **Test** in the workflow canvas with one excluded address and one allowed address.
Inspect the condition result and selected branch in the [run log](https://docs.os.default.com/workflows/run-logs.md).
Test runs execute configured actions, so use a test workflow without customer messages or CRM updates.

List changes apply to new workflow runs without publishing the workflow again. Runs already in
progress keep the lists they started with. These settings do not change form email validation or
enrichment rules. Editing the workflow itself still requires **Publish** for live runs.

For a larger qualification example, see [Lead qualification](https://docs.os.default.com/lead-routing/qualification.md).
For branch ordering, see [Multi-Branch](https://docs.os.default.com/workflows/steps-logic-timing.md#multi-branch).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.