Skip to content

Commit 89cdd31

Browse files
committed
new article
1 parent cfe8a4b commit 89cdd31

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

docs/programs/notifications.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
title: "Notifications"
3+
path: "/programs/notifications.html"
4+
id: "programs/notifications"
5+
---
6+
7+
Notifications enable you to keep track of activity that is going on in your program. The default setting is to receive notifications for all activity on all reports. This means that any action causing a change to a report will generate an email notification. All team members that are a part of your program as well as the hacker that found the vulnerability will receive a notification. If the action is for internal purposes, only your team members will be notified. Learn more on how to [manage your report notifications](/hackers/manage-notifications.html).
8+
9+
In addition to receiving notifications for activity on reports, you'll also receive notifications for:
10+
* Members leaving your program
11+
* Payments
12+
* Product changes
13+
* Policy updates
14+
* Program updates
15+
* Account changes
16+
17+
### FAQs
18+
19+
Question | Answer
20+
-------- | -------
21+
If a user self submits a report, does that specific user receive a New Report notification? | Yes. The user will receive a New Report notification for a report they submitted.
22+
Can I customize the notifications someone receives? For example, if the head of security just wants to know about new reports coming in, can they receive notifications just for that? | Sorry, we currently don't enable you to customize your notifications in this way.

0 commit comments

Comments
 (0)