Control cells are interactive cells that allow us to filter down the data displayed in our canvas. They're accessed from the toolbar at the bottom of the screen. We have several different types of control cells that we can use. We have drop down select control cells, date picker control cells, the options for a string input or a number input. We have slider cells, toggle for Boolean data, and we have table filters, which are a unique type of control cell. Essentially, they display the data from one of your tables. And for very quick ad hoc analysis, you can add filters here. So I'm gonna change this to title, and we can quickly filter on any one of the results. There are some key concepts that should help you understand how control cells work. So starting from the bottom and working our way back up, we have downstream cells, which are the visual or table cells that are affected by the value in the control cell. The control cell is the filter itself. So if I change the value here, you can see that the downstream cells update. You can see that the source data does not update. The source data is the data that the downstream cells are built off of. It's important to note that the source data does not necessarily need to appear on the canvas. We have an example here of a really simple visual that was built with count metrics, and you can see that the source data for this particular visual is it's a view within our catalog. Similarly, when I click on the control cell here, the source of this is also the same view within our catalog. There are three ways to set up a control cell and it depends on your use case. So the first use case is when you have a data source and you want all downstream cells from that data source to be filtered by the control cell. This is really handy if you have a report built, for example, and you want to add one filter to the report that will update all of the cells in the report when it changes. So it's really easy to do. We go down to our toolbar. We select the type of filter that we want to apply. We are gonna give the control cell a meaningful name. So I'm gonna call this artist ID because that's what we'll be filtering on. And when I come down here in the multiple select, I'm gonna select one of the source data cells here under self table. So I have named that table artists all downstream, and I am gonna reference that here. So artists all downstream, and the column that we're interested in is artist ID. Coming further down on this menu, we want to add automatic references so that all of the downstream cells are automatically filtered by that control cell. So I'm gonna hit the plus symbol, and you can see that this populates with the info that we've already added above. So artist dot down stream and artist ID. I'm gonna add a second automatic reference for our other source table. So here, I'm gonna select tracks all down stream, which is what I've named the other table. And similarly, I'm gonna select the same column, artist ID. You can see that both of the visualizations update as this changes. So I'm gonna select all. As I mentioned before, this is really handy when you do have a report and you want all of the cells in the report to be updated when the value in the control cell changes. Another handy tip for that instance is if we come to our overview panel, if we put a forward slash, we can select a control. And here, we can actually select the control that is on our canvas. So artist ID, the one we just created. And you can see that here, I can actually update the contents of the control cell from here, which is really handy if you are in a report or a really big canvas and you need to move around. That way, the control cell is always there. At the side, you don't need to come back and find it on the canvas. And another thing to mention here is that there can, of course, be instances where you don't necessarily want all of the downstream cells to be filtered by the control cell. You can manage this by when you click on the control cell, come into the automatic references, you click on the three dots next to it, and you can see down here that there's a toggle for scope to specific frames. If we wanted to, we could toggle this on and we would select a specific frame. If that were the case, only the downstream cells that sit in that frame would be affected by the values in the control cell. In our second setup use case, we are going to imagine that we have a visual that we would like to filter, but we don't necessarily want all of the visuals that are downstream from that source to be filtered. In that case, we select our control cell from the toolbar down below. This time I'm gonna use a single select, which will allow me to only pick one value from our source table. Again, I'm gonna rename the, the control cell. So this time I'm gonna call this artist name because that's what we'll be filtering on. Down here, we're gonna select our source data. So this table is called artists underscore. So we're gonna select it here. And the column that we're interested in is name. You can see that our control cell is connected to the source. Now we need to connect it to the visualization. So we select the visualization. I'm gonna take the field that I want to use as a filter and add it to filters. You can see in the pop up, I can select connect to control. And here I have to select the control cell to connect it to. I'm gonna connect it to artist name, which is the control cell that we have just created. And you can see that I can select a value and that this visualization updates and this one doesn't, which is exactly what we were hoping to do. Our third use case is great when you have something quite specific that you want to do and you want to link a control cell to your code to make something interactive. You can see that I've created a control cell here called genre control. When we look at the sidebar, we can see that when I added it, these manual references were automatically generated. So it tells you what to write to be able to reference the control cell within your code, and it's possible for both SQL and Jinja. So let's take a look at the SQL example. Here you can see that I've I've referenced genre control here within my where clause. So my query says to select any entries from Spotify dot Spotify genres where the field genre is like the field value from genre control. And I've typed rock in here and you can see that rock appears in several different genres from this dataset and they all appear here. In this example, you can see that I have essentially written the same code, but I've used Jinja rather than, referencing it as a SQL table, and I have the same results. Rock is appearing in several different genres. And that's it. So for more information on control cells, check out our docs. Thank you very much.