Currently, Domo does not support column-level security. When sharing dashboards or apps with external users, there is no native way to hide specific columns within a dataset.
Current Workaround
- Create a separate, trimmed dataset via ETL
- Remove restricted columns
- Build external dashboards/apps on that dataset and not on original dataset.
Workaround Limitations
This leads to:
- Dataset duplication
- Additional ETL pipelines to maintain
- Increased governance and maintenance overhead
- Risk of inconsistencies between internal and external datasets
Requested Enhancement
Introduce column-level security controls at the dashboard or app level so a single governed dataset can be reused safely while restricting specific columns for external users.
This would simplify architecture, reduce operational overhead, and improve governance for partner-facing and embedded analytics use cases.
