Skip to main content

Q4 2026

14
Feature Request

Korbyt MCP (Model Context Protocol Server)

Hosted MCP server letting tenant admins and Korbyt internal teams connect AI clients (Claude, Cursor, ChatGPT) to a Korbyt tenant via a tenant-scoped API key for conversational access to media, players, content, schedules, users, analytics, and data adapters.

Max Guerrero
Feature Request

Integrate Okta SCIM Provisioning and Push Groups for Automated User Management

As an IT Admin, I want the Korbyt platform to support Okta SCIM provisioning and push groups so that user and role management is automated and aligned with enterprise identity governance policies. Acceptance Criteria: Given the IT Admin has connected their Okta instance to Korbyt, when SCIM provisioning is enabled, then user accounts are automatically created, updated, or deactivated based on Okta directory changes. Given an Okta group is mapped to a Korbyt role, when the group membership changes, then the user's Korbyt role updates accordingly. When a user is removed from all relevant groups or disabled in Okta, their Korbyt access is revoked. Admins can configure group-to-role mappings via the Korbyt admin UI. Korbyt provides audit logs of SCIM sync events and role assignments.

Ross Wilson
Feature Request

Ability to put "Maintenance" window on players - individual or by groups

i.e., a building/location is down for “maintenance”, unnecessary to receive alerts on the players in this building/location. Possibly by the Player Location map.

Amy Strouf
Feature Request

API Access and Exportable Report for Sonar-Based Content

Summary Request to enable API access or generate an exportable report for Sonar-based content (similar to what is available for Players) to support reporting and data analysis. Problem Statement Currently, there is no method via the Korbyt Anywhere API to retrieve Sonar-based content or associated metadata (e.g., names, views, metrics). Additionally, there is no export functionality available on the Sonar page, making data collection manual and inefficient. Desired Outcome - Ability to programmatically access Sonar-related data through the Korbyt Anywhere API. - Alternatively, the ability to export Sonar data (CSV/Excel) from the UI manually when needed. Use Case - The customer wishes to periodically generate internal reports involving Sonar content. - Though the process is infrequent, having an automated or exportable method will save time and reduce manual errors. - API access would also allow integration with internal monitoring/reporting tools. Desired Data Points (Examples) - Sonar Content Name - Associated Player/Device - Last Updated Date - Status (Active/Inactive) - Views or other engagement metrics (if available) Suggested Solutions 1. API Endpoint Enhancement: - Add a new endpoint under the Korbyt Anywhere API for retrieving Sonar content data. - Endpoint could support filters (by site, tag, status, etc.) 2. Manual Export Button: - Include an Export to CSV/Excel option on the Sonar page in the CMS. - Functionality similar to what is available for Player lists. Priority - Medium (not urgent, but a valuable quality-of-life feature) - Frequency of use: Low (periodic reports only) - Impact: Moderate (improves efficiency for institutional reporting) Notes - This is not a frequent operation but manual copy/pasting from the UI is the current workaround. - Client understands that this may not be immediately available and is open to future consideration or interim solutions.

A.Smith
Feature Request

Productize RS-232 support on Player edit pages for BrightSigns

Currently the way to deploy rs-232 controls on BrightSigns is clunky and hard for customers to manage or change once deployed (either via scriptlet or Layout scripting). As a business user, it would be nice to have UI features on the player page (like we support for KWPs). Requested commands: On/Off Input set to HDMI1 Mute On/Off It would be nice to build in the command sets for Sony Bravia, Samsung QM, LG, Sharp, NEC.

Ben
Feature Request

O365 Calendar Adapter – Support app-only authentication (Entra ID app registration with client secret)

Add an authentication option to the Office 365 Calendar Adapter that uses an Entra ID (Azure AD) enterprise application registration with the OAuth 2.0 client credentials flow (tenant ID, client ID, and client secret). This would replace the need for a licensed user or service account to authenticate. Current behavior The adapter authenticates as a user account that has delegated access to the room and resource mailboxes. Customers have to provision and license a service account, exempt it from MFA and Conditional Access, and manage password rotation. When that account’s password expires, gets locked, or is caught by a new security policy, calendar data stops flowing to signage and room panels without warning. Requested behavior Add an authentication type selector to the adapter: User Account (existing) or Application (Client Credentials). For Application auth, accept Tenant ID, Client ID, and Client Secret. Optionally accept a certificate as well. Use Microsoft Graph application permissions such as Calendars.Read (or Calendars.ReadWrite where booking or extend actions are needed) with admin consent. Support customers who limit the app to specific mailboxes through Exchange Online RBAC for Applications or an Application Access Policy. Show the secret’s expiration date and warn before it expires. Business justification Security and compliance: Enterprise customers, especially law firms and financial services, increasingly block or flag MFA-exempt service accounts. App-only auth is Microsoft’s recommended pattern for daemon and background integrations. Reliability: Fewer outages caused by password expiry, account lockouts, or Conditional Access changes. Cost and friction: Customers don’t need a licensed mailbox for the service account. It also shortens security review during implementation, which is currently a common source of delay. Competitive parity: Most workplace and room-scheduling platforms already support app registration auth. Acceptance criteria The adapter can read room calendars using only Tenant ID, Client ID, and Secret, with no user credentials. Access can be scoped to specific mailboxes, and the adapter fails gracefully on mailboxes outside that scope. Existing user-account configurations are unaffected. The secret’s expiry shows in the UI and an alert is raised before it expires. Customer impact: BLG has requested this most recently

Ben
Feature Request

Support Screen Control (RS232/CEC) for BrightSign Players via Player Groups

A scheduled nightly power-off and morning power-on via RS-232 for ~180–190 displays, driven by Korbyt players (This request is on Dell PCs) The goal is energy management. Right now every display runs 24/7 because nothing can turn them off. Need to be able to schedule this from a group level to large swaths of players can be scheduled to turn off during off hours at the University Campus

Nate Fullington
Feature Request

Role-based freeform tagging

Title: Allow freeform tag creation by role when Tag Administration is enabled Current behavior. Tag Administration is a single tenant-wide switch. Off, and any user can create tags freely. On, and nobody can, so every tag has to be pre-created by an administrator in Tag Manager before anyone can apply it to content. There is no middle setting. The problem. These two states serve opposite needs and most enterprise customers need both at once. Structural tags that drive routing must stay locked, because an accidental variant silently breaks content delivery. But ad hoc tags used for organizing and retrieving content, campaign names being the common case, need to be created by the people doing the work. Forcing those through an administrator makes the queue the bottleneck, and the usual outcome is that customers turn Tag Administration off entirely and accept tag drift. Requested change. Make freeform tag creation a role-level permission rather than a tenant-level switch. Proposed model when Tag Administration is enabled: RoleFreeform tag creation Tenant Administrator Allowed Administrator Allowed Content Approver Allowed Contributor Predefined tags only Read Only Not applicable Launchpad only Predefined tags only

Ross Wilson
Feature Request

Serial number on the player detail page

Surface the full device serial number as a copyable field on the player detail page Problem. The player detail page shows Provision Code and Player Name but never the serial number as a labeled, copyable field. On BrightSign the provision code is the serial plus a two-character suffix, and the Player Name carries the serial with the delimiters stripped. So the data is on the page twice and usable neither time. Example from the customer tenant: Provision Code USF52N-002740-8S, Player Name BrightSign-USF52N002740, actual serial USF52N002740. Impact. Every BrightSign fleet workflow keys off the serial: cross-referencing BSN Cloud, opening BrightSign support tickets, RMAs, asset inventory reconciliation. The customer's current workaround is copying the last six digits and using them as a search string. Requested change. Display the full serial as a labeled field on the player detail page with copy to clipboard. Include it in the provisioning export if it isn't already.

Ross Wilson
Feature Request

Use Lat/Long to set timezone

Under a player’s details and Custom Properties, you can change a player’s (BrightSign) timezone manually. If the location data is provided including Lat/Long, have the system automatically set the player’s timezone.

Tim

Q1 2027

4
Feature Request

Partner Portal

Deliver a partner portal to enable Korbyt Partners to manage their tenants from a single admin screen.

Max Guerrero
Feature Request

Ability to make parent folder read only

Can we have the option to make a parent folder ready only for user groups in all the storage modules (Media Manager, Playlists, and Layouts)? We have users that are not using the correct folder setup for them and are continuing to upload content directly into parent level folders. Our folder structure is like: root\northamerica\facility Users are supposed to put content in their facility folder but because the system allows them to upload it directly under the top level folder(s), there is no easy way to prevent this as we add more and more users and devices into our environment. Its getting very cluttered and hard to maintain.

Dylan Pyles
Feature Request

Enhance the OAuth 2.0 request when using the External URL element

Issue: Korbyt's External URL element hardcodes the Files.Read scope into every OAuth 2.0 request it sends, regardless of provider or target resource. This works fine when the target is a Microsoft Graph resource (SharePoint, OneDrive, Excel embeds), but breaks for any non-Graph OAuth target, since Entra rejects the request with AADSTS65005 ("scope doesn't exist") when the app registration on the receiving end has no Files.Read scope defined. Update the external URL element to support OAuth2.0.

Levi Stogsdill
Feature Request

Jump to specific pages throughout the Korbyt Application

Throughout the Korbyt environment, there are areas that have multiple pages that go beyond the 4 initial pages visible in the quick-click list: As a user, it’d be very helpful to be able to jump to a specific page in the menu to quickly and efficiently get to the section of a list. This is true for all areas - Players and Groups, Playlists, Custom Integration datasets, and more.

Joel Fajardo

Q2 2027

1

Q3 2027

No issues scheduled for Q3 2027