LookML Flashcards
(186 cards)
1
Q
What are the three types of files a LookML Project contains?
A
- Models
- Views
- LookML dashboards
2
Q
In what file type are “Explores” defined.
A
Models
3
Q
What 5 types of fields can a view contain
A
- Dimensions
- Measures
- Parameters
- Filters
- Field Sets
4
Q
Describe the difference between an “object” and a “file”
A
A file ends with .lkml or .lookml
An object is something defined with code (e.g., “view: foo {}”
5
Q
There are object models? T / F
A
False. There are only model files, unlike views, which can be a file or an object.
6
Q
Should an include refer to the object name or the file name?
A
File name. E.g., “include: /views/your_mommas.view.lkml”
7
Q
Is every file in Looker completely separate from the files?
A
Yes
8
Q
Are there cases where it’s acceptable to have a view not match the file name?
A
Yes. For example, if we want to include a group of files, we may include the group name. E.g.,
view_name = "bobs" view_file_name = "people.bobs.view.lkml"
9
Q
What happens if you include a model inside another model?
A
The LookML validator will throw an error about the connection being defined twice.
10
Q
What are the two things “Explore” refers to in Looker?
A
- An “explore” is a LookML object that lives inside a model file. E.g., “explore: bobs_burgers {}”
- An “explore” is an interactive page where the standard user can SQL queries by clicking on fields in the UI.
11
Q
What is the reason you don’t want to make your explore (object) contain too many views? What is the reason you don’t want to break explores apart too much? (too few views)
A
The user will be overwhelmed by the number of fields and options inside an Explore.
If you make Explores for every view, the user will be overwhelmed knowing what Explore to choose.
Balance.
12
Q
Should you join a view you -think- you may need?
A
No. Only join what you will use. This saves clutter in the UI.
13
Q
What is the difference between a “model” and “project”?
A
Models are LookML files that contain Explores Projects are collections of LookML files. A Project “owns” a model.
14
Q
Can a project contain multiple models?
A
Yes.
15
Q
Is the following valid SQL for a measure?
${orders.total} + ${bakesales.total}
Assuming both of these fields are measures of type: sum.
A
Yes. If the measure wrapping them is type: number. This tells Looker to add these fields, but not to aggregate them (i.e., not include the field in the GROUP BY).
16
Q
If you add a measure as a filter and set it to > 0, what appears in the SQL to fulfill the filter?
A
Something like,
HAVING field_name > 0
17
Q
When you make a change in development mode, what other users can see this change?
A
None. Unless they sudo you.
18
Q
If you change the “Project Settings” in development mode, which users are impacted?
A
All users. The “Project Settings” impact the entire project–not just your development branch.
19
Q
Is “Production Mode” LookML read-only? T / F
A
True.
20
Q
What happens if you have a view which extends another view, neither view has an sql_table_name defined?
A
The LookML parser assumes the table name matches the view name. If it does not, it will through a DB error.
21
Q
dimension: view:, type:, sql: are all examples of what?
A
LookML parameters.
22
Q
The ${} is referred to as what?
A
Substitution syntax. It replaces anything inside ${} with a corresponding object.
23
Q
What is the purpose of using substitution syntax?
A
Reduces the number of changes which need to be made throughout a model.
24
Q
Why is it important to use the substitution operator? I.e., ${}?
A
- It makes LookML code more reusable.
- It simplifies code maintenance.
- It removes the need for the same SQL code to be written multiple places (DRY).
25
What does ${TABLE} become?
The table defined in the sql_table_name. Or, the name of the view if the sql_table_name parameter is not defined.
26
If you create a dimension_group called "start" with the type "time" and timeframes [raw, time, date, month, year], how would you refer to the month?
${start_month}
27
If you create a dimension_group called "start" with the type "time" and timeframes [raw, time, date, month, year], which of these fields would not show in the UI?
${start_raw} would not show in the UI.
28
T / F -- A dimension_group of type: time automatically adjust for user's timezone?
True
29
What are the required parameters of a dimension_group of type: duration? (other than the type).
* sql_start:
* sql_end:
* intervals: []
30
Given the following dimension_group:
```
dimension_group: created {
type: duration
interval: [
day,
week,
month,
year
]
sql_start: ${created_date}
sql_end: ${created_date}
}
```
How would you refer to the number of days in a custom filter?
The interval part goes first:
${days_created}
31
Consider the following dimension:
dimension: in_house {
type: yesno
sql: ${TABLE}. in_house ;;
}
What will show in the UI when
1. in_house = 1
2. in_house is NULL
3. in_house = "no"
4. in_house = 0
1. in_house = "Yes"
2. in_house = "No"
3. in_house = "Yes"
4. in_house = "No"
32
Consider the following dimension:
dimension: age_tier {
type: tier
tiers: [0, 30, 50]
sql: ${TABLE}. age ;;
}
What is the category label for someone
1. ${TABLE}. age = -1
2. ${TABLE}. age = 30
3. ${TABLE}. age = 49
4. ${TABLE}. age = 55
1. "Below 0"
2. "31 to 49"
3. "31 to 49"
3. "50 or Above"
33
Consider the following dimension:
dimension: age_tier {
type: tier
tiers: [0, 30, 50]
sql: ${TABLE}. age ;;
}
What parameter and value should be added to have the values show as numbers?
style: integer
34
Consider the following dimension:
dimension: age_tier {
type: tier
tiers: [0, 30, 50]
sql: ${TABLE}. age ;;
}
Could you add both a style and value_format parameters?
Yes.
35
What are the 5 built in map_layers which Looker provides?
* countries
* uk_postcode_areas
* us_states
* us_counties_fips
* us_zipcode_tabulation_area
36
What are the required parameters for a dimension of type: location?
* sql_latitude
| * sql_longitude
37
What format does a custom map layer file need to be in?
TopoJSON
38
If no type is provided to a dimension, what type will it be?
String.
39
You have a sale_price dimension and a cost dimension. If you wanted to create a profit dimension that subtracts cost from sale_price, what type would you specify for this new dimension?
number
40
When should a type: count_distinct be used on a measure?
When counting a unique field which is not the primary key in a table.
41
What is wrong with this measure definition:
measure: order_items {
type: count
sql: ${order_items} ;;
}
The measure does not need to include sql: parameter, as the primary key will be used to perform a count.
42
What is wrong with this measure definition:
measure: order_items {
type: count_distinct
}
A measure of type count_distinct must include a sql: parameter, as it will be used to perform the distinct count.
43
What are the 4 types of formatting for the value_format_name parameter?
* ID (id)
* Decimal (decimal_0, decimal_1, decimal_2, decimal_3, decimal_4)
* Currency (usd, usd_0, gbp_0, gbp, eur, etc.)
* Percents (percent_0, percent_1, etc)
44
T / F -- Can a user access this dimension?
dimension: order_id {
hidden: yes
sql: ${order_id} ;;
}
Yes. The "hidden:" parameter only impacts whether the field will show in the UI, it is still accessible in custom filters, custom dimensions, etc.
45
How many database connection can a model file have?
One.
46
T / F -- Looker production mode is read-only
True
47
What is the keyboard shortcut for toggling dev mode?
CMD / CTRL + SHIFT + D
48
What are the two things a model file defines?
1. Database connection
| 2. Explores
49
What is one of the primary advantages of LookML dashboards?
They are defined LookML and therefore version controlled.
50
How do you define navigation in a Looker document file
```
At the front matter of the document use YAML to define it as a navigation enabled document.
---
navigation:
- document_one
- document: document_two
label: Customized Label for Document Two
- section: My Section Name
- document_three
---
```
51
What all can be defined in a manifest file?
* project imports (remote or local)
* model localization settings
* LookML constants
* Extension definitions
* Custom visualization definitions.
52
Where should the manifest.lkml file be located in the project directory?
It can -only- be stored in the root directory.
53
When is a manifest_lock.lkml file added?
When a remote dependency is added to the project.
54
What is the appropriate (but not required) file extension for an explore file?
.explore.lklml
E.g., my_explore.explore.lkml
55
Is LookML case sensitive.
Yup!
my_dimension != My_DIMENSION
56
When you move a LookML file from one folder to another in the IDE, what does its Git history look like?
It is blank. When moving a file, the IDE deletes it and creates a new file in the new directory.
57
Can you bulk delete views not in a directory?
Yes, the IDE has a bulk deletion option.
58
Given the path "/views/business_views/new_views"
How would you create an include statement to include all .lkml files in the "/views/business_view" and /views/business_views/new_views"
include: "/views/**/*.lkml"
The double asterisk is a recursive wildcard.
59
What does Looker cache?
Looker caches the results of every query run. Queries can be run from explores, Looks, dashboards, and schedules.
60
Does Looker cache dashboards?
No. But it does cache the queries on a dashboard.
61
What is the default cache duration?
1 hour, unless overridden by a caching policy.
62
What happens if the Looker cache fills up?
The oldest results will be dropped to make way for new results.
63
What is the recommended way to control caching behavior?
Looker recommends to use Datagroups.
64
Other than "label" and "description," what are the other two parameters: on a datagroup.
1. max_cache_age:
| 2. sql_trigger:
65
T / F -- Datagroups can contain a description?
True. The option description: should explain the datagroup's purpose.
66
How many rows can the sql in a sql_trigger parameter return?
One.
67
What is the result of a sql_trigger compared to determine if it is triggered?
The sql_trigger results are compared to the previous results. They must be different to trigger.
68
What timezone do sql_trigger dates use?
They are not adjusted by Looker; they will be the timezone set in your database.
69
How does sql_trigger_value: work in dev mode?
Any sql_trigger_value becomes replaced with persist_for: "24 hours" no matter what setting.
70
What are the 3 intervals allowed in a max_cache_age?
* seconds
* minutes
* hours
71
What's the difference between max_cache_age and persist_for when assigned to a PDT?
max_cache_age only invalidates the results (deletes the cache), it does not cause the PDT to rebuild.
persist_for invalidates the PDT and rebuilds it.
Pro tip, if you define a datagroup with only max_cache_age, a derived table assigned that datagroup will persist, but because there is no trigger assigned, the PDT will sit in the scratch schema indefinitely.
72
What parameter is used in an explore: to apply a datagroup caching policy?
persist_with:
E.g.,
explore: my explore {
...
persist_with: name_of_datagroup
73
How can you control the default caching policy for all explores?
Define a datagroup for the caching policy and add persist_with: at the model level. This should cascade to all explores.
74
What is the default interval which a sql_trigger runs at
Every 5 minutes. It can be overridden in the connections.
75
Given it's 18:00 UTC (0600 database time), when would this PDT rebuild?
derived_table: my_pdt {
sql_trigger: SELECT EXTRACT(day FROM DATEADD(hour, -3, GETDATE()))
...
3 AM.
76
What's wrong with this PDT trigger?
derived_table: my_pdt {
sql_trigger: SELECT EXTRACT(minute FROM DATEADD(hour, -3, GETDATE()))
...
The minute is being extracted, therefore, it will fire every hour.
77
What does suggest_persist_for control?
How long a filter dimension lookup query is persisted for
78
T / F -- a user who manually clicking on "Clear Cache and Refresh" causes any "persist_for" countdown to be reset?
True.
79
If any explore is dependent on an ETL should persist_for or datagroup be used?
datagroup. The datagroup parameter can tie together a check if an ETL has completed with sql_trigger: SELECT MAX(id) ;; and max_cache_age: "24 hours"
If the explore had a simple persist_for: "24 hours" parameter set, then it may be reset by a user hitting "Clear Cache and Refresh"
80
A persist_with can apply a datagroup to...
* An explore
| * A model
81
What are 4 common reasons to use derived tables?
1. Dimensionalizing a measure.
2. Building subqueries or CTEs
3. Performance.
4. SQL which can't be modeled (e.g., "UNION"s)
82
What are some SQL set operations which require a DT / PDT?
1. UNION
2. UNION ALL
3. EXCEPT
4. INTERSECT
5. MINUS
83
Are WINDOW functions executed pre- or post- aggregation
Post.
84
What are the 3 parameters which can be added to a derived table (DT) to persist it (PDT)?
1. persist_for
2. sql_trigger_value
3. datagroups
85
Why does Looker not recommend using "persist_for" for PDTs?
Often, the objective of PDTs is reduce user wait. The first user running a query on the PDT will have a horrible experience.
86
What are the "repear" and "regenerator"?
The repeat is the Looker tool which runs every 5 minutes and check if PDTs and cache need to be dropped.
The regenerator runs every 5 minutes and determines which PDTs need to be dropped
87
In most SQL dialects, what SQL does a Native Derived Table (NDT) generate?
It is converted into a CTE, based on the explore joins defined on the explore from which the NDT is based.
88
What is one big advantage of Native Derived Tables ( NDTs)?
They have the parameters bind_filter: and bind_all_filters, which inject the user's filter into the CTE.
89
How often will a PDT rebuild with sql_trigger: SELECT 1;;?
Never. Since 1 never changes, it will never rebuild.
90
From admin level, what 3 functions combined determine what a user can do?
1. Roles.
2. Permission sets.
3. Model sets.
91
What 2 components make up a user "Role"?
1. Permission sets
| 2. Model set
92
On an admin level, what controls what -data- a user can access?
Model Set(s).
93
On an admin level, what controls what -actions- a user can make?
Permission Set(s).
94
What are the 5 default Permission Sets?
1. Admin
2. Developer
3. User
4. User who can't view LookML
5. LookML dashboard user
95
Define the "Developer" default Permission Set.
The user can develop and deploy, but has no Admin level access.
96
Define the "User" default Permission Set.
Can't develop or deploy, but can view LookML
97
Define the "User who can’t view LookML" default Permission Set.
Can't view LookML, but can explore
98
Define the "LookML dashboard user" default Permission Set.
Can't explore, can only view Dashboards
99
From an admin perspective, define a "Permission."
A permission is an enablement which can be toggled per "Permission Set." E.g., "see_looks", "save_content", etc.
100
What can a "Role" be assigned to?
A "Role" can be assigned directly to a "User" or a "Group," which contains users.
101
Can an admin sudo any user?
They can not sudo admins, but otherwise can sudo all users.
102
What are the two things "Groups" makes easier to manage?
1. Space Access
| 2. User Permissions.
103
Can a user be assigned two two groups?
Yes. Their permissions will be based on a union of both groups.
104
What is "content" in context of permissions?
Looks and Dashboards.
105
Where are the two places you can a user's folder permissions?
Inside a folder, click the cog at the top right and assign a "User" or "Group" and what level of access. I.e., "View" or "Manage / Edit".
OR
In the Admin -> Content Access.
106
When creating a folder inside a folder, what "Content Access" (Users and Groups) will the folder have?
It will inherit the parent folder's Content Access settings.
107
T / F -- Are admins the only ones who can change a folder's access settings?
No. Any user with the "manage_space" permission can make changes to a folder' "Content Access"
108
What is a "Closed System"?
1. The "All Users" group is removed.
2. All user folders are made "Private" by default. Though, users can still share content in their folder with other members of their groups.
3. Ensures Looker users can only view other users in their group.
109
Can you name all of the instance wide permissions?
1. create_table_calculations
2. save_content
3. create_alerts
4. follow_alerts
5. deploy
6. support_access_toggle
7. manage_spaces
8. manage_homepage
9. manage_models
10. embed_browse_spaces
11. see_queries
12. see_logs
13. see_users
14. sudo
15. see_schedules
16. see_system_activity
110
What are the two types of permissions?
1. Model specific.
| 2. Instance wide.
111
T / F -- I can make it so a user can develop one one model, but only view another model.
False.
Since "develop" and "see_lookml" permissions will be given a user for all models.
112
If the plan is to white-label and allow customers to write LookML, how should an admin control so users can only develop certain LookML models?
The client asks, "How do I control which models a user or group can edit and develop on?"
The initial thought is: Simple, create a role that the has the `develop` and `see_lookml` permissions (both are model-specific permission) and then grant this role the specific Model Set access. Done and done right?
Well, the "expected" unexpectedness here is that if you have a single Project with multiple models, granting `develop` and `see_lookml` on a single model will allow this user to develop on all models if they can see all models. Interesting right? As mentioned, this is in Docs at a high level.
The important take away is if a customer wants to break out and separate `develop` permissions, the best option is to create completely separate Projects.
113
What are the two primary applications of User Attributes?
Use with
1. access_filters
2. access_grants
114
Which of these is an access_grant and access_filter?
xxxxx: this {
user_attribute: my_customers
allowed_values: [ "51" ]
}
xxxxxx: that {
field: customer_id
user_attribute: my_customers
}
access_filter: that {
field: customer_id
user_attribute: my_customers
}
access_grant: this {
user_attribute: my_customers
allowed_values: [ "51" ]
}
115
Describe the difference between "access_grant" and "access_filter"?
"access_grant" filters columns. They are applied to joins, fields, or can be referenced in "required_access_grants". It limits what fields a user can access.
"access_filter" filters rows. It is added directly in an explore: object. It creates a where clause restricting what data user can access.
116
What parameter should one use to restrict the fields a user can access based on their user_attributes? Where should it be applied?
access_grant.
It can be applied by adding it directly to a dimension or join. Or, defined in a file and then applied to joins or fields using the required_access_grant: parameter.
117
What parameter should one use to restrict the -rows- (data) a user can access based on their user_attributes? Where should it be applied?
access_filter.
It should be declared directly in an explore: object.
118
T / F -- You can apply multiple access_grants to fields and joins.
True.
E.g.,
access_grant: can_view_financial_data {
user_attribute: department
allowed_values: [ "finance", "executive" ]
}
access_grant: can_view_payroll_data {
user_attribute: view_payroll
allowed_values: [ "yes" ]
}
view: payroll {
required_access_grants: [can_view_financial_data, can_view_payroll_data]
}
119
If a user is given an Explore with content which is restricted for the user with an access_grant, what will the user see when opening the Explore?
The Explore will contain warnings at the top stating there is (are) field(s) which are not accessible by this user.
120
Given a dimension which has an access_grant applied the user -does- have access to, but the dimension is contained in a view with an access_grant the user does not have, does the user have access to the dimension?
No. The access_grants are additive.
121
What are the 4 places where you can apply a "required_access_grants:" parameter?
1. Inside an explore
2. Inside a view.
3. Inside a join.
4. Inside a field (dimension, measure, etc.)
122
The sql_always_where: creates SQL in what part of the output query?
The "WHERE" clause.
123
The sql_always_having: creates SQL in what part of the output query?
The "HAVING" clause.
124
Where can sql_always_where: and sql_always_having: parameters be applied?
Inside
1. explores
2. joins
125
If you use raw SQL in your sql_always_where: parameter, what might you also need to do?
You may need to add a always_join the table being referred to in the sql_always_where.
E.g.,
explore: order {
sql_always_where: customer.name <> 'Periaptly Corporation' ;;
join: customer {
sql_on: ${order.customer_id} = ${customer.id} ;;
}
}
In this example, the "customer.name" is referring directly to the database and not the LookML object ${customer.name}.
A better fix is probably adding the join properly and changing the code to:
"sql_always_where: ${customer.name} <> 'Periaptly Corporation'"
126
If you want filters a user can change but not remove, what parameter should you use?
always_filter.
This parameter is added to an Explore and always adds a filter to the Explore, though, the user can change the values making it "completely open."
127
If you want filters a user cannot change, what parameter should you use?
access_filter. These and be applied directly to views, joins, explore and limit what a user can
128
What is the primary difference between access_filter and sql_always_where?
The "access_filter" allows restricting row-level data from user access based on user_attributes.
```
E.g.,
explore: customer {
access_filter: {
field: sales.region
user_attribute: sales_region
}
}
```
The "sql_always_where" filters row-level data to specific value
```
E.g.,
# Using Looker references
explore: order {
sql_always_where: ${created_date} >= '2012-01-01' ;;
}
```
129
Describe the functionality of the conditionally_filter: parameter.
A default filter that can be removed if at least one of the specified alternative filter fields is selected as filter.
```
explore: order_items {
conditionally_filter: {
filters: [created_date: "1 month"]
unless: [users.id]
}
}
```
130
Describe the behavior of measure, type: average
Aggregate.
It is an aggregate which finds the mean of a numeric data cross rows.
131
Describe the behavior of measure, type: average_distinct
Aggregate.
It is an aggregate which finds the mean of a numeric data cross rows, -meant for denormalized data-.
132
Describe the behavior of measure, type: date
Non-aggregate
A measure which contains a date.
133
Describe the behavior of measure, type: list
Aggregate.
It creates a comma separated list of values across rows.
134
Describe the behavior of measure, type: max
Aggregate.
Finds the maximum value across rows.
135
Describe the behavior of measure, type: min
Aggregate.
Finds the minimum value across rows.
136
Describe the behavior of measure, type: median
Aggregate.
Gets the midpoint value across rows for numeric data.
137
Describe the behavior of measure, type: median_distinct
Aggregate.
Gets the midpoint value across rows for numeric data -which is denormalized.-
138
Describe the behavior of measure, type: number
Non-aggregate.
For a non-aggregate measure containing a number. Note, like all measures, there is no GROUP BY added.
139
Describe the behavior of measure, type: percentile
Aggregate.
Generates the total for each row (i.e., "value / SUM(value)").
140
Describe the behavior of measure, type: percentile_distinct
Aggregate.
Generates the total for each row (i.e., "value / SUM(DISTINCT value)") for denormalized data.
141
Describe the behavior of measure, type: running_total
Post-SQL
Running total for every row.
142
Describe the behavior of measure, type: string
Non-aggregate.
For measures containing letters or special characters.
143
Describe the behavior of measure, type: sum
Aggregate.
Adds all values across rows (i.e., SUM(value))
144
Describe the behavior of measure, type: sum_distinct
Aggregate
Generates a sum of values within a column for denormalized data.
145
Describe the behavior of measure, type: yesno
Non-aggregate.
Fields that will show "Yes" or "No" for their result.
146
T / F -- when extending a view, in the extended view you can delete a field.
False.
You can override the values of a dimension, but your cannot delete it. However, you can hide it from UI or remove it from the field: [] in the join.
147
Why should extending a view which contains a PDT be avoided?
This will cause two different PDTs to be created, as they are tracked by their view name.
148
What does the permission_set "access_data" control? And what does it depend on?
No dependencies.
Allows users to access the LookML data files.
149
What does the permission_set "see_lookml_dashboards" control? And what does it depend on?
Depends on model specific "explore"
Allows users to view LookML dashboards. If they have "develop" permission, they can also edit them.
150
What does the permission_set "see_looks" control? And what does it depend on?
Depends on access_data.
Users can see saved Looks (but not dashboards). Users must have the "explore" permission to "Explore from Here" on the Looks.
151
What does the permission_set "see_user_
| dashboards" control? And what does it depend on?
Depends on "see_looks".
Users can view dashboards.
152
What does the permission_set "explore" control? And what does it depend on?
Depends on "see_looks"
Users can access and use the Explore page to generate reports. Without this permission, users can only view saved dashboards (if see_lookml_dashboards or see_user_dashboards has been granted).
153
What does the permission_set "create_table_calculations" control? And what does it depend on?
Depends on "explore"
Users can view, edit, or add table calculations and custom fields; users with only the explore permission can only view table calculations and custom fields.
154
What does the permission_set "save_content" control? And what does it depend on?
Depends on "see_looks."
Users can save and edit Looks and dashboards. Users must have explore permission for any relevant models to explore from those Looks and dashboards. Users must have download_with_limit and/or download_without_limit permissions to download the content.
155
What does the permission_set "create_public_looks" control? And what does it depend on?
Dependencies are model specific.
Users can mark a saved Look as public, which will then generate URLs granting access to that report without authentication.
156
What does the permission_set "download_with_limit" control? And what does it depend on?
Depends on "see_looks."
Users can download queries (as CSV, Excel, and other formats) but must specify a row limit of 5,000 or fewer to avoid memory problems from large downloads on the instance.
157
What does the permission_set "download_without_
| limit" control? And what does it depend on?
Depends on "see_looks."
The same as download_with_limit, but does not require the user to specify a row limit. Downloading all results for some types of queries may require substantial memory, potentially causing performance issues or even crashing the Looker instance.
158
What does the permission_set "schedule_look_emails" control? And what does it depend on?
Depends on "see_looks"
Users can deliver any Looks, dashboards, and queries with visualizations to which they have data access to email. Users can schedule delivery to occur after a datagroup has been triggered, has managed the cache, and has rebuilt relevant PDTs.
To send or schedule System Activity dashboards, users must have access to all models.
Users who also have create_alerts permissions can send email alert notifications.
If no email domains are specified in the Email domain allowlist on the Settings page of the Admin panel, the user can deliver to any email domain.
There are additional considerations for embed users.
This permission is applied to individual models or model sets, rather than across the entire Looker instance.
159
What does the permission_set "schedule_external_
| look_emails" control? And what does it depend on?
Depends on schedule_look_
emails.
The same as schedule_look_emails. If any email domains are specified in the Email domain allowlist on the Settings page of the Admin panel, the user can deliver to any email domain.
Users who also have create_alerts permissions can set alerts that send notifications to emails with any domain.
There are additional considerations for embed users.
This permission is applied to individual models or model sets, rather than across the entire Looker instance.
160
What does the permission_set "create_alerts" control? And what does it depend on?
Depends on see_looks.
Users can create, duplicate, and delete their own alerts; and see and duplicate alerts marked Public by other users. The user must be signed in to Slack to see alerts that send Slack notifications. Users can view their alerts on the Manage Alerts user page. Admins can access the alerts admin pages.
161
What does the permission_set "follow_alerts" control? And what does it depend on?
Depends on see_looks.
Users can view and follow alerts. View the alerts they have followed or for which they are listed as a recipient from the Manage Alerts user page.
162
What does the permission_set "send_to_s3" control? And what does it depend on?
Depends on see_looks.
Users can deliver any Looks, dashboards, and queries with visualizations to which they have data access to an Amazon S3 bucket. Users can schedule delivery to occur after a datagroup has been triggered, has managed the cache, and has rebuilt relevant PDTs.
This permission is applied to individual models or model sets, rather than across the entire Looker instance.
163
What does the permission_set "send_to_sftp" control? And what does it depend on?
Depends on see_looks.
Users can deliver any Looks, dashboards, and queries with visualizations to which they have data access to an SFTP server. Users can schedule delivery to occur after a datagroup has been triggered, has managed the cache, and has rebuilt relevant PDTs.
This permission is applied to individual models or model sets, rather than across the entire Looker instance.
164
What does the permission_set "send_outgoing_webhook" control? And what does it depend on?
Depends on see_looks.
Users can deliver any Looks, dashboards, and queries with visualizations to which they have data access to a webhook. Users can schedule delivery to occur after a datagroup has been triggered, has managed the cache, and has rebuilt relevant PDTs.
This permission is applied to individual models or model sets, rather than across the entire Looker instance.
165
What does the permission_set "send_to_integration" control? And what does it depend on?
Depends on see_looks.
Users can deliver any Looks, dashboards, and queries with visualizations to which they have data access to the third-party services integrated with Looker via the Looker Action Hub. If using custom actions with user attributes, users must have this permission and have a non-null and valid user attribute value for the specified user attribute to deliver Looker content to that action destination. This permission is not related to data actions. Users can schedule delivery to occur after a datagroup has been triggered, has managed the cache, and has rebuilt relevant PDTs.
This permission is applied to individual models or model sets, rather than across the entire Looker instance.
166
What does the permission_set "see_sql" control? And what does it depend on?
Depends on see_looks.
Users can access the SQL tab while exploring and any SQL errors caused by their queries.
167
What does the permission_set "see_lookml" control? And what does it depend on?
Depends on see_looks.
Users have read-only access to LookML. Users must have this permission to see the Go to LookML link in the Admin panel.
If you want a user to be able to edit LookML you must also give them the develop permission. This permission interacts with model sets in a potentially unexpected way, as described above.
168
What does the permission_set "develop" control? And what does it depend on?
Depends on "see_lookml."
Users can make local changes to LookML but will not let them make those changes available to everyone unless they also have the deploy permission. This permission interacts with model sets in a potentially unexpected way, as described above.
This permission is required to see the Chat option in the Help menu, and to see metadata in the Looker IDE. Users also need this permission to access the Rebuild Derived Tables & Run option in the Explore gear menu. Note that this is not model-specific, so if a user has this permission in one model, they will have access to Rebuild Derived Tables & Run in all models.
169
What does the permission_set "deploy" control? And what does it depend on?
Depends on "develop."
Users can push their local LookML changes to production so that those changes become available to everyone.
170
What does the permission_set "support_access_toggle" control? And what does it depend on?
Depends on "develop."
Users can enable or disable access by Looker analysts to your Looker instance.
171
What does the permission_set "use_sql_runner" control? And what does it depend on?
Depends on "see_lookml."
Users can use SQL Runner to run raw SQL against their allowed connections.
172
What does the permission_set "see_drill_overlay" control? And what does it depend on?
Depends on access_data.
Users can see the results of drilling into a dashboard tile but cannot explore those results. If explore is granted, this permission is also automatically granted (even if it isn’t checked).
173
What does the permission_set "manage_spaces" control? And what does it depend on?
No dependencies.
Users can create, edit, move, and delete folders. Users will also need the Manage Access, Edit content access permission.
174
What does the permission_set "manage_models" control? And what does it depend on?
No dependencies.
Each LookML model is mapped to a specific set of database connections on the Manage LookML Projects page. With this permission, users can configure these mappings and create new projects. Non-admin users granted this permission will have access to all connections that are allowed by the models to which they have access.
175
What does the permission_set "create_prefetches" control? And what does it depend on?
No dependencies.
Allows API calls to the pre-fetch API endpoint, which you can read more about in this Community topic.
176
What does the permission_set "login_special_email" control? And what does it depend on?
No dependencies.
Users can log in with traditional email/password credentials, even if other login mechanisms (such as Google, LDAP, or SAML) have been enabled on your instance. This can be useful for consultants or others who may not be a part of your normal authentication system.
177
What does the permission_set "embed_browse_spaces" control? And what does it depend on?
No dependencies.
Enables the content browser for single sign-on (SSO) embeds. If you are using SSO embeds you should give this permission to users who have the save_content permission.
178
What does the permission_set "see_queries" control? And what does it depend on?
No dependencies.
Users can see the Queries page in the Admin section of Looker. This privilege does not give a user the ability to terminate a query on the Queries page.
179
What does the permission_set "see_logs" control? And what does it depend on?
No dependencies.
Users can see the Log page in the Admin section of Looker.
180
What does the permission_set "see_users" control? And what does it depend on?
No dependencies.
Users can see the Users page (but not the Groups page) in the Admin section of Looker. This privilege does not give a user the ability to create new users, see or create API credentials, reset passwords, or otherwise modify users or privileges. A user granted this permission can see all users in all groups on an instance, even on a closed system. A user can see all group names and all role names, which some companies may consider sensitive.
181
What does the permission_set "sudo" control? And what does it depend on?
Depends on "see_users"
Users can sudo (in other words, act as and temporarily inherit the permissions of) another user by clicking the Sudo button on the Users page.
The sudo permission does not allow a non-admin to sudo as an admin, but a non-admin could potentially escalate their privileges by using sudo, so exercise caution.
182
What does the permission_set "see_schedules" control? And what does it depend on?
No dependencies.
Users can see the Schedules and Schedule History pages from the Admin panel in Looker.
183
What does the permission_set "see_pdts" control? And what does it depend on?
No dependencies.
Users can see the Persistent Derived Tables page in the Admin section of Looker and view information about PDTs from projects that use any connection associated with models for which they have data access.
ADDED6.22 This permission is applied to connections to which users have data access, rather than across the entire Looker instance or to individual models or model sets.
184
What does the permission_set "see_datagroups" control? And what does it depend on?
No dependencies.
Users can see the Datagroups page in the Admin section of Looker. Users can see connection names, model names, and other information about datagroups defined in a model for which they have data access.
This permission is applied to individual models or model sets, rather than across the entire Looker instance or to connections.
185
What does the permission_set "update_datagroups" control? And what does it depend on?
Depends on see_datagroups.
Users can trigger a datagroup, or reset its cache, via the Datagroups page in the Admin section of Looker. Like users with the see_datagroups permission, users with update_datagroups can see datagroups defined in projects that use a model for which they have data access.
This permission is applied to individual models or model sets, rather than across the entire Looker instance or to connections.
186
What does the permission_set "see_system_activity" control? And what does it depend on?
No dependencies.
Users can access the System Activity Explores and dashboards and the internal i__looker database to view usage, history, and other metadata about a Looker instance.
