The default folder in Document360 Drive determines where images are automatically saved when contributors paste or upload them directly from the article editor. Setting the right default folder keeps your Drive organized, reduces manual file management, and ensures assets land in a predictable, structured location from the start.
What is the default folder?
When a contributor adds an image to an article by pasting it or uploading it inline from the editor, Document360 needs to know where to store that file in the Drive. The default folder is the fallback destination for all such uploads.
The default folder operates at the project level, meaning it applies to all contributors in the project. It acts as a catch-all when no more specific folder mapping is in place for a category.
NOTE
If a category has been mapped to a specific Drive folder, that mapping takes precedence over the default folder. Only when no category-level mapping exists does the default folder apply. Refer to Mapping a category with a folder in Drive for more information.
Why set a default folder?
Without a default folder, uploaded assets may land in an unintended or ungrouped location, making them difficult to find, audit, or maintain over time. A well-chosen default folder:
Prevents assets from accumulating in a root-level or unstructured location.
Gives new contributors a sensible starting point without requiring them to manually select a folder every time they upload.
Supports Drive organization when your team has not yet set up category-level folder mappings.
Acts as a safety net for edge cases — for example, when images are pasted from an external source or when articles are imported from Word documents (.docx).
Use cases
The following scenarios illustrate when setting a default folder is most useful:
Scenario | How the default folder helps |
|---|---|
New project setup | Before category-folder mappings are configured, all uploaded images go to one designated folder rather than scattering across the Drive. |
General or uncategorized content | Articles that do not belong to a specific category still have a consistent home for their assets. |
Importing Word documents | Images embedded in imported .docx files are automatically extracted and saved to the default folder. |
Inline image pastes | When contributors paste screenshots directly into the editor, the image is saved to the default folder without any additional steps. |
Teams without a folder mapping strategy yet | A shared default folder keeps assets accessible to the whole team while the Drive structure is being established. |
Set a default folder
To set a folder as the default folder,
Click the Drive icon in the left navigation bar.
In the left navigation pane, locate the folder you want to set as the default.
Click the More icon next to the folder and select Set default folder.
A confirmation popup appears saying Editor folder updated. The default folder is now set at the project level and is identifiable by the edit icon that appears next to its folder icon in the Drive.
NOTE
You can set the default folder as many times as needed. If you select Set default folder on a folder that is already the default, no changes are made.
Folder mapping priority
Document360 uses a priority order to determine which Drive folder receives an uploaded image. Understanding this order helps you plan your Drive structure effectively.
Priority | Setting | When it applies |
|---|---|---|
1 (Highest) | Subcategory folder mapping | The article belongs to a subcategory that has been mapped to a Drive folder. |
2 | Parent category folder mapping | The article belongs to a category (with no subcategory mapping) that has been mapped to a Drive folder. |
3 (Fallback) | Default folder | No category or subcategory mapping exists for the article. |
To set up category-level folder mappings, refer to Mapping a category with a folder in Drive.
Best practices
Create a dedicated default folder. Avoid setting a system folder or a category-specific folder as the default. Instead, create a folder named something like General or Unsorted to serve as a clear catch-all.
Mirror your category structure. As your knowledge base grows, set up category-to-folder mappings for each major category. This reduces reliance on the default folder and keeps assets logically organized.
Monitor the default folder regularly. Review its contents periodically and move files to more specific folders as your Drive structure matures.
Update the default folder before hitting the file limit. Each folder supports up to 5,000 files. If your default folder is filling up, change the default to a new folder before uploads start failing. Refer to Troubleshooting Drive issues for steps on resolving folder file limit errors.
Communicate the default folder to your team. Since the setting applies project-wide, all contributors are affected. Let your team know which folder is set as the default and why, so they can anticipate where their uploads will go.