With Policy Foundry, you set policies to monitor conditions and define the action taken when the monitored condition is met. You can monitor button clicks on a Smart Badge or Asset Tag 2, device battery levels, a device entering or exiting a location, and Portal Beam room occupancy and environmental readings such as temperature, humidity, and air quality.
How it works
When the condition set in a policy is met, the policy's action is triggered automatically. An action can send an email or a text message to notify staff, or send an event to an AWS Kinesis or Azure Event Hub stream. You can review policy events in the Policy Foundry activity log.
Policy Foundry access is granted by your administrator in the Users app. Viewing policies and the activity log, and setting up actions, may require different levels of access.
Setup overview
You set up two things to begin monitoring your Kontakt.io devices and events: an action, then a policy.
Step 1: Create an action. An action defines how a notification is sent. The action types are streams, emails, and text (SMS) messages. A policy can have one assigned action, but a single action can be assigned to one or many policies.
Step 2: Create a policy. A policy defines the monitored conditions and the action taken when the condition is met.
About policies
A policy defines the monitored conditions and the action taken when the condition is met.
As you prepare to add a policy, you'll decide the following for each one.
When the policy is active: always (24/7), specific days of the week, or during a specific date range.
What locations: Smart Location campuses, buildings, floors, and rooms.
What devices: all devices or specific devices.
What is the monitored condition: the event that triggers the policy's action.
What action: how the notification is sent. A policy is limited to one action.
You select one of your configured actions — a stream, email, or text message.
Limit the number of messages (limiters): set how many email or text notifications, or stream events, are sent in a given period of time (hours, minutes, or seconds). For example, you might limit notifications to 5 or fewer per hour.
Policy conditions
A policy monitors one of the following conditions.
Beacon Signals: a Button click — either the Default (Blue) button or the Second (Red) button — or a device Battery level.
Telemetry (Portal Beam): an environmental reading — temperature, humidity, or air quality.
Positions: a location event — a device entering or exiting a location.
Occupancy (Portal Beam): room occupancy count.
About actions
An action defines how a notification is sent. The action types are streams, emails, and text (SMS) messages. A policy can have one assigned action, but a single action can be assigned to one or many policies.
As you plan your actions, you'll need the following for each action type.
Email and text action requirements
For email and text message actions, you can customize what's included in the notification.
Email: recipients' email addresses, the email subject, event data (parameters), and the text included in the email.
Text messages: recipients' mobile phone numbers, event data (parameters), and the text included in the message.
Stream action requirements
A stream action sends events to an AWS Kinesis or Azure Event Hub stream.
AWS Kinesis stream: endpoint, secret key, stream name, region, access key, and forced partition key (optional).
Azure Event Hub stream: endpoint, shared access key name, shared access key, and event hub name.
