# monday.com Folder Structure and Board Organization Canonical: https://www.taskrhino.ca/monday-com/folder-structure/ > How to organize monday.com folder structure: 3 folder levels, templates that create boards in a folder, naming patterns, and API options for named folders. Published: 2026-02-26 Updated: 2026-10-29 Author: Rakesh Patel Categories: BoardBridge **Key takeaways** - monday.com folders hold boards, dashboards and docs inside a workspace and nest 3 levels deep (a folder plus 2 layers inside it). - A create-board automation with a multi-component template creates all its boards within a folder: up to 10 components on Pro and 30 on Enterprise; Standard templates hold 1 component. - Native automations don’t name the folder or boards from deal data, pre-fill the boards, or move existing boards into folders. - The monday.com API can: create\_folder, create\_board and duplicate\_board take a name and a folder, and update\_board\_hierarchy moves an existing board into a folder. - Use one folder per project, named with the date and client, and one board naming pattern. One deal closes. Nine boards should land in a named project folder, not scattered across your workspace. Definition **Folder:** a container inside a monday.com workspace that groups boards, dashboards and docs; folders nest up to 3 levels. Can monday.com auto-create folder structure? [monday.com workspaces can get messy fast](https://www.taskrhino.ca/monday-com/). Folders group boards, dashboards and docs inside a workspace, but every new project adds multiple boards — and if you’re creating those boards manually, they land at the root level of your workspace, mixed in with everything else. You then drag them into folders, rename them to match the project, and hope someone remembers to follow your naming convention next time. Native automations solve part of this, and the monday.com API covers the rest. Here’s what each can do, and how to set up a folder structure that stays organized. ## Where monday.com Folder Automation Falls Short **The problem:** New project boards scatter across root workspace instead of being organized into project folders monday.com board duplication puts new boards at the **root level** of your workspace. An automation can create a multi-component template, and those boards are all created within a folder in the selected workspace (Pro: up to 10 components and 1,000 items; Enterprise: 30 and 2,500) ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/360001362625)). What native automation can’t do is: - Name the folder and boards from deal/project data - Create more boards than the plan’s component limit, or create a multi-board folder on Standard - Pre-fill the new boards with deal data - Move existing boards into a folder ### The Manual Workflow Here’s what teams do today: 1. CRM deal moves to “Won” 2. PM creates the project folder 3. PM duplicates boards to root level ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/360000304399-How-to-duplicate-a-board)) 4. PM drags each board into the project folder 5. PM renames folder to match project name 6. PM renames boards to match internal convention For high-volume teams creating 10+ projects per week, this is a constant background task that compounds: - Inconsistent naming conventions (sometimes “ProjectName”, sometimes “ProjectName – 2026”) - Boards left at root level by accident (clutter and confusion) - Duplicate folder names if someone misremembers the format - Team members can’t find their project boards because they don’t know the naming pattern - Cross-board automations that need reconnecting after each duplication (see [why cross-board recipes break on duplication](https://www.taskrhino.ca/monday-com-automations/dont-carry-over-duplicated-boards/)) ### What the Community Says In the monday.com community thread [Folder and subfolder creation through automation](https://community.monday.com/t/folder-and-subfolder-creation-through-automation/116470) (June 2025), a user asked: > “Why can’t we automate folder and sub-folder creation in monday? we have automations that ‘when status changes, create board from template'” — **mike01**, June 20, 2025 monday.com staff pointed to the API documentation and Feature Requests. Native automation covers part of it (template boards created into a folder), but not dynamic naming or data pre-fill. **Need help setting up new projects in monday.com?** Book a free 30-minute call with a certified monday.com partner. [Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## The Five Board Naming Mistakes Teams Make ### 1\. Template boards mixed with live boards **Problem:** You have “Event Template” sitting next to “Acme Corp Event” in the same workspace view. **Fix:** Templates go in a dedicated “Templates” folder. Live project boards go in project folders or a “Live Projects” folder. Archived projects go in “Archive – 2025” folders. ### 2\. Inconsistent naming patterns **Problem:** Half your project boards are named “Client Name – Board Type” and the other half are “Board Type – Client Name”. **Fix:** Pick one pattern and stick to it. Recommended: `{Client/Project Name} - {Board Type}` so all boards for the same project sort together alphabetically. ### 3\. No date or year in project names **Problem:** You have “Smith Wedding” from 2023 and “Smith Wedding” from 2026. Which is which? **Fix:** Include year or date in project folder names: “Smith Wedding – June 2026” or “Acme Corp Q1 2026 Campaign”. ### 4\. Duplicate board names across workspaces **Problem:** monday.com allows duplicate board names with no warning. You have “Marketing Campaign” in three workspaces. Search results show all three. **Fix:** Prefix board names with workspace context or client name: “Acme – Marketing Campaign”, “Beta Corp – Marketing Campaign”. ### 5\. No archive or cleanup strategy **Problem:** Your workspace has 200 boards. Half are from completed projects 2+ years ago. Everything is one big scrollable list. **Fix:** Archive completed projects into year-based folders: “Archive – 2024”, “Archive – 2023”. Delete boards that will never be referenced again. ## How to Auto-Create Folder Structure in monday.com There are two ways to have a project’s boards created inside a folder: a native automation with a multi-component template, or a script on the monday.com API. Key stat 10 components is the most one template holds on Pro; Enterprise allows 30 and Standard 1. ### Option 1: Native Automation with a Multi-Component Template (Pro and Enterprise) A template holds 1 component on Standard, up to 10 on Pro (1,000 items) and up to 30 on Enterprise (2,500 items). When a create-board automation uses a template with multiple components, they are all created within a folder in the selected workspace. 1. **Build the project template** — Move the boards a project needs into a separate workspace and save the workspace as a template (workspace owners, Pro and Enterprise). 2. **Add a create-board automation** — For example, when a CRM deal’s status changes to “Won”, create a board from that template; all its components are created within a folder in the selected workspace. 3. **Rename the folder and boards** — The automation doesn’t name them from the deal, so rename the folder (e.g., “2026-03-15 — Acme Corp Conference”) and each board to your pattern. ### Option 2: The monday.com API (Custom Script or Integration) The API covers what native automations don’t: - **create\_folder** takes a name, a workspace and a parent\_folder\_id for subfolders, so folder names can come from your deal data - **create\_board** and **duplicate\_board** take a board\_name and a folder\_id, so boards are created inside the folder with project names - **update\_board\_hierarchy** moves an existing board into a folder It needs development time, and every call counts toward the account’s daily API limit (200 on Free, 1,000 on Basic and Standard, 10,000 on Pro, 25,000 on Enterprise). **Example: Event Management Project** - **Folder name:** “2026-03-15 — Acme Corp Conference” - **Boards created in folder:** Event Overview, Band Confirmations, Team Confirmations, Vendor Coordination, Logistics, Production, Reporting, Marketing, Finance - **Result:** When the PM opens monday.com, one folder contains all 9 boards (within Pro’s 10-component limit). No root-level clutter. ### Naming Convention TaskRhino tip Add a unique identifier, such as a project or client ID, to your folder naming pattern so two projects never get the same folder name. Pick a folder naming pattern and board naming rules, and use them whether you rename by hand or name boards through the API: **Folder Naming Pattern:** `{project_date} — {client_name} {event_type}` Example output: `2026-03-15 — Acme Corp Conference` **Board Naming Rules:** `{board_type_name} — {project_name}` Example output: - `Event Overview — Acme Corp Conference` - `Team Confirmations — Acme Corp Conference` - `Vendor Coordination — Acme Corp Conference` Each board gets a consistent name that includes both the board’s purpose and the project context. ### Name Template Boards So Renaming Is Quick TaskRhino tip Name each template board “Template – Board Type”: a new project then only needs “Template” swapped for the client or project name. Name each template board “Template – Board Type”, so a new project only needs “Template” swapped for the client or project name: **Template boards:** - Template – Event Overview - Template – Band Confirmations - Template – Travel - Template – Production **Project boards after renaming:** - Acme Corporation – Event Overview - Acme Corporation – Band Confirmations - Acme Corporation – Travel - Acme Corporation – Production Other patterns work too: `{Client Name} - {Board Type} - {Year}` or `{Project Code} - {Board Type}`. ### Keep One Folder per Project Move every board into its project folder so the workspace stays organized: **Templates folder:** - Template – Event Overview - Template – Band Confirmations - Template – Travel **Acme Corporation – Annual Event folder:** - Acme Corporation – Event Overview - Acme Corporation – Band Confirmations - Acme Corporation – Travel - Acme Corporation – Production **Smith Wedding – June 2026 folder:** - Smith Wedding – Event Overview - Smith Wedding – Band Confirmations - Smith Wedding – Travel Every project is self-contained in its own folder. No loose boards. ### Folder Naming Best Practices #### Active projects: `{Client/Project Name} - {Event Date or Year}` **Examples:** - Smith Wedding – June 2026 - Acme Corp Q1 Campaign – 2026 - Downtown Festival – Sept 2026 #### Templates: “Templates” and “Templates – Archive” (old versions) #### Archive: “Archive – 2026”, “Archive – 2025”, “Archive – 2024” Move completed projects into year-based archive folders. This keeps the active workspace clean. ### Enforcing Consistency Across Teams When naming follows one documented pattern (or an API script applies it), every team member creates folders the same way: - No typos in project names - No “Project”, “project”, “PROJECT”, or “Proj” variations - No forgotten date prefixes - Board names always include the project context - Everyone knows where to find boards for a specific project ### No Manual Drag-and-Drop With a multi-component template or an API script, boards are created inside the folder, so nobody has to drag them there. **Need help structuring your monday.com boards?** Book a free 30-minute call with a certified monday.com partner. [Book a Free Call](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## How to Clean Up an Existing Messy Workspace 1. **Create a Templates folder** — Move all template boards into it. Prefix template board names with “Template -” for clarity. 2. **Create Archive folders** — Create “Archive – 2024”, “Archive – 2023”, etc. Move completed projects into the appropriate year. 3. **Batch rename live boards** — Rename all active project boards to the same pattern. Before: “Event Board”, “Project Alpha”, “Client XYZ – Overview”. After: “Acme Corp – Event Overview”, “Beta Inc – Event Overview”, “Gamma LLC – Event Overview”. 4. **Create project folders for active projects** — Group related boards into folders named after the client or project. 5. **Delete unused boards** — If a board hasn’t been touched in 2+ years and has no historical value, delete it. Use monday.com’s Activity Log to check last edit date. Deleting a folder archives every board inside it and deletes its dashboards, so empty a folder before you delete it. ## Group Naming Inside Template Boards Set group names once in the template so every project starts with the same structure. **Example:** On a Confirmations board template, name the groups by member type: - Group: “Band Members” - Group: “Production Crew” - Group: “VIP Guests” Every board created from the template starts with those groups, keeping board structure consistent across projects. ## Workspace Permission Best Practices **Related to organization:** Workspaces with clear folder structure make permissions easier to manage. **Recommended workspace setup:** - **Main Workspace:** Active projects only - Permissions: All team members - **Templates Workspace:** Template boards only - Permissions: Admins only (prevents accidental edits) - **Archive Workspace:** Completed projects - Permissions: Read-only for most users This prevents clutter and accidental modifications. For more on permission management, see our guide to [monday.com board permissions](https://www.taskrhino.ca/monday-com/board-permissions/). Structure is the start; our [workflow management best practices](https://www.taskrhino.ca/monday-com/workflow-management-guide/) and our guide to [project management in monday.com](https://www.taskrhino.ca/monday-com/project-management-guide/) cover the work that runs on these boards. ## Real-World Scenario: Multi-Team Project Organization A consulting firm manages 20+ projects per year across multiple industries. Each project has 8-10 boards, and team members need to find their boards instantly. **Manual folders and naming:** 1. Deal won on CRM 2. PM creates project folder manually, names it “Project ABC” 3. PM duplicates board templates to root 4. PM drags Event Overview board into Project ABC folder 5. PM renames it “Event Overview – Project ABC” 6. PM repeats for every other board 7. Six months later: “Was Project ABC the one in the ‘Project’ folder or the ‘Acme’ folder?” **With a multi-component template automation:** 1. Deal won on CRM 2. The automation creates all the project’s boards within a folder 3. PM renames the folder “2026-Q1 — Acme Corp” and the boards (“Event Overview — Acme Corp”, “Team Confirmations — Acme Corp”, etc.) 4. Team member searches “Acme” → finds the folder instantly ## Manual vs Template Automation vs API | Need | Manual Folders | Multi-Component Template Automation | API Script | | --- | --- | --- | --- | | Create folder at project start | Manual (PM must remember) | ✓ Automatic on status change | ✓ Automatic | | Consistent folder naming | No — depends on PM convention | Manual rename | ✓ Named from deal data | | Place boards in correct folder | Manual drag-and-drop | ✓ Created inside the folder | ✓ Created inside the folder | | Consistent board naming | No — depends on the PM | Manual rename | ✓ Named per board type | | Plan needed | Any | Pro (10 components) or Enterprise (30) | Any; calls count toward the daily API limit | | Setup effort | None | Template + automation | Development time | ## How to Set It Up 1. **Pick your naming patterns** — folders (e.g., `{date} — {client} {project_type}`) and boards (e.g., `{board_type} — {project_name}`) 2. **Build the multi-component template** — Save the project’s boards as one template (Pro: up to 10 components; Enterprise: 30) 3. **Configure the create-board automation** — usually on the CRM’s Won status 4. **Test:** Win a test deal, check the boards appear together in a folder, then rename them to your pattern 5. **Document the naming convention** for your team so they understand the pattern ## Limitations You Should Know Key stat 3 levels of organization is the most a workspace allows: a folder plus up to 2 layers of folders inside it. **Folders nest only three levels deep.** You can add up to 2 layers of folders within a folder, for a total of 3 levels of organization within a workspace ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/115005316845)). A “2026 → Q1 → Acme Corp” hierarchy fits; a fourth level does not. **Renaming boards is manual.** Neither templates nor create-board automations name boards from your data, and nothing renames existing boards. If you have 50 boards with inconsistent names, you’d rename them manually or use a script with the monday.com API. **Cross-board automation recipes break on duplication.** When you duplicate template boards, cross-board automation connections don’t transfer properly, requiring manual reconfiguration (see [why cross-board recipes break on duplication](https://www.taskrhino.ca/monday-com-automations/dont-carry-over-duplicated-boards/)). **Plan limits exist.** The Free plan allows 3 boards in total ([monday.com Help Center](https://support.monday.com/hc/en-us/articles/115005320209)). At very high scale (300+ boards), multiple workspaces can keep boards easier to find. Our [monday.com implementation](https://www.taskrhino.ca/monday-com-implementation/) team can set up the workspace structure and templates for you. ## Common Questions **Q: Can monday.com auto-create folder structures?** A: Partly. An automation can create a multi-component template, and its boards are created within a folder in the selected workspace (up to 10 components on Pro, 30 on Enterprise). It can’t name that folder from deal data or pre-fill the boards. The monday.com API can create named folders and the boards inside them. **Q: Can I customize the folder naming pattern?** A: Not with native automations: they don’t name the folder from your data, so you rename it after creation. With the API, create\_folder takes any name you build from CRM or project data. **Q: What if two projects have the same name or date range?** A: Add a unique identifier, such as a project or client ID, to your naming pattern so folder names never collide. **Q: Can I use different folder structures for different project types?** A: Yes. Save one multi-component template per project type (an event template, a consulting template) and point each automation at the right one. **Q: Can I move or rename the folder after creation?** A: Yes. Rename a folder from its three-dot menu and drag boards in or out at any time; through the API, update\_folder changes a folder’s name or parent and update\_board\_hierarchy moves a board. **Q: Does folder auto-creation work with nested folder structures?** A: Folders nest up to 3 levels within a workspace (a folder plus 2 layers inside it). A multi-component template creates one folder; a Year > Quarter > Project hierarchy needs manual setup or the API’s parent\_folder\_id. **Q: What if I need boards at the root level AND in project folders?** A: A multi-component template puts all its boards in its folder. Move any board you want at the root afterward. **Q: Can I set folder permissions automatically?** A: Folders don’t have their own permissions: a folder is visible only to its creator and to users with access to the boards inside it, and only its creator can delete it. Control access through [board and workspace permissions](https://www.taskrhino.ca/monday-com/board-permissions/). ## Who This Is For An automated folder structure suits teams who: - Create multiple projects per month and want instant organization - Want consistent naming conventions enforced automatically - Hate wasting time dragging boards into folders - Need team members to find project boards without confusion - Manage large workspaces with 100+ boards and need structure to stay sane If you’ve ever searched for a board and couldn’t remember which project folder it was in, auto-created folder structures solve that. **Need organized folder structures for every project?** TaskRhino’s [monday.com implementation](https://www.taskrhino.ca/monday-com-implementation/) team can set up the templates, automations or an API script for you. [Book a free 30-minute consultation](https://www.taskrhino.ca/contact-us/). **Need Help With Your monday.com Setup?** TaskRhino has implemented monday.com for 110+ teams. Get a free consultation. [Schedule Free Consultation](https://calendly.com/rp-spaceo/call-with-rakesh-est-timezone) ## Frequently Asked Questions **How can I automate folder creation in monday.com when a status changes to trigger new project boards from templates?** ### Native monday.com automations can create boards from templates on status changes, and a multi-component template creates its boards within a folder in the selected workspace (up to 10 components on Pro, 30 on Enterprise). They don’t name that folder from your deal data, so rename it after it’s created. For named folders, a script on the monday.com API can call create\_folder and then create or duplicate boards into it with folder\_id. **Why can’t monday.com automations move newly created boards directly into a specific folder?** ### Automation recipes don’t have a move-to-folder action. A multi-component template creates its boards within a folder (Pro and Enterprise), but single-board templates land in the workspace root, so those boards need drag-and-drop. Through the API, update\_board\_hierarchy moves an existing board into a folder. **Can I use monday.com API to auto-generate folder structures with subfolders for project portfolios?** ### Yes. The API’s create\_folder takes a name, a workspace and a parent\_folder\_id for subfolders, and monday.com allows 3 levels of folders within a workspace. create\_board and duplicate\_board accept a folder\_id, so a script can build the whole structure. It needs custom development, and API calls count toward the account’s daily limit (200 on Free, 1,000 on Basic and Standard, 10,000 on Pro, 25,000 on Enterprise). **How to avoid workspace clutter from automated board creation per client or stakeholder group in monday.com?** ### Use a multi-component template (Pro and Enterprise) so each automation run creates its boards together within a folder instead of the main workspace, then rename the folder for the client or stakeholder group. For high volumes, an API script can create a named folder per client and the boards inside it. Manual folder creation and drag-and-drop work too, but they don’t scale. **How do I systematically audit and rename more than 100 boards without breaking existing automations and integrations?** ### Start with a private audit board listing each board’s current name, new name, purpose, owner and connected automations or integrations. Rename in small batches, starting with boards that have no cross-board automations, and check that each board’s automations still run after the rename. Test on one board before renaming the rest. **What’s the difference between using prefixes (like ‘Project -‘) versus folder structures for organizing more than 100 boards at scale?** ### Prefixes make boards easy to find in search and keep related boards together alphabetically, but they lengthen names and become redundant once boards live in folders. Folders give a visual hierarchy (up to 3 levels within a workspace) without cluttering names. Use folders for primary organization (by client, project or department) and keep prefixes only where they add meaning, such as “Template –” on template boards. **How should I handle duplicate board names like three ‘Marketing Campaign’ boards in different folders—consolidate or rename?** ### Duplicate names across folders create confusion in automations, notifications, and when team members reference work verbally. Before consolidating, audit each board’s columns, groups, and active items using your audit board—if they’re genuinely different workflows, rename them to reflect their distinction (e.g., ‘Marketing Campaign – Q2 2026’, ‘Marketing Campaign – Social Media’, ‘Marketing Campaign – Email’). If they’re identical, consolidate into one board with groups or subitems to separate campaigns, which reduces maintenance overhead and ensures single-source-of-truth for shared data. **What’s the best approach to deprecate and archive 8 boards named after clients who left two years ago?** ### Don’t delete these boards right away: first check for automations, mirror columns or Connect Boards columns that reference them. Move them into an archive folder with a name like “ARCHIVE – Client Name – End Date” and note in each board’s description why it was archived. Delete them only once you’re sure nothing references them. Deleting a folder archives all the boards inside it, and archived boards can be restored from the Archives section. **How do I prevent the ‘Project -‘ prefix problem from happening again as we scale beyond more than 100 boards?** ### Set a naming standard now and build it into your board templates, so new boards start from a template rather than from scratch. Avoid generic prefixes, use consistent casing, and keep a short governance board that records your naming standards, retired prefixes and who approves new boards. **Should I use Connect Boards columns to centralize board metadata (like owner, purpose, status) to reduce search time?** ### Yes—create a ‘Board Registry’ board with columns for Board Name, Owner, Purpose, Status (Active/Deprecated), and Last Updated, then use Connect Boards columns in your audit/governance board to link to the registry. This eliminates redundant data entry and creates a single source of truth for board information, cutting the time spent searching for the right board. However, this only works if your board naming is already clear—metadata centralization amplifies poor naming rather than fixing it. Pair this with consistent naming conventions first, then implement the registry as your organizational layer.