Enforce account type limits for Editors when using Preview as

  • Describe Feature
    When I am editing or have published a workbook, I want to be able to use the Preview as… to see the options exactly as the end user will see them

  • What is the use case?
    Developing documentation and training for end users based on what they will be able to see/do instead of what I am able to see/do

  • How often would this feature be used?
    Regularly - every time a workbook is in development.

  • What is the impact of this feature on your organization?
    Currently has potential to cause confusion between creators and end users.

Hey @zwhitcomb, what differences are you seeing when you use the Preview as feature? Are you looking for the ability to log in as a specific user to test row-level security or something?

Hi @data_katrina - this specifically came up in reference to whether and what kind of files users could download from visualizations. View as a specific user would be cool, but just having accurate views for all account types would be great.