Skykit Emergency Alerts displays urgent messages on Skykit-managed digital signage when those messages are triggered from a supported third-party emergency mass notification system. When an authorized user sends an alert through InformaCast or Alertus, Skykit receives the alert, overrides scheduled content on the appropriate displays, and restores regular programming when the alert clears.
This article provides a deeper explanation of how the integration works, how tenant-level delivery is handled, what Skykit does and does not do, and what to review before testing or troubleshooting.
Quick answer: Skykit does not replace your emergency mass notification system. Skykit extends the alerts you already send to one more high-visibility channel: your digital signage network.
At a glance
Use this table if you need a fast summary before reviewing the full article.
| Question | Short answer |
|---|---|
| What does Skykit Emergency Alerts do? | It displays emergency alerts from InformaCast or Alertus on Skykit digital signage. |
| What happens to scheduled content? | Scheduled signage content is temporarily overridden while the alert is active. |
| What happens after the alert clears? | Skykit automatically returns displays to their normal scheduled content. |
| Who triggers alerts? | Authorized users or automations in the third-party emergency mass notification system. |
| How are alerts targeted? | Alerts are delivered by Skykit tenant using the configured Tenant Code or endpoint mapping. |
| Can one building receive a different alert? | Yes, when that building is organized as its own Skykit tenant and configured with its own alert profile. |
| Are offline displays updated later? | No. Alerts are real-time and are not buffered for offline displays. |
Before you begin
Before operating any emergency alert integration with Skykit in a production environment, you must review the emergency alerts terms within your Skykit Master Services Agreement. Please contact support@skykit.com for a link to the relevant terms.
You should also confirm the emergency alert platform your organization uses, which Skykit tenants should receive alerts, and who on your team owns configuration in the third-party alert system.
| Requirement | Why it matters |
|---|---|
| Supported alert system | Skykit currently supports integrations with InformaCast and Alertus. |
| Tenant plan | The Skykit tenant structure determines which displays show an alert. |
| Tenant Codes or endpoint details | Skykit provides the values needed to connect the third-party alert service to the correct tenant. |
| Customer alert administrator | This person configures the third-party system using the information provided by Skykit. |
| Customer IT support | IT may need to confirm outbound HTTPS access, credentials, and network allowlisting requirements. |
| Test or drill plan | A planned test validates alert delivery without creating confusion during production use. |
How Emergency Alerts work in Skykit
Skykit Emergency Alerts connects your existing emergency communications workflow to the digital signage network you already manage in Skykit. The third-party emergency mass notification system remains the source of record for alert content, user authorization, trigger logic, targeting rules, and cancellation or expiration.
Skykit acts as the signage display layer. After Skykit receives a valid alert, it displays the message on the displays assigned to the mapped tenant. When the alert expires or is cancelled in the third-party system, Skykit removes the override and normal content resumes.
| System | What it owns | What that means for your team |
|---|---|---|
| InformaCast or Alertus | Alert content, trigger logic, user authorization, alert targeting, cancellation, expiration, and non-signage delivery channels. | Your safety and IT teams continue using the emergency alerting workflow they already know. |
| Skykit | Alert receipt, tenant mapping, display override, alert rendering, schedule restoration, and event review support. | Skykit extends the alert to signage without requiring a separate signage-only emergency alert workflow. |
What happens when an alert is sent
The viewer experience is simple: scheduled content is playing, an alert appears when triggered, and normal content resumes when the alert ends. Behind the scenes, Skykit and the third-party alert system coordinate the workflow shown below.
| Step | What happens | Primary owner |
|---|---|---|
| 1. Alert starts | An authorized user or automation starts an alert in InformaCast or Alertus. | Third-party alert system |
| 2. Alert is sent to Skykit | The alert system sends the message to Skykit using the configured alert profile, Tenant Code, endpoint, and credentials. | Third-party alert system |
| 3. Skykit receives the message | Skykit validates the request and maps the alert to the correct tenant. | Skykit |
| 4. Displays are overridden | Skykit replaces scheduled signage content with the emergency alert template. | Skykit |
| 5. Alert clears | The alert is cancelled or expires in the third-party system. | Third-party alert system |
| 6. Regular content resumes | Skykit removes the override and returns displays to normal scheduled content. | Skykit |
What Skykit does
Skykit acts as the signage delivery layer for alerts created in your third-party emergency mass notification system.
| Skykit capability | Description |
|---|---|
| Receives emergency alerts | Skykit receives alert messages from InformaCast or Alertus through the configured integration. |
| Overrides scheduled signage | Skykit temporarily displays the alert over playlists, campaigns, and scheduled content. |
| Restores normal content | When the alert clears, displays return to their scheduled content automatically. |
| Scopes alerts by tenant | The configured Tenant Code or endpoint mapping determines which Skykit tenant is affected. |
| Displays a readable alert template | Skykit renders the alert in a Skykit-hosted HTML template designed for digital signage visibility. |
| Supports event review | Skykit supports alert event logging and Proof of Play reporting capabilities. Availability may vary by product version and account configuration. |
What Skykit does not do
Skykit is not a replacement for InformaCast, Alertus, or your organization’s emergency notification program. The responsibilities below remain outside Skykit.
| Skykit does not | What to use instead |
|---|---|
| Create or trigger emergency alerts | Create and send alerts from the third-party emergency mass notification system. |
| Approve who can send alerts | Manage sender permissions in InformaCast, Alertus, or your organization’s access control process. |
| Send alerts to mobile, desktop, speakers, SMS, or email | Use your emergency mass notification system for non-signage channels. |
| Store alerts for offline displays | Treat signage alerts as real-time events. Offline displays resume scheduled content when they reconnect. |
| Wake displays from standby mode | Review display power settings with IT or facilities. Emergency Alerts does not currently wake screens through CEC. |
Supported integrations
Skykit currently supports integrations with InformaCast and Alertus. Use the configuration guide for your system when you are ready to set up the integration.
| Integration | Configuration guide |
|---|---|
| InformaCast | InformaCast Emergency Alerts Configuration Guide. |
| Alertus | Alertus Emergency Alerts Configuration Guide. |
Tenant-level delivery
Alerts are delivered to Skykit displays based on your tenant structure. During configuration, the third-party alert service is mapped to a specific Skykit tenant using a unique Tenant Code or Skykit-provided endpoint details.
When an alert is sent to that tenant mapping, all displays within the tenant show the alert at the same time. If different groups of displays need to receive different alerts, such as different buildings on a campus, each group should be organized into its own Skykit tenant and configured with its own corresponding alert profile.
| Deployment model | Recommended use | Targeting behavior |
|---|---|---|
| Single tenant | One building, one campus, or one shared display environment. | Alerts affect the displays in that tenant. |
| One tenant per building | Multi-building schools, healthcare facilities, manufacturing sites, offices, or public-sector locations. | Alerts affect only the tenant mapped to that alert profile. |
| Groups inside one tenant | Organizations that need more granular targeting inside a single tenant. | Additional review may be required. Contact Skykit Support to discuss available options. |
Alert templates
The visual layout of the alert on your screens is controlled by an HTML template hosted by Skykit. By default, integrations use a standard alert template designed for readability on digital signage.
Because emergency alerts must remain clear and legible, template changes should be handled carefully and coordinated with Skykit. During onboarding, Skykit can help review basic tenant-level presentation needs.
Offline displays and standby mode
Emergency Alerts is a real-time override. If a display is offline when the alert is sent, Skykit does not deliver that alert later when the display reconnects. After reconnecting, the display returns to its scheduled content.
Emergency Alerts also does not currently turn on a display that is in standby mode through Consumer Electronics Control, commonly called CEC. If your emergency readiness plan depends on screens being powered on and visible, review device power settings with your IT or facilities team before launch.
Audit logs, Proof of Play, and compliance review
Audit records may help organizations document that critical communications were sent and displayed. Skykit supports alert event logging and Proof of Play reporting capabilities for review and compliance documentation.
Because reporting features can vary by product version, account configuration, and implementation scope, confirm your audit requirements with Skykit before launch. This is especially important if your organization has specific retention, export, or API access requirements.
Compliance note: Skykit provides technical capabilities that may support compliance documentation. Skykit does not guarantee that a specific customer deployment automatically satisfies HIPAA, OSHA, Clery Act, FERPA, or any other regulatory requirement. Your compliance team should evaluate the full deployment, including policies, procedures, access controls, testing practices, and record retention.
Setup overview
Skykit Support coordinates setup with your organization’s IT and emergency alert system administrators. Setup usually includes tenant planning, credential sharing, Tenant Code or endpoint configuration, alert profile setup, network review, and a test or drill.
| Setup step | What happens | Owner |
|---|---|---|
| 1. Plan tenant targeting | Decide which Skykit tenant or tenants should receive alerts. | Skykit and customer stakeholders |
| 2. Provide configuration details | Skykit provides the credentials, Tenant Codes, or endpoint information needed for setup. | Skykit |
| 3. Configure Skykit settings | Skykit maps the integration to the correct tenant and alert template. | Skykit |
| 4. Configure the alert profile | The customer’s alert system administrator adds the Skykit-provided information in InformaCast or Alertus. | Customer administrator |
| 5. Confirm network access | Customer IT confirms the alert system can securely communicate with Skykit. | Customer IT |
| 6. Run a test | The teams send a test or drill alert and confirm the expected display behavior. | Skykit and customer stakeholders |
For multi-building deployments, plan to repeat configuration and testing for each building or tenant.
Network requirements
The network model is straightforward: the third-party emergency alert system must be able to securely communicate with Skykit using the configuration details provided during onboarding. Customer IT should confirm that the alert system can reach Skykit and that any required credentials are configured correctly.
| Requirement | What to confirm |
|---|---|
| Outbound connectivity | The emergency alert system can reach Skykit using the required secure connection. |
| Correct Tenant Code or endpoint | The Skykit-provided value is copied exactly into the third-party system. |
| Authentication | Credentials, when required, match the values provided during onboarding. |
| Targeting alignment | The alert profile points to the intended Skykit tenant. |
| Test mode | Test or drill mode is used when validating behavior before go-live. |
Testing before go-live
A successful test should answer three questions: Did the alert appear on the intended screens, did it avoid unintended screens, and did normal content return after the alert cleared?
| Test checkpoint | What success looks like |
|---|---|
| Alert appears quickly | The intended displays show the alert shortly after it is triggered. |
| Targeting is correct | Only the expected tenant, building, or location is affected. |
| Message is readable | The alert template is clear and visible on the display. |
| Content resumes | Scheduled playlists and campaigns return after the alert clears. |
| Event is reviewable | Available logs or reports show the test event as expected. |
Skykit recommends testing before launch and establishing a recurring test cadence with your safety and IT teams. A regular test helps confirm that configuration settings, network access, and display readiness remain healthy over time.
Troubleshooting common issues
If an alert does not behave as expected, start with the basics: Tenant Code or endpoint, authentication, network access, targeting, and display connectivity. These are the most common causes of setup issues.
| Problem | First thing to check | Why it matters |
|---|---|---|
| Alert does not appear | Confirm the Tenant Code or endpoint details in InformaCast or Alertus are correct. | A typo can prevent the alert from reaching the intended Skykit tenant. |
| Authentication fails | Confirm the configured credentials match the Skykit-provided credentials. | Incorrect credentials can cause the request to fail. |
| Wrong building is affected | Confirm the alert profile points to the correct tenant mapping. | Building targeting depends on sending the alert to the correct tenant. |
| No request reaches Skykit | Confirm the emergency alert system can securely communicate with Skykit. | The third-party system must be able to reach Skykit. |
| Users think a test is real | Confirm test or drill mode was used. | Test mode helps reduce confusion during validation. |
| Regular content does not resume | Capture the alert time, tenant, display names, and alert identifier before contacting support. | These details help Skykit investigate the event quickly. |
Frequently asked questions
What does Skykit Emergency Alerts do?
Skykit Emergency Alerts displays emergency messages from InformaCast or Alertus on Skykit-managed digital signage. The alert temporarily overrides scheduled content, and the regular signage schedule resumes when the alert clears.
Do I need to buy InformaCast or Alertus separately?
Yes. Skykit displays alerts from your emergency mass notification system, but it does not replace that system. Your organization needs an active supported emergency alert platform to create, authorize, and send alerts.
How quickly do alerts appear on screens?
Alerts are designed to appear quickly after Skykit receives the alert. Actual timing can depend on network conditions, integration configuration, and display connectivity.
Can I target one building instead of all displays?
Yes, if each building is configured as its own Skykit tenant with its own alert profile. Your emergency alert system administrator sends the building-specific alert using the configuration associated with that building’s tenant.
Can I target specific display groups inside one tenant?
The standard model is tenant-level targeting. If your organization needs group-level targeting inside one tenant, contact Skykit Support to review the available configuration options.
Can I customize the alert design?
Skykit can help configure basic tenant-level presentation settings during onboarding. More advanced behavior, such as different templates for different alert types, should be discussed during planning.
Will an alert interrupt scheduled campaigns?
Yes. The alert temporarily interrupts scheduled content while it is active. Scheduled campaigns and playlists are not deleted. When the alert clears, regular content resumes automatically.
What happens if a display is offline?
Offline displays do not receive historical alerts after reconnecting. Alerts are real-time only. When the display reconnects, it resumes scheduled content.
Will Emergency Alerts turn on a screen in standby mode?
No. Emergency Alerts does not currently wake displays through CEC. If screen power state is important for emergency readiness, review power settings with IT or facilities.
Does Skykit provide an audit trail?
Skykit supports alert event logging and Proof of Play reporting capabilities. Availability, retention, export options, and API access may vary by product version and account configuration. Contact Skykit to confirm whether the available reporting meets your organization’s requirements.
Is Skykit Emergency Alerts HIPAA, OSHA, Clery Act, or FERPA compliant?
Skykit provides technical capabilities that may support compliance documentation, but no single feature automatically makes an organization compliant. Your compliance team should evaluate the full deployment and determine whether it meets your obligations.
Who can trigger an alert?
Alert authorization is managed in the third-party emergency mass notification system. InformaCast or Alertus controls who can create, approve, and send alerts for your organization.
How do I get started?
Contact support@skykit.com. Include the emergency alert system you use, the Skykit tenants you want to enable, and the best contact for your emergency alert system administrator.
What to include when contacting Skykit Support
When you contact Skykit Support about Emergency Alerts, include enough detail to help the team identify the tenant, display, alert, and expected behavior.
| Information | Example |
|---|---|
| Skykit tenant | Main Campus or Building A |
| Affected displays | Lobby Display 01, Cafeteria Display 02 |
| Alert date and time | May 21, 2026, 10:30 AM Central |
| Emergency alert platform | InformaCast or Alertus |
| Alert identifier | Identifier from the alert message or third-party system event record |
| Expected behavior | Alert should display on all Building A screens. |
| Actual behavior | Alert appeared on one screen but not another. |
| Screenshots or photos | Attach images if they help show what appeared on screen. |
Related articles
Use these articles together when planning or configuring Skykit Emergency Alerts.
| Article | Use it for |
|---|---|
| Emergency Alerts Overview | A concise overview of the feature and setup path. |
| InformaCast Emergency Alerts Configuration Guide | Step-by-step setup for InformaCast. |
| Alertus Emergency Alerts Configuration Guide | Step-by-step setup for Alertus. |
References
Emergency Alerts Overview
[2]: https://support.skykit.com/docs/alertus-emergency-alerts-customer-configuration-guide
[3]: https://support.skykit.com/docs/informacast-emergency-alerts-customer-configuration-guide)