When to use folder-as-project
If multiple stakeholders need access but shouldn’t see each other’s links, use workspaces. If everyone on the team already sees everything, use folders.
How to set up
1
Create separate folders for each project
Sidebar → Folders & Tags → New Folder. Examples:
Q2 Launch, Brand Refresh, Client: Globex.2
Create additional folders for channels if needed
If you want to separate channels, create each one as its own folder. For example:
Q2 Launch - Paid Search, Q2 Launch - Paid Social, Q2 Launch - Email, Q2 Launch - Organic.3
Set a default folder
Make the active project the Default folder. The link builder UI pre-selects it for new links unless you pick another.
4
Apply tags for cross-project attributes
experiment, evergreen, paused - cross-cuts every project. See Folders & Tags.Real-world example
Internal SaaS marketing team running three projects in one workspace:experiment, paused, seasonal - apply across folders.
Common mistakes
Reaching for a new workspace when a folder fits
Reaching for a new workspace when a folder fits
Workspaces are heavy: separate billing, separate domains, separate members. If you don’t need isolation, use a folder.
Expecting nested folders
Expecting nested folders
Folders are separate, flat containers. Use naming conventions or tags to represent channel, quarter, or status instead of nesting folders.
Project sprawl
Project sprawl
Once a project ends, deactivate or delete its folder. Use archive on links if you want them out of default views but kept for analytics.
Edge cases
Default folder logic. Only one default per workspace. Setting a new default unsets the old one automatically.