> For the complete documentation index, see [llms.txt](https://handbook.musescore.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.musescore.org/3/basics/workspaces.md). # Workspaces Workspace is the visual settings, also known as graphical user interface (GUI), of the Musescore program itself. An analogy to the position of the pen, ruler etc on a composer's desk. It includes: * the toolbars and buttons at the top of the window, * the side panels, or sidebars, to the left of the window, such as [Palette](/3/basics/palettes.md), [Inspector](/3/basics/inspector.md), [Timeline](/3/advanced-topics/timeline.md) etc, * their configuration settings and position information, and * theme and canvas settings, see [Preferences](/3/advanced-topics/preferences.md). Note that the followings do **not** count as workspace: * **View→ Documents Side by Side, Documents Stacked, Full screen**, covered in [Viewing and navigation](/3/basics/viewing-and-navigation.md) chapter. * **View→ Show visible, Show Invisible, Show Unprintable, Show Frames, Show Page Margins, Mark irregular measures**, and toolbar's **Concert pitch, Zoom level and Page View/Continuous View/Single Page options** : these settings are covered in [Viewing and navigation](/3/basics/viewing-and-navigation.md) chapter. They are score data. They are [saved to and loaded from each score file](/3/basics/opensaveexportprint.md). Templates contain these settings and will be used when you create a new score from a template, see [Instruments, staff setup and templates](/3/basics/instruments.md). Workspace presets are setting profiles for workspace, user can choose the options a preset contains so that only those options are loaded and saved when the preset is applied. There are two default presets: **Basic** and **Advanced**, you can [create your own custom workspaces](#create-custom-workspace). ## Apply a preset Use either one of the following methods: * Select a new preset from the drop-down menu to the right of the [Note Input Toolbar](/3/basics/viewing-and-navigation.md#toolbars) (in versions prior to 3.3. this is located at the bottom of the workspace panel), or * From the menu, select **View→Workspaces**, and click on one of the options. ## Create a new preset To create a new preset: 1. Select an existing preset, see [Apply a preset](#apply-a-preset), 2. Either * Click the **+** button next to the dropdown list, or * Click **View -> Workspace -> New**, 3. The following dialog is shown:\\
Create new workspace dialog
4. Enter a name for the new preset, 5. Choose what the preset saves and loads, namely: * **Toolbars**: Information about toolbars and toolbar buttons and their order. * **Menu bar**: No function, as this is not implemented in MuseScore 3. * **GUI Components**: Information about the position of the GUI components and whether they are open or not. * **GUI Preferences**: Settings in [Preferences](/3/advanced-topics/preferences.md) such as Theme and Canvas settings. 6. Press **Save** ## Edit what settings a preset contains To change what settings a preset contains, select **View→Workspace→Edit**. In versions prior to MuseScore 3.3, you must create a new preset and then edit it, you cannot edit the Basic preset or the Advanced preset, see [Create new workspace preset](#create-custom-workspace). Changes made to the current workspace are automatically saved to the current preset, no further action is required, see [Edit the workspace](#edit-the-workspace) below. ## Edit the workspace Any changes you make to the current workspace are automatically saved to the current preset, no further action is required. See the main chapter [Viewing and navigation](/3/basics/viewing-and-navigation.md), these are some popular ways: * To choose which toolbar is displayed, toggle them under **View→Toolbars** menu. * To edit toolbar buttons, select **View→Toolbars→Customize toolbars**, see [Viewing and navigation : Toolbars](/3/basics/viewing-and-navigation.md#toolbars). You **cannot** add items to a toolbar from the [Master palette](/3/advanced-topics/master-palette.md). * To choose which sidebar is displayed, toggle them under **View** menu. * To dock or undock sidebars, see [Viewing and navigation : Side panels](/3/basics/viewing-and-navigation.md#side-panels). * To setup different sidebars, refer to their relevant chapters. For example, to set up palette see [Palettes](/3/basics/palettes.md) and [Master palette](/3/advanced-topics/master-palette.md). ## Preset directory Each preset is saved as a separate file under: * **Windows**: `C:\Users\[USERNAME]\AppData\Local\MuseScore\MuseScore3\`(actually `%LOCALAPPDATA%\MuseScore\MuseScore3`) * **MacOS**: `~/Library/Application\ Support/MuseScore/MuseScore3/`. * **Linux**: `${XDG_DATA_HOME:-~/.local/share}/MuseScore/MuseScore3/`. ## See also * [Viewing and navigation](/3/basics/viewing-and-navigation.md) for setting up toolbar and buttons. * [Palettes](/3/basics/palettes.md) * [Master palette](/3/advanced-topics/master-palette.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://handbook.musescore.org/3/basics/workspaces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.