
User Codes & Levels Of Authority (cont.)
Open/Close Reporting
Note: When adding a user, the system will only prompt for Open/Close report capability if the user is being added by the Installer. When a Master or Manager adds a new user, the new user's Open/Close report- ing enable will be the same as that of the Master or Manager adding the user. If Open/Close reports are required to be selectable by the Master or Manager, the Installer should assign two Master or Manager user codes: one with Open/Close reporting enabled, and one without Open/Close reporting.
Manager (Level | 2) | ¥ | Can perform all system functions (Arm, Disarm, Bypass, | |||
|
|
|
| etc.) programmed by Master. | ||
|
|
| ¥ | May create other users of the system below this level | ||
|
|
|
| (Manager cannot assign anybody a level of 0, 1, or 2). | ||
|
|
| ¥ | May change his own code. | ||
|
|
| ¥ | May add, delete, change operators. | ||
|
|
| ¥ | Open/close reporting of added users will be same as his | ||
|
|
|
| own (enabled/disabled as set by installer or master). | ||
|
|
| ¥ | May operate a partition. |
| |
|
|
|
| |||
Operator |
| ¥ | Operators can arm and disarm the system to the authority | |||
(Levels |
|
| assigned, but cannot add or modify any user code. | |||
|
|
| ¥ | May operate a partition with one of the three | ||
|
|
|
| OPERATOR authority levels A through C listed below. | ||
|
|
|
| Level | Title | Functions Permitted |
|
|
|
| 3 | Operator A | Arm, Disarm, Bypass |
|
|
|
| 4 | Operator B | Arm, Disarm |
|
|
|
| 5 | Operator C | Arm, Disarm only if armed with |
|
|
|
|
|
| same code |
|
|
| ¥ | Operator C (sometimes known as | ||
|
|
|
| cannot disarm the system unless the system was armed | ||
|
|
|
| with that code. This code is usually assigned to persons | ||
|
|
|
| who may have the need to arm and disarm the system at | ||
|
|
|
| specific times only (ex. a | ||
|
|
|
| system only when | ||
|
|
|
|
| ||
Duress | (Level | 6) | ¥ | The duress code is a means of sending a silent alarm to a | ||
|
|
|
| central monitoring station if the user is being forced to | ||
|
|
|
| disarm (or arm) the system under threat. This feature is | ||
|
|
|
| only useful if the system is connected to a central station. | ||
|
|
| ¥ | When the system's Auxiliary Voltage Triggers are | ||
|
|
|
| connected to another communication's media (Derived | ||
|
|
|
| Channel/Long Range Radio), note that duress is | ||
|
|
|
| signaled on the same trigger that signals silent panic | ||
|
|
|
| (whereas duress has a unique report when digitally | ||
|
|
|
| communicated). |
| |
|
|
| ¥ | The duress code is assigned on a partition by partition | ||
|
|
|
| basis and can be any code desired. | ||
|
|
| ¥ | When used, the system will disarm (or arm), but will also | ||
|
|
|
| send a silent alarm to the central station (if service is | ||
|
|
|
| connected). There will be no indication at the keypad | ||
|
|
|
| that an alarm was sent. |
| |
|
|
| ¥ | Duress Reporting Note: The Duress report triggering | ||
|
|
|
| logic activates on the 5th key depression (ex. OFF), not | ||
|
|
|
| the 4th key depression (last digit of code). Duress reports | ||
|
|
|
| will not be triggered if the 5th key is a [*], such as when | ||
|
|
|
| performing a GOTO or viewing capabilities of users. | ||
|
|
|
|
|
|
|
General Rules on Authority Levels and changes
The following rules apply to users when making modifications within the system based on the user code authority levels:
¥Master Codes and all lower level codes can be used interchangeably when performing system functions within a partition (a system armed with a user's temporary code can be disarmed with the Master Code or another user's temporary code), except the Operator Level C Code described above.
¥A user may not delete or change the user code of the SAME or HIGHER authority than which he is assigned.
¥A user (levels 0, 1 & 2 only) may only ADD users to a LOWER authority level.
¥A user may assign other users access to only those partitions to which he himself has access.