Creating Device Protocols for an Entity
Purpose of Hardware Protocols

Any enrollee who is assigned hardware should have a protocol assigned to them
A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps can include:
- Notifications to assigned officers
- Notifications to tenant admins
- Notifications to a contact
- Notifications to any email address
Accessing the Protocol Groups Tab

You must have Tenant Admin permissions in order to create hardware protocols
- Search for the desired entity by name
- Go to the "Protocol Groups" tab
- Select the "+Protocol Group" button
Creating the Protocol
- Enter a name for the protocol
- Naming the protocol something that indicates the intended enrollees it will be assigned to and/or type of hardware are helpful (Ex - "Low Risk - ShadowDevice")
- Select the type which indicates what type of hardware the protocol is for
- ShadoWatch
- ShadowDevice
- ShadowPhone
- ShadowCuff
- Active - defaults to yes
- Begin adding your protocol steps by selecting the +Protocol button

Protocol steps should be created for each alarm type
- Fill in the following fields:
- Alarm Type - designates which alarm you want to set this protocol step for.
- Grace Period - allows you to designate a buffer period so an alarm is not triggered instantly. If the alarm is resolved before the grace period ends, the alarm is ignored.
- Active - defaults to active. To make a protocol inactive disable this field.
- Auto-Resolve - defaults to being enabled. Allows for automatic alarm clearing when the issue that triggered the alarm is resolved. If this feature is disabled, all alarms will require to manual resolution by a user.
- Select the +Step button to enter protocol steps when an alarm is triggered. Your options are:
- Send email - send an email to any user, contact, tenant admin, or email address
- Send SMS - send a text to any user, contact, tenant admin, or email address
- Reboot device - will automatically initiate a reboot on the hardware
- Place call - places an automated call to the user using Shadowtrack's IVR system when an alarm is triggered
- Place call with delivery confirmation - places an automated call to the user using Shadowtrack's IVR system when an alarm is triggered. The user is required to acknowledge receipt of the notification.
- Send Push Notification- notification sent to the enrollee or victim via the EnrolleeApp alerting the recipient of the violation. (Only for EnrolleeApp users. This action will not occur if the enrollee or victim is not logged in to the app)
- You can repeat the same process to enter protocol steps when an alarm clears
- Select the action Type. Your options are:
- Automated - this is the default type. The action will be automated if this is enabled.
- Manual - the action must be completed manually by a user
- Select "Save"
- After adding a protocol step for each alarm, select save to create the protocol
Auditing Protocols
Protocol Audit Logs have been added to the ShadowtrackONE platform. This was added to track any changes made within Protocol Groups, listing the type of change as well as the user who initiated the change.
- At the Entity Level select the "Protocol Groups" tab. Above the list of Protocol Groups you will see a button labeled "Protocol Group Audit Logs". Selecting this button will allow the user to select a date, and all logs on and before that date will list beginning with the most recent. Each modification can be seen with the date/time of the change listed in the left column. The officer who initiated the change will be listed as well as all information relative to the change. The following can be seen within these logs.
Protocol groups created or deleted
Protocol alarms (within the group) added, removed, or modified
Protocol alarm steps added, removed, or modified
Protocol clear steps added, removed, or modified
Related Articles
Creating ShadowDevice Protocols for an Entity
Purpose of Hardware Protocols Any enrollee who is assigned hardware should have a protocol assigned to them A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps ...
Creating ShadowCuff Protocols for an Entity
Purpose of Hardware Protocols Any enrollee who is assigned hardware should have a protocol assigned to them A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps ...
Creating Interview Questions and Protocols
What Are Interview Questions and Protocols A Protocol should be assigned to the Enrollee so that someone is notified in the event of an Alarm. Questions are made of two parts, the primary question and the follow up question. Questions must be created ...
Creating a ShadoWatch Protocol for an Entity
Purpose of Hardware Protocols Any enrollee who is assigned hardware should have a protocol assigned to them A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps ...
ShadowVisit Protocols
What is ShadowVisit ShadowVisit is an in app feature that allows the enrollee to answer a series of questions upon arriving to the office for a scheduled appointment with their officer. Enrollees are able to check in and out using this feature, as ...