Ability for column level security to show/hide shared formulas as it can with attributes

[dirons]

We support multiple applications of data within a model, as there is crossover between the applications; however, our customers have granularity to choose which application data with which they are allowed to see when they create new dashboards.

We use column level security for attributes today so that Application A author can only see table of data pertaining to application A while Application B author can only see tables of data pertaining to application B (note that a user can have both author rights and see all both application data).

We found that this does not pertain to Shared Formulas.  This now increases the "noise" that authors see, as they are seeing formulas for an application that isn't something they can readily use.

[DRay]

Hello @dirons,

Thank you for sharing your idea and providing details.

We encourage people to continue to vote and comment. We use community interest as one of the ways we prioritize efforts, so every vote and comment can help turn a request into a reality.

Thank you again for sharing and being part of our community!

[DrewGillow]

Additionally we find that shared formulas can be modified by anyone that has access to them.  We want dashboard designers to reuse the formulas but have data designers build the formulas.