Currently, any dashboard created in CS is immediately visible to admins or provisioned users. There is no option to mark a dashboard as “Draft” or “Inactive.” The only workaround is adding “WIP” or “DRAFT” in the dashboard title. This does not restrict access, is easy to miss in dropdown menus, and often confuses end users.
The alternative is to adjust user permissions or bundles, which is not a good solution. This requires admins to repeatedly edit sharing logic, introduces risk of impacting unintended users or groups, and creates additional work to revert changes later. If forgotten, dashboards remain exposed or inaccessible to the wrong audiences.
Other Gainsight objects (such as programs, activities, playbooks, templates, rules, etc.) already support draft, active, and inactive/published statuses. Dashboards are an exception. This inconsistency complicates governance overhead and forces admins into risky workarounds for what should be a simple task.
As such, requesting to introduce dashboard statuses such as:
- Draft - visible only to the creator and admins, hidden from other users
- Active - (current behavior) visible to provisioned users
- Inactive - Retained, but hidden until reactivated or deleted
This would effectively reduce admin effort and eliminate the need for risky permission/bundle manipulation. In addition, it would:
- Provide a more consistent lifecycle approach across CS features
- Prevent unfinished or outdated dashboards from undermining end user trust in reporting
- Reduces dropdown and search clutter for end users
- Support improved administration/governance and change management by allowing testing, iteration, and archiving without unintended exposure
NOTE: I could have sworn this idea already existed, but our team has been unable to locate it in the community; please merge as appropriate if related idea exists.