diff --git a/source/_integrations/alarm_control_panel.template.markdown b/source/_integrations/alarm_control_panel.template.markdown
index f3f31b4b3a4..ce9dcc8b7ba 100644
--- a/source/_integrations/alarm_control_panel.template.markdown
+++ b/source/_integrations/alarm_control_panel.template.markdown
@@ -96,11 +96,13 @@ panels:
           description: Defines an action to run when the alarm is armed to night mode.
           required: false
           type: action
+        code_arm_required:
+          description: If true, the code is required to arm the alarm.
+          required: false
+          type: boolean
+          default: false
 {% endconfiguration %}
 
-
-
-
 ## Considerations
 
 If you are using the state of a integration that takes extra time to load, the Template Alarm Control Panel may get an `unknown` state during startup. This results in error messages in your log file until that integration has completed loading. If you use `is_state()` function in your template, you can avoid this situation.
@@ -109,4 +111,4 @@ For example, you would replace {% raw %}`{{ states.switch.source.state == 'on' }
 
 ### Working without entities
 
-If you use a template that depends on the current time or some other non-deterministic result not sourced from entities, the template won't repeatedly update but will only update when the state of a referenced entity updates. For ways to deal with this issue, see [Working without entities](/integrations/binary_sensor.template/#working-without-entities) in the Template Binary Sensor integration.
\ No newline at end of file
+If you use a template that depends on the current time or some other non-deterministic result not sourced from entities, the template won't repeatedly update but will only update when the state of a referenced entity updates. For ways to deal with this issue, see [Working without entities](/integrations/binary_sensor.template/#working-without-entities) in the Template Binary Sensor integration.