---
title: "Managing notifications in JXL"
canonical: "https://support.appfire.com/space/SUPPORT/3374186525/Managing%20notifications%20in%20JXL"
format: markdown
---
## Summary

This article explains how the JXL notification toggle interacts with Jira notification schemes and details the permission requirements for suppressing email notifications during issue updates.

## Use cases

### Case 1: Understanding the JXL notification toggle

You often need to perform bulk updates or frequent changes in JXL without triggering a high volume of email notifications to stakeholders.

**How it works**  
JXL does not send notifications directly. Instead, it interacts with Jira APIs to update issues. The **Notifications** toggle in the JXL status bar attempts to suppress the standard emails that Jira would normally send based on your project notification scheme.

### Case 2: Notifications sent by non-admin users

A common issue occurs when you deactivate the **Notifications** toggle, but emails are still sent to watchers or assignees.

**Behavior and limitations**  
The ability to suppress notifications is governed by Atlassian API restrictions:

- **Administrators**: Only users with Jira Administrator or Project Administrator permissions can successfully suppress notifications using the **Notifications** toggle.
- **Standard users**: If you don't have administrative rights, the toggle won't function. Jira doesn't allow third-party apps to silence notifications for non-admin users.

### Case 3: Controlling specific events (for example, Issue Closed)

If you want to prevent notifications for a specific event, such as **Issue closed**, regardless of whether you're an admin or a member of the Service Desk Team.

**Configuration requirements**  
It's not possible to selectively send/suppress specific event notifications from within the JXL app. Because JXL relies on the Jira API, you must configure the relevant notification scheme in Jira (and customer notification settings in JSM) so that no notifications are defined for that specific event. If Jira is configured to send a notification for an event, JXL can only attempt to send/suppress it for admin users; it can't override the underlying Jira project configuration for all users.

## How to suppress notifications during updates

If you have the required administrative permissions, follow these steps to silence emails:

1. In the JXL sheet, navigate to the status bar located below the issue table.
2. Click the **Notifications** toggle to set it to **Off**.
3. Perform the necessary issue updates or bulk changes.
4. Click the **Notifications** toggle to set it back to **On** once your changes are complete.

## Troubleshooting persistent notifications

If emails are still being sent despite the toggle being deactivated, verify the following:

1. **Check permissions**: Ensure you have the **Administer Projects** or **Administer Jira** permission.
2. **Customer notifications**: If it's a Jira Service Management project, navigate to *Project settings* > **Customer notifications**. Ensure that customer-facing alerts aren't overriding the expected behavior.
3. **Automation Rules**: Check whether any automation rules are configured that might cause this issue.
4. **Test outside JXL**: Reproduce the issue both inside and outside a JXL sheet (directly on the issue) to test whether it occurs and whether it's limited to JXL or happens in general.