You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/changelog/2022/march.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ date: "2022-03"
5
5
---
6
6
7
7
### Retesting Enhancement
8
-
We've update retesting time so the tester will now have 72 hours to complete retesting.
8
+
The tester will now have 72 hours to complete retesting once a retest is claimed.
9
9
10
10
### Program Hacker Matching Improvement
11
11
We’ve made improvements to our Invitation Engine, using program requirements and customer preferences to match hackers to opportunities, we provide our hacker community with much more personalized recommendations.
12
12
13
13
### Organization Settings Page
14
-
Customers with multiple programs can now manage users from a single page.
14
+
The Organization Settings page allows customers with multiple programs to manage users from a single page.
When you navigate to the credentials area, you will see an option to first download the template which will auto-populate some of the fields with information from your project. The **Asset ID** and **Asset information** are required in the CSV when using Asset-specific credentials. The **Assigned To column** can be left empty if there is no credential inquiry required, and any hacker can claim the credentials.
@@ -41,35 +41,35 @@ The hacker provides the information via the program’s Policy Page.
41
41
42
42
When it’s not necessary to request information from the hacker before creating credentials, you can immediately add credentials.
43
43
44
-
44
+
45
45
46
46
47
-
47
+
48
48
49
49
50
50
You will see a list of hackers that requested credentials and provided the needed information.
51
51
52
-
52
+
53
53
54
54
### Hacker Assignment
55
55
#### Claiming Credentials
56
56
57
57
When a program has an asset that does not require information from a hacker, the hacker can claim a credential via the program’s Policy Page. Once the credential is claimed by the hacker, the credential is automatically assigned to them.
61
+
62
62
63
63
#### Requesting Credentials
64
64
When a program has a credential inquiry, the hacker can’t immediately claim credentials. First, they need to request credentials and provide the necessary information.
65
65
66
66
Once the information is provided, the hacker is put on a waiting list until the Program Manager creates the credential and assigns the hacker to these credentials.
When creating a new credential and assigning the credential to a hacker via CSV upload. Once the credential is assigned the hacker is removed from the waiting list.
@@ -83,8 +83,6 @@ To assign credentials to hackers, you need to create a CSV file with credentials
83
83
84
84
When the credential is assigned to a hacker, the hacker is notified. If a hacker is not a whitelisted reporter in the program, an error is raised.
85
85
86
-
87
-
88
86
### Edit, Revoke and Delete Credentials
89
87
If you need to edit a credential, you can do this by clicking on the edit button on the right side of the table.
90
88
@@ -98,4 +96,4 @@ Credentials are also automatically revoked when a hacker leaves a program for an
98
96
#### Delete All Credentials
99
97
If you want to delete all credentials on all the assets, click on the Reset button. This action will delete both the assigned and unassigned credentials.
0 commit comments