Skip to content

Update Configuring-Email-Notifications.md #87531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
brianlee-expensify wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −0
Open

Update Configuring-Email-Notifications.md #87531

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/articles/travel/company-setup/Configuring-Email-Notifications.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,9 @@ These settings can help manage inbox volume or ensure backup approvers stay info
## Can I send notifications to shared email addresses or aliases?
Yes. You can use shared inboxes, email aliases, or distribution lists in the CC or BCC fields.

## Can I turn off notifications for reports that I approve for reimbursement?
No. To comply with regulations in several US states, Expensify is required to send you an email whenever you send money to another individual.
Comment on lines +70 to +71
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot Apr 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scope / single-workflow violation: This article covers configuring Expensify Travel email notification rules (booking confirmations, approval requests, flight updates, etc.). This new FAQ is about reimbursement payment emails, which is a separate workflow unrelated to travel notification configuration.

Per HELP_AUTHORING_GUIDELINES.md Section 1 ("Solve one primary workflow only") and Section 6 ("Avoid multi-feature coverage"), reimbursement email behavior should live in an article about reimbursements or payment notifications, not in a travel email notifications article.

Consider moving this FAQ to a more appropriate article (e.g., one covering reimbursement settings or payment notifications).


## Can I create multiple rules with different conditions?
Absolutely. Each rule can have different triggers and filters. You can create as many rules as needed.

Expand Down
Loading