WEBVTT

1
00:00:00.000 --> 00:00:02.113
Our training reviewer receives an update about

2
00:00:02.113 --> 00:00:04.841
a survey. This lesson turns a notification

3
00:00:04.841 --> 00:00:06.889
into a verified action on the actual

4
00:00:06.955 --> 00:00:09.483
file. The page shows recent file and

5
00:00:09.485 --> 00:00:12.926
account updates. Unread styling identifies items you

6
00:00:12.928 --> 00:00:14.791
have not marked as read; it does

7
00:00:14.793 --> 00:00:18.144
not rank engineering severity. Check the notification's

8
00:00:18.296 --> 00:00:21.025
subject, time and related item. A request

9
00:00:21.028 --> 00:00:23.355
for review is different from confirmation that

10
00:00:23.355 --> 00:00:25.889
a review has already been completed. A

11
00:00:25.978 --> 00:00:29.601
training notification refers to DEMO 001. Open

12
00:00:29.601 --> 00:00:31.782
the related file and inspect its current

13
00:00:31.791 --> 00:00:34.967
status before deciding what action is appropriate.

14
00:00:35.107 --> 00:00:37.469
Another authorised person may have acted since

15
00:00:37.481 --> 00:00:40.252
the notification was created. The current file

16
00:00:40.263 --> 00:00:42.473
record is more reliable for deciding the

17
00:00:42.473 --> 00:00:44.998
next step than an older message alone.

18
00:00:45.135 --> 00:00:47.985
Mark read changes your notification state. It

19
00:00:47.986 --> 00:00:50.907
does not co-sign, certify or resolve findings

20
00:00:50.908 --> 00:00:52.932
on the survey. The page shows the

21
00:00:52.937 --> 00:00:56.530
latest fifty notifications. Mark all notifications as

22
00:00:56.535 --> 00:00:59.528
read also includes older notifications, so use

23
00:00:59.533 --> 00:01:02.980
it deliberately. Pause here. Open the sample

24
00:01:03.167 --> 00:01:06.403
update, locate its related record, and explain

25
00:01:06.461 --> 00:01:09.056
what marking the notification as read does

26
00:01:09.071 --> 00:01:10.596
and does not change.