> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/workspaces-and-drives/folder-templates.md).

# Folder Templates

Folder templates for when you leverage the same folder structure repeatedly. This is most comment for projects that follow a given folder structure for every new project that gets spun up. At the moment, folder templates only support a set folder structure, and cannot also include files. A template can contain up to 100 folders.

### Creating folder templates

1. From within a Drive, create a desired folder structure within a parent folder, or navigate to an already existing folder structure contained within a parent folder
2. Right-click on the parent folder containing the desired folder structure
3. Select **Save folder as template**
4. Pick an icon and name your template
5. Add an optional description so people know what the template is used for
6. Turn on **Save to Workspace** if the template should be usable across any/all Drives within your Workspace. This option is only available to workspace admins.
7. Click **Create template** to Save

### Using a folder template

From within a Drive

1. Navigate within the folder hierarchy to where the folder should go
2. Right-click and hover over **Create new folder**
3. Select your template from the fly out menu

### Manage existing folder templates

Deleting a template happens immediately, without a confirmation step.

#### Drive-level templates

1. Right-click on a Drive
2. Click **View Folder Templates**
3. Rename or delete your Drive-level folder templates

#### Workspace-level templates

1. Go to Settings > General > Folder Templates
2. Click **Manage Templates**
3. Rename or delete your Workspace-level folder templates


---

# 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://academy.shade.inc/workspaces-and-drives/folder-templates.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.
