You have created a LookML model and dashboard that shows daily sales metrics for five regional managers to use. You want to ensure that the regional managers can only see sales metrics specific to their region. You need an easy-to-implement solution. What should you do?
The best and easiest-to-implement solution is A. Create a sales_region user attribute, and assign each manager’s region as the value of their user attribute. Add an access_filter Explore filter on the region_name dimension by using the sales_region user attribute. This option is optimal because it directly leverages Looker's built-in features for row-level security (Access Filters) and user personalization (User Attributes), making it easy to implement, scalable, maintainable, and secure. Option B (Separate Explores) is inefficient and less maintainable. Option C (Separate Dashboards) does not provide data security and is easily bypassed. Option D (Separate Looker Instances) is extreme overkill, costly, and impractical. Therefore, Option A is the clear and correct choice for an easy-to-implement and secure solution.