# Imported views ### Imported views When you're working on projects that have several different [views](/guides/views.md), you'll often find yourself rebuilding certain settings in every single view. For example, you might want all views to have a base element size of 20, or you might want all views to have a [filter control](/guides/controls.md) across the top to filter by element type. But let's say you decide later on that you want the base element size to be 25, or you want to filter by tags instead of element type—if you had to update those settings across a big group of views, it would get tedious and complicated. **Imported views** solve that problem! Instead of rebuilding your base settings in every view, you can simply define them in one view, then instruct your other views to import those base settings. When you make any change to your first view, Kumu will automatically update all other views that are importing those base settings. ### Import views with the Advanced Editor You can use the [Advanced Editor](/overview/user-interfaces/view-editors.md#advanced-editor) to import views. Here's the basic syntax: ```scss @import "my-view"; ``` Replace `my-view` with the [slug](/guides/slugs.md) of your original view's name, and you'll be ready to go! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.kumu.io/guides/imported-views.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.