Update documentation for Critical Commanding and Command Authority (#2240)

* Update documentation on Critical Commanding and Command Authority

* Reuse existing images

* PR Feedback

Author: clayandgen

docs.openc3.com/docs/configuration/_command.md

@@ -22,6 +22,21 @@ When defining command parameters you can choose from the following data types: I
 
 <div style={{"clear": 'both'}}></div>
 
+## Command Authority (Enterprise)
+
+Command Authority can be enabled in the Admin Console under the Scopes tab and is enabled scope wide. Once Command Authority is enabled, individual users can take and release Command Authority which enables exclusive command and script access to that target for that user. Without taking Command Authority, users can not send a command or start a script under that target. Note, commands or scripts scheduled with Calendar or Autonomic are not affected by Command Authority.
+
+![Command Authority](/img/cmd_tlm_server/cmd_authority.png)
+![Command Authority in CmdTlm Server](/img/cmd_tlm_server/targets.png)
+
+## Critical Commanding (Enterprise)
+
+Critical Commanding can be enabled in the Admin Console under the Scopes tab and is enabled scope wide. Critical commanding requires a different user to approve critical commands. When Critical Commanding mode is set to NORMAL, HAZARDOUS and RESTRICTED commands need approval. When Critical Commanding mode is set to ALL, all manual commands will require approval. OFF is the default, and disables Critical Commanding.
+
+Here is an example of sending a HAZARDOUS command in Command Sender when Critical Command Mode is set to NORMAL.
+
+![Critical Command](/img/cmd_tlm_server/critical_cmd_sender.png)
+
 # Command Keywords
 
 COSMOS_META

docs.openc3.com/docs/configuration/command.md

@@ -22,6 +22,21 @@ When defining command parameters you can choose from the following data types: I
 
 <div style={{"clear": 'both'}}></div>
 
+## Command Authority (Enterprise)
+
+Command Authority can be enabled in the Admin Console under the Scopes tab and is enabled scope wide. Once Command Authority is enabled, individual users can take and release Command Authority which enables exclusive command and script access to that target for that user. Without taking Command Authority, users can not send a command or start a script under that target. Note, commands or scripts scheduled with Calendar or Autonomic are not affected by Command Authority.
+
+![Command Authority](/img/cmd_tlm_server/cmd_authority.png)
+![Command Authority in CmdTlm Server](/img/cmd_tlm_server/targets.png)
+
+## Critical Commanding (Enterprise)
+
+Critical Commanding can be enabled in the Admin Console under the Scopes tab and is enabled scope wide. Critical commanding requires a different user to approve critical commands. When Critical Commanding mode is set to NORMAL, HAZARDOUS and RESTRICTED commands need approval. When Critical Commanding mode is set to ALL, all manual commands will require approval. OFF is the default, and disables Critical Commanding.
+
+Here is an example of sending a HAZARDOUS command in Command Sender when Critical Command Mode is set to NORMAL.
+
+![Critical Command](/img/cmd_tlm_server/critical_cmd_sender.png)
+
 # Command Keywords
 
 

docs.openc3.com/docs/tools/cmd-tlm-server.md

@@ -34,15 +34,9 @@ The Targets tab displays all the targets and their mapped interfaces along with
 
 ![Targets](/img/cmd_tlm_server/targets.png)
 
-Command Authority is enabled in the Admin Console and is enabled scope wide. Once Command Authority is enabled, individual users can give and take Command Authority which enables exclusive command and script access to that target. Without Command Authority, users can not send a command or start a script under that target. Note, commands or scripts scheduled with Calendar or Autonomic are not affected by Command Authority.
+[Command Authority (Enterprise)](../configuration/command.md#command-authority-enterprise) allows individual users to take and release Command Authority which enables exclusive command and script access to that target for that user. Without taking Command Authority, users can not send a command or start a script under that target. Note, commands or scripts scheduled with Calendar or Autonomic are not affected by Command Authority.
 
-![Command Authority](/img/cmd_tlm_server/cmd_authority.png)
-
-The other option shown in the Scope List is the Critical Command Mode. Critical commanding requires a different user to approve each command. It can either be enabled on just HAZARDOUS and RESTRICTED commands or on all manual commanding.
-
-Here is an example of sending a HAZARDOUS command in Command Sender when Critical Command Mode is set to NORMAL.
-
-![Critical Command](/img/cmd_tlm_server/critical_cmd_sender.png)
+Command Authority, along with [Critical Commanding (Enterprise)](../configuration/command.md#critical-commanding-enterprise), can be enabled in the Admin Console under the Scopes tab.
 
 ## Command Packets Tab