> For the complete documentation index, see [llms.txt](https://developerdocs.instructure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developerdocs.instructure.com/services/canvas/permissions/details/file.permissions_manage_course_templates.md).

# Manage Course Templates

## What it Does

### Course Templates - create

Allows user to set a template for an account.

Allows user to select a course as a course template in Course Settings.

Allows user to view names of course templates in the root account.

### Course Templates - delete

Allows user to remove a course as a course template in Course Settings.

Allows user to set an account to not use a template.

### Course Templates - edit

Allows user to change the template being used by an account.

Allows user to view names of course templates in the root account.

## Additional Considerations

### Account Settings

To access the Account Settings tab, Account-level settings - manage must also be enabled.

### Courses

To create a new course to use as a course template, Courses - add must also be enabled.


---

# 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://developerdocs.instructure.com/services/canvas/permissions/details/file.permissions_manage_course_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.