How to bulk manage Atlassian Teams notifications

[#1]

👋 Hi Atlassian Community,

We’ve made some changes that allow admins and users to manage your notifications in bulk.

We’ve introduced a way for users and org admins to manage and control these notifications directly via the Atlassian Teams GraphQL API, so org admins can perform bulk operations without flooding their inboxes and users can also better manage their inbox.

✨What’s new

As an org admin, you can now:

• Enable or disable specific Teams notifications for the entire org.

• Configure this yourself using the "setScopeNotificationConfiguration" GraphQL mutation so there’s no need to wait for a backend change from Atlassian.

As a user, you can now:

• Enable or disable specific Teams notifications

• Configure this yourself using the "setNotificationConfiguration" GraphQL mutation so there’s no need to wait for a backend change from Atlassian.

Once configured, notification behaviour for all Team operations will follow the rules you’ve set.

📌 When you might use this

Here are a few common scenarios:

• You’re migrating to Atlassian Teams and creating a large number of teams at once.

• You’re doing a cleanup of old or duplicate teams and don’t want to send a notification for every change.

• You’re running scripted or automated updates across many teams and want tighter control over the resulting notifications.

In each of these cases, you can adjust notification settings before you start, then restore them afterwards if needed.

🛠️ How it works

You’ll use the Atlassian Teams GraphQL API and the "setScopeNotificationConfiguration" (org admins) and "setNotificationConfiguration" (all users) mutation to view and update your notification settings.

1. Review the Teams GraphQL API docs

For more information surrounding GraphQL API, there’s team specific and Atlassian specific documentation found here:

• Introducing Teams GraphQL API

• GraphQL API
  

2. Authenticating with GraphQL

There are multiple ways to authenticate with the GraphQL API, depending on the client being used:

• OAuth: OAuth clients use https://api.atlassian.com/graphql

• Browser sessions and API tokens: Browsers and API tokens use https://{your-subdomain}.atlassian.net/gateway/api/graphql. Replace <your-subdomain> with your actual site name.

3. View your current notification configuration

Org admins can use the scopeNotificationConfigurations query to inspect your org’s existing settings for Teams notifications.

At a high level, as an org admin, you can:

• Fetch the current configuration to see what notification types are enabled for the org

• Identify which ones are tied to the bulk operations you’re about to run (for example, notifications when teams are created or deleted).

query FetchScopeNotificationConfigurationQuery {
team {
scopeNotificationConfigurations(ari: "ari:cloud:platform::org/<orgId>") @optIn(to: "Team-notifications") {
ari
enabled
notificationType
notificationChannel
}
}
}

All users can use the notificationConfigurations query to inspect your own existing settings for Teams notifications.

At a high level, as a user, you can:

• Fetch the current configuration to see what notification types are enabled.

query FetchNotificationConfigurationQuery {
team {
notificationConfigurations(ari: "ari:cloud:platform::org/<orgId>") @optIn(to: "Team-notifications") {
ari
enabled
notificationType
notificationChannel
}
}
}

4. Adjust notifications for bulk operations

Org admins can use the "setScopeNotificationConfiguration" mutation to update your org’s configuration:

• Temporarily disable notification types that would generate a lot of email during your bulk operation.

• Keep other important notifications enabled so users still receive what they need.

mutation SetScopeNotificationConfiguration {
team {
setScopeNotificationConfiguration(input: {
ari: "ari:cloud:platform::org/<orgId>",
notificationType: USER_REQUESTED_TO_JOIN_TEAM,
notificationChannel: EMAIL,
enabled: true
}) @optIn(to: "Team-notifications") {
ari,
notificationType,
notificationChannel,
enabled
}
}
}

You can:

• Apply a configuration and leave it in place if it suits your ongoing needs, or

• Revert or adjust the configuration after your bulk operation is complete.

All users can use the "setNotificationConfiguration" mutation to update your personal configuration:

• Disable notification types that would generate a lot of noise.

• Keep other important notifications enabled so you can reduce inbox noise.

mutation SetNotificationConfiguration {
team {
setNotificationConfiguration(input: {
ari: "ari:cloud:platform::org/<orgId>",
notificationType: USER_REQUESTED_TO_JOIN_TEAM,
notificationChannel: EMAIL,
enabled: true
}) @optIn(to: "Team-notifications") {
ari,
notificationType,
notificationChannel,
enabled
}
}
}

Once saved, the configuration you set will be used automatically for future operations so no extra steps from the Atlassian side are required.

➡️ What’s next

We’re exploring ways to make notification controls more accessible in the front end UI in the future. For now, the Teams GraphQL API is the supported way to manage bulk notifications for Atlassian Teams.

If you try this out, share any gaps or ideas for improving notification controls in the comments.