Read scorecards and KPI history, then post indicator values as approved steps
Connect BSC Designer and your scorecards become something you can ask questions about from the terminal. List documents, pull an indicator's value against its baseline and target, group history by month or quarter, and pull the Excel report. When a number needs updating, Luumen shows the change first and posts it after you approve. Authentication uses an API key.
10 tools: 7 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed BSC Designer run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — balance scorecard weights, set indicator values, update indicator — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to BSC Designer — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.