KPI Management: visibility and confidentiality
Set the right confidentiality level on a KPI, and know exactly what happens to one you make invisible.
Making a KPI invisible doesn't touch its data. It only touches who's allowed to see it.
Settings โ KPI Management opens on a KPI list: Selected, Category, KPI, Id, Visible, Forecastable, Confidentiality, filterable by category and searchable by name. Visible is an eye icon per row โ open and orange when visible, crossed out and grey when not. Forecastable is a checkbox. Confidentiality holds four values: Basic, Confidential, Strictly confidential, and Custom Permissions โ the middle tier, "Confidential," is a genuine level between Basic and Strictly confidential, not a naming echo of the last one.
Each of the first three tiers carries a default meaning: Basic is operational data, visible to standard users by default; Confidential is strategic data, meant for senior roles or department leads; Strictly confidential is financial data, typically restricted to administrators and executives. Custom Permissions is the escape hatch โ it bypasses those defaults entirely for one specific KPI, which is why it has no Read/Write toggle of its own in the Groups matrix (13.3): the other three tiers are what a Group's permissions are actually set against, and Custom Permissions is assigned per KPI instead. A department head's Group, for instance, might Read Confidential but not Strictly confidential โ while one specific revenue KPI gets Custom Permissions to open it up for that same group as an exception.
Above the list, the page states its own warning verbatim: "These settings apply to all users in your company. Note that no data will be collected or displayed for invisible KPIs. Existing data will not be deleted." Read literally: making a KPI invisible is reversible and non-destructive. The historical numbers stay exactly where they are โ they simply stop being collected or shown to anyone until visibility is switched back on.
A View as company / View as user toggle sits above the list โ the way to check what a specific person actually sees, rather than trusting the admin-side settings alone.
Above the KPI list, Refresh KPI calculations and an Include Query Builder calculations checkbox force a recalculation; a separate ValueWorks Central Service section holds Get latest KPIs and benchmarks, pulling in new standard KPIs and benchmark data from ValueWorks itself rather than recalculating what's already there.

Takeaways
- โ Caution
Making a KPI invisible is non-destructive and reversible โ per the product's own wording, no data is collected or shown, and existing data is not deleted.
Confidentiality has four values โ Basic, Confidential, Strictly confidential, Custom Permissions โ and is a separate setting from Visible: one controls whether anyone sees it at all, the other controls which tier of user can.
Basic/Confidential/Strictly confidential map to default data sensitivity (operational/strategic/financial) and to a Group's Read/Write permissions (13.3); Custom Permissions overrides that default for one specific KPI.
View as user is how you verify what a specific person actually sees, rather than trusting the settings alone.
Refresh KPI calculations recalculates; Get latest KPIs and benchmarks pulls new ones in from ValueWorks itself.
Surfaces covered
- KPI Management
- KPI list (Selected, Category, KPI, Id, Visible, Forecastable, Confidentiality)
- Four levels: Basic
- Confidential
- Strictly confidential
- Custom Permissions
- View as company / View as user
- โ *"no data will be collected or displayed for invisible KPIs. Existing data will not be deleted."*
- Refresh KPI calculations
- Include Query Builder calculations
- Get latest KPIs and benchmarks
Also taught in the Academy
Module 13 ยท Settings and KPI Management
Take it as lesson 13.2 in Business Analyst & FP&A