Skip to main content

Why Can’t I Create a Folder Inside Request Folders?

Understand why folder creation is restricted inside Request sections, and how ManyRequests automatically structures folders to match your actual projects and keep your workspace organized.

Written by Regine Garcia

If you’ve tried organizing files inside your Requests section and noticed that you can’t create folders in certain places, you’re not doing anything wrong. This is expected behavior.

Let’s walk through why this happens and how the file structure works.

📌 Use Case

You’re managing multiple client requests and want to keep things tidy. Naturally, you try to:

  • Create folders inside a request to group assets

  • Add subfolders under “Design Projects” or “Requests”

  • Organize files the same way you would in Google Drive or Dropbox

But then you realize… the option to create folders is missing.

Why This Happens

ManyRequests uses a structured file system to keep everything consistent and tied to actual work.

Here’s how it works:

1. Root Level (Flexible)

At the top level, you can:

  • Create folders

  • Upload files

  • Organize things however you like

This is your free-form workspace.

2. Request Folders (System-Generated)

Inside sections like:

  • Design Projects

  • Requests

Folders are automatically created by the system whenever a new request or project is added.

Because of this:

  • You cannot manually create folders or files here

  • Each folder represents a real request, not just storage

This prevents:

  • Duplicate or unused folders

  • Confusion between actual work and manually created items

  • Broken links between requests and their assets

3. Inside Each Request Folder (Editable)

Once you're inside a specific request folder, you can:

  • Upload files

  • Add assets, deliverables, or references

Think of it as the working space inside each request.

How to Work Around This

If you need more structure, here are a couple of practical options:

Option 1: Use Root-Level Folders

Create your own folder structure outside the Requests section for:

  • Internal organization

  • Drafts or shared resources

  • Files not tied to a specific request


Option 2: Use Naming Conventions

Inside request folders, organize files by:

  • Prefixes (e.g. 01_wireframe, 02_final)

  • Versioning (e.g. homepage_v1, homepage_v2)

Simple, but it works well in practice.

You can’t create folders inside Request sections because those folders are directly tied to real requests and are created automatically by the system. This keeps your workflow clean, structured, and aligned with actual client work.

Did this answer your question?