Input and Output Rules

Learn to create your own customized rules to detect any specific access control transactions and invoke actions.

Ankita Chakraborty avatar
Written by Ankita Chakraborty
Updated over a week ago

What are input and output rules?

Input and Output rules (also known as "Triggers and Actions") are the IF-THEN rules which govern the behavior of your Genea access control system. They are mechanisms to provide extensions to the inherent functions of the access controllers. They extend the basic operation and add the ability to provide customization, depending on the requirements of the application.

Triggers allow the application developer to create logic in the access controller that will make decisions based on pre-defined events and execute actions when those events occur. Actions are a “canned” list of commands that an operator could perform. The trigger defines the event for which a chain of actions is desired. The actions execute the list of commands. Together they provide event-based control and allow for customization of the system.

A trigger can be created to detect any specific transaction and invoke actions.
For example, a trigger can be specified to detect an access request, specific access activity, or changes of state in the door. Monitor point changes, time zone transitions, and even other triggers can trip a trigger.

And actions could be to unlock a door, delay 10 seconds, and then pulse a relay.

Currently, Genea supports local I/O rules which allow you to create triggers and actions on the sources attached to the same controller.

How to create an I/O rule?

1) Navigate to the 'I/O Rules' from your Genea admin dashboard. Click "+Add".

2) Enter the details. Name of the rule, select the controller and add a description. Click "Save".

Adding a trigger to an I/O rule:

1) Click "+Add", under the trigger section.

2) Enter the name of the trigger and an optional description.

Important Terms:

Schedule: Determines the time during which a source will trigger the action.

Source Type: The object from which the event that will trigger the sequence originates. Source types include Monitor Points, Access Control Readers, Control Points, Schedules, etc.

Source: Defines the element of the source type, For example, your main door reader will be the source for the source type access control reader or the panic switch that you have configured at Input 3 of Controller-1 will be the source of the source type monitor point.

Transaction: Determines the events that need to occur for the sequence to activate such as change of state of a monitor point or control point, etc.

Reason for the transaction: Defines the reason for the transaction such as access denied, access granted, alarms, secured, etc. All reasons are specific to the transaction.

3) Choose the required fields and click "Save".

Advanced configuration of triggers includes trigger variables, that can be used to further define the conditions under which the trigger will be tripped. Learn more on variables here.

Adding actions to an I/O rule:

1) Click "+Add", under the action section.

2) Enter the name of the procedure and an optional description. Click on add action.

3) Just like triggers, select the source type for the action and other related fields. Click "Save".

4) You can add multiple actions and on getting a trigger the list of actions will be executed in sequence.


  • If you delete any schedule or source that is associated with a trigger or action, then the corresponding trigger and actions will be deleted as well.

If you have any questions about this feature or have any other requests, please reach out to

Did this answer your question?