Description
We are currently developing an internal operational dashboard using the Monday.com Vibe app framework. The app pulls data from several specific boards using the BoardSDK to display information such as survey jobs, system installations, and operational status for our team.
Our workflow requires creating new operational boards each year (for example 2026, 2027, etc.) to keep data organised. When these new boards are created, they receive new board IDs, which means the app’s existing board references will no longer point to the correct boards.
Because of this, the application would require code changes and redeployment each year simply to update the board IDs, even though the board structure and purpose remain the same. This creates an unnecessary maintenance burden and introduces risk that the app may stop working when boards are replaced.
What are you trying to achieve
We are trying to build a long-term operational dashboard that can continue working even when new boards are created as part of our yearly workflow.
Ideally, we would like one of the following capabilities:
The ability for an app to select boards dynamically (for example by name, workspace, or user selection).
A configuration layer or settings panel where administrators can map which boards the app should use.
The ability to update connected boards without redeploying the app.
This would allow organisations that rotate boards annually (for projects, operational tracking, etc.) to maintain stable apps without requiring yearly code changes.