# Using folders in accounts

![](https://2751937154-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lu-ZWvY7BC8vS5I6doj%2F-MNysA9OI-THKqPmfoqV%2F-MNyvpeRj8TNXkYM1VlS%2FScreen%20Shot%202020-12-07%20at%202.34.05%20PM.png?alt=media\&token=e30eecd5-3fae-433d-b95d-2cb215a84ef6)

### Organize content with folders within an account

If an account on Content Controller has a large content library inside it, consider using folders to group courses and other assets easily. 

Adding content to folders inside an account works the same way as the [Organizing content with folders](https://guide.contentcontroller.com/content-1/organizing-content-with-folders) page. Just make sure you're in the **Account** section, rather than the **Content** section.

### **How to copy a folder from the content section into an account** 

1. Select an Account. 
2. Select **Content** to see content from that account. 
3. Select the content you'd like to copy to a folder using the checkboxes. 
4. Select **+ADD.** A dropdown will appear with an option to **Copy Folder** to copy a folder from the content section and all the contents inside it. 
5. Choose the folder you want to copy from the dialogue. 
6. Select **Next.**
7. Add optional descriptive notes, then select **Next**.
8. Make sure you are copying the correct folder into your account, and select **Submit.**
9. The result is having two folders with the same content that is *unlinked* from the original folder content.

{% hint style="info" %}
 Unlinked: copying a folder to an account does not mean that changes made to that folder in the Content section will also happen to the account. 
{% endhint %}


---

# 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://guide.contentcontroller.com/accounts/using-folders-in-accounts.md?ask=<question>
```

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.