Drive folder mapping lets you link a Drive folder to a category so that images uploaded in the article editor are automatically saved to the correct folder. Without a mapping, all uploaded images go to the default Editor folder in Drive. With a mapping, images are routed by category, keeping your Drive organised without any manual sorting.
When to use Drive folder mapping
- You want images automatically organised by content area rather than collected in a single Editor folder.
- You want contributors to upload images without manually selecting a Drive folder each time.
- Your Drive folder hierarchy mirrors your category structure and you want uploads to reflect that.
- Multiple contributors are uploading images across many categories and you need consistent file placement.
Map a Drive folder to a category
- Navigate to Documentation () in the left navigation bar.
- Hover over the category in the Categories & Articles pane and click the More () icon.
- Select Set drive folder.
- In the Set drive folder panel, select the folder or subfolder from your project's Drive where images should be saved.
- Click Update.
All images uploaded to articles in this category will now be automatically saved to the selected folder.
Changing a category's Drive folder mapping does not move images that were previously uploaded. Only images added after the mapping is updated will be saved to the newly selected folder.
Mapping precedence
When a parent category and a subcategory are each mapped to different Drive folders, the most specific mapping always takes priority.
| Priority | Mapping applied |
|---|---|
| 1 (highest) | Subcategory Drive folder mapping |
| 2 | Parent category Drive folder mapping |
| 3 (default) | Editor folder |
Example: If the "Getting Started" category is mapped to /docs/getting-started and a subcategory "Quick Start" within it is mapped to /docs/quickstart, images uploaded to articles in "Quick Start" will go to /docs/quickstart, not the parent category's folder.
Best practices
- Mirror your Drive folder structure to your category hierarchy. This makes it easy to find images by browsing Drive the same way you browse categories.
- Set mappings before contributors start uploading. Changing the mapping later does not move existing images, so configure it early to avoid scattered files.
- Use subcategory mappings for granular control. If one subcategory generates significantly more images than others, give it a dedicated folder.
- Keep Drive folder file counts in check. Drive folders have a limit of 5,000 files. For high-volume image categories, create dedicated subfolders to stay within this limit.
FAQ
Can I map a Drive folder to subcategories as well?
Yes. The Set drive folder option is available for all categories and subcategories.
How is a category Drive folder mapping different from the Editor folder?
If a category is mapped to a Drive folder, that mapped folder takes precedence over the Editor folder. All images added to articles in that category will be saved to the mapped folder. If no mapping is set, images are saved to the Editor folder by default.
Can I map a Drive folder at the article level?
No. Drive folder mapping is only available at the category and subcategory level. It is not possible to set a different Drive folder for individual articles.
Can I change or remove a category's Drive folder mapping?
Yes. You can change or remove a mapped Drive folder at any time. Changing the mapping will not move previously uploaded images. Only images added after the update will be saved to the newly selected folder.
My subcategory and its parent category are mapped to different Drive folders. Which one applies?
The subcategory mapping takes precedence. The most specific mapping always overrides any broader setting.