Restricting Notetaker by domain: the Blocked domains setting

Last updated: November 18, 2026

Available on: Mac, Windows — adding rules requires admin access and an active Enterprise subscription.

Use Blocked domains to prevent Notetaker recordings of linked calendar meetings with specified email addresses or domains on the invite. Admins can restrict recording without stopping members from joining the call.


How to configure blocked domains

Manage rules only in the admin portal; desktop Settings → Notetaker has no blocked-domains control or per-meeting rule status.

Important: New rules overlapping your organization's verified domains—including parent/subdomain overlaps—or a consumer provider such as gmail.com can stop recordings with your own members. Saving prompts "These rules also block your own members" and lists the conflicts.

Warning: Closing with unsaved edits prompts "Discard unsaved changes?" Discard loses those edits; Keep editing returns to the editor.

  1. Sign in to the admin portal at admin.wisprflow.ai.

  2. Go to Settings → Organization → Notetaker and find Blocked domains.

  3. Click Add domains (no rules) or Configure (existing rules) to open Edit blocked domains.

  4. Edit entries, separated by commas or newlines; delete entries or clear the field to remove all rules.

  5. Click Save.

  6. Choose Save anyway to confirm, or Go back to revise, if prompted.

  7. Confirm "Blocked domains updated" appears; the editor closes and remaining rules show a count on the card.

Changes are recorded in your organization's audit log.

No restart is needed. After removing a rule, retry Join or Record; removal applies on the next successful check. A new rule can take one extra attempt for a meeting already checked as allowed in the same signed-in session.

Entry format

Format

Example

What it matches

Domain wildcard

*@lawfirm.com

lawfirm.com and all subdomains, such as eu.lawfirm.com.

Specific address

alex@wispr.ai

That address and plus-addressed variants (alex+news@wispr.ai), but not addresses on subdomains.

The 200-entry organization limit is checked while typing: "Enter at most 200 entries (you have N)." Each distinct domain or address counts once. An empty list blocks nothing; there is no Allow rule.

All invitees count, including declined attendees, except Google room/shared-calendar addresses ending .calendar.google.com and addresses with nothing before @.

How entries are counted

@lawfirm.com, lawfirm.com and *@lawfirm.com are equivalent. Duplicates merge, ignoring case and trailing dots; the first spelling stays while editing. Blank lines and extra commas are ignored. Saved rules reopen comma-separated with standardized spellings: *@lawfirm.com becomes lawfirm.com.

An address and its plus-addressed variant occupy two slots if entered separately. Internationalized domains save in ASCII; Unicode and ASCII spellings count separately while editing but merge after saving.

Save is disabled with the tooltip "No changes to save." when there are no edits, including changes only to order or equivalent spellings.

If you cannot save

Only the entry limit is checked while typing. Formats are checked on save; all invalid entries are reported together using your entered text, which stays editable. Editing clears the error.

Format errors include "missing a domain"; "not a valid email address. Use person@example.com for one person, or *@example.com for a whole domain."; "'<x>' is not a valid domain"; and "'<x>' has an empty label".

Ports, paths, spaces and control characters are invalid. Space-separated entries produce "Invalid entry '<text>': looks like more than one entry. Separate entries with a comma or a new line."

Top-level domains such as com are rejected: "'<x>' is a top-level domain, which would match every address under it. Enter a full domain, like example.com."

Shared suffixes such as co.uk, com.au and github.io are rejected: "'<x>' is a public suffix shared by unrelated organizations. Enter the organization's own domain, like example.co.uk."

Length errors say "a domain can be at most 253 characters" or "each label can be at most 63 characters"; a label is a dot-separated section.

Network or unknown failures show "Couldn't update blocked domains. Try again." Other errors appear inline; "Failed to save. Please try again." appears only when no error message is available.

  1. Correct any entries named in the error.

  2. Retry Save and check for the success confirmation described above.

When adding or editing is unavailable

Enterprise organizations need no extra setup. Without an active subscription, additions fail with "Enterprise has no active Flow Enterprise subscription"; removals do not require an active subscription.

On other plans, or if Wispr has turned adding off at your organization's request, the card appears only while rules exist. Admins can remove—but not add—entries, and existing rules remain enforced. Attempting an addition disables Save with the tooltip and status message "Adding new domains is not enabled for this organization. You can still remove existing ones."

Non-admins can open the list only when rules exist. The field and Save are disabled; the tooltip says "Only admins can edit blocked domains."


What members experience

When blocked, Join from a calendar reminder, Record in a linked note, and resuming after reopening Flow refuse recording. Only that meeting's note window comes forward with "Notetaker blocked for this meeting"; on Mac, Flow also becomes active. Without an open note window, recording is refused without a message.

The conference link still opens when joining; join-only from the meetings drawer is unaffected. Existing note content stays viewable and editable after dismissing the message.

Members cannot override a rule: Record checks again and refuses while blocked. Ask an admin to change the rules.

Blocked automatic starts—including "Meeting detected" countdowns—produce no recording or prompt. When already blocked, no recorder window opens. If a block applies during the countdown or after opening but before recording, the start is refused; any empty draft closes and any displaced note returns.

Other block-message behavior

The message includes only matching attendees, not the full invitee list: up to four addresses, then "and others". Without addresses, it shows a positive match count if available. The member's own matching address blocks recording but is neither named nor counted; a self-only match shows the generic message without addresses or a count.

Got it, Escape or clicking outside dismisses the message for that opening only; the next blocked start shows it again. There is no retry, override or request-access action. Keyboard focus stays inside until dismissal, then returns to its previous position; the summary behind the message is covered.

Shared notes never show this message. HIPAA/BAA restrictions or other recording-access refusals show their own message instead; organization-wide Notetaker disablement can prevent access before the note opens. Calendar reminders do not indicate whether a meeting is blocked.


Coverage boundaries

Important: These rules require a linked calendar event with attendee addresses. Ad-hoc recordings and detected calls without a calendar match are not blocked. Incomplete attendee lists or missing addresses do not themselves trigger a block, so some attendees may not be checked.

  • Unavailable checks: Without a known block, recording is allowed when a check is pending, fails or cannot run offline. A failed re-check preserves the last result, so a known block remains enforced offline within that signed-in session. Signing out or switching accounts clears remembered results.

  • Started recordings: Blocked-domain rules do not discard recordings that have started; those recordings are stored and transcribed normally.

  • Late linking: An ad-hoc recording cannot later be linked to a blocked calendar event, preventing automatic sharing to that invite's attendees. The recording keeps running.

  • Calendar notices: When Flow has confirmed a meeting is blocked, opening it or attempting to record adds no recording notice to its shared invite. Scheduled pre-meeting notices operate independently of blocked-domain rules; this is not a guarantee that no notice will appear.

  • Separate controls: Organization-wide Notetaker enablement, consent, transcript retention and note-sharing settings apply independently.

Where calendar notices are available, scheduled notices are Google Calendar only, never Outlook. They require the organizer's calendar write permission and an active event ending in the future, starting within seven days, with at least two attendees.


Still need help?

Contact Wispr support if saving still fails after corrections and a retry. Include your platform, the error message and what you tried.