> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/guides/layouts/fixed.md).

# Fixed

With the fixed layout, you position everything manually. Just click and drag an element to change its location, or click and drag a connection to change its curvature. If you want to change the starting point of a connection (to make it start from another element), click on the starting point of the connection and drag it over to another element. The same steps can be used to change the ending point of a connection.

If you're building a fixed map with [Sketch Mode](/getting-started/first-steps.md#sketch-mode), you can hold the `Alt` key on your keyboard, then click and drag elements and connections to move them.

**Good to know:** The [system templates](/guides/templates.md#system-template) are set to a fixed layout by default.

## Changing from force-directed to fixed layout:

1. Click on the settings icon ![](https://1181816445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkXSW1nEf49ISqGxYuRfS%2Fuploads%2Fgit-blob-29572adb5b74c3a9b2db8fca66f2a4a00fe6b652%2Fsliders-h.svg?alt=media) on the right side of the map
2. Select **Customize defaults**
3. Scroll down to the **General settings** section to change the "Layout" to "off"
4. In the same section, change "Default element behavior" to "fixed"

If you would rather do this in the [Advanced Editor](/overview/user-interfaces/view-editors.md#advanced-editor), here is the code you can use to switch to a fixed layout:

```scss
@settings {
    layout: static;
}
```

If you were previously using a force-directed layout, you may need to pin all the existing elements in place. You can do this by pressing `A` on your keyboard to select all, and then by clicking the pin button in the lower right of the element profile or pressing `P` on your keyboard.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kumu.io/guides/layouts/fixed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.