Currently, account views can either be private, made visible to all, or visible by profile.
When there are multiple teams and sub-teams in an org, this means the users have to have many views in their list that do not pertain to them, or we need to have a profile for every combination of views. It would be great if there was another way(sharing rules, public groups, etc.) to give access to views other than by profile.
While permission sets are more flexible for giving access in other parts of the application, I have seen account views be the deciding factor in having to use profiles over permission sets on multiple occasions. I have also seen where users have large lists of account views that do not pertain to them due to this limitation. For example, if you have several products, and some are shared across teams, and each product has several product metrics, and teams want views for different combinations of metrics for each product, the list of views can add up fast.
Please sign in to leave a comment.