diff --git a/docs/exam_ask.rst b/docs/exam_ask.rst
index 6584d7ac..509224e3 100644
--- a/docs/exam_ask.rst
+++ b/docs/exam_ask.rst
@@ -51,4 +51,35 @@ below. You can give a name for the grant and save the grant by using "OK" action
     
 You see all granted ASKs within the second list with the ASK hash and the name that was given on grant. All explicitly granted ASKs from that list are
 considered trusted for the exam. And future SEB client connection that connects with one of the ASKs from this list are granted. All SEB clients that
-are connecting to the exam with different ASK will apply to the heuristic check using the given "Numerical Trust Threshold".
\ No newline at end of file
+are connecting to the exam with different ASK will apply to the heuristic check using the given "Numerical Trust Threshold".
+
+Monitoring with App-Signature-Key
+---------------------------------
+
+When the App-Signature-Key check is enabled for an exam, SEB Server will check the ASK sent by a connecting SEB and mark it within the "Status" 
+column of the monitoring table. The App-Signature-Key check is processed in batch for newly connected SEB clients but not within the SEB connecting process
+itself. So when a new SEB client connection appears in the monitoring, the check will probably not be done yet for this new connection. This is marked 
+with "(No ASK Grant) tag after the status name. This will stay so when SEB has not sent an ASK and SEB Server is not able to apply the check on that
+SEB connection. If SEB has sent an ASK, the check will be processed within the next ASK update and the connection gets either granted or denied. Denied
+SEB connections are marked red and with the tag "- ASK Grant Denied" after the status name.
+
+.. image:: images/exam/examASKMonitoring1.png
+    :align: center
+    :target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/exam/examASKMonitoring1.png
+    
+In the detail view of a SEB client connection you can see this too and you are able to apply a grant for a denied APK afterwards by using the 
+"Grant App Signature Key" action from the right action pane. This will open a pop-up with the ASK hash and an input field for the name of the 
+grant. 
+
+.. image:: images/exam/examASKMonitoring2.png
+    :align: center
+    :target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/exam/examASKMonitoring2.png
+    
+.. image:: images/exam/examASKMonitoring3.png
+    :align: center
+    :target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/exam/examASKMonitoring3.png
+
+
+After you have granted a unknown ASK, the grant is also applied to the respective SEB connection and to all following SEB connections that
+come with the same ASK. The grants can be modified within the Exam view as described above.
+
diff --git a/docs/images/exam/examASKMonitoring1.png b/docs/images/exam/examASKMonitoring1.png
new file mode 100644
index 00000000..b1a27845
Binary files /dev/null and b/docs/images/exam/examASKMonitoring1.png differ
diff --git a/docs/images/exam/examASKMonitoring2.png b/docs/images/exam/examASKMonitoring2.png
new file mode 100644
index 00000000..c6027af7
Binary files /dev/null and b/docs/images/exam/examASKMonitoring2.png differ
diff --git a/docs/images/exam/examASKMonitoring3.png b/docs/images/exam/examASKMonitoring3.png
new file mode 100644
index 00000000..2c5d622c
Binary files /dev/null and b/docs/images/exam/examASKMonitoring3.png differ