Skip to main content

Folders

Folders help teams keep campaign work organized. They can also act as the workspace boundary that editors operate inside.

Folders​

Folders are useful for structuring work by:

  • brand
  • team
  • campaign type
  • market or language
  • project or season

Use a folder structure that helps the team find active work quickly. The goal is clarity, not hierarchy for its own sake.

How folders fit into the workflow​

Folders are most useful when they mirror how work is actually managed.

For example, a folder can represent:

  • one business unit
  • one market
  • one lifecycle team
  • one campaign stream
  • one brand workspace

This gives editors a clear place to create and manage campaigns without having to search across unrelated work.

Parent and child folders​

Folders can be nested. A common pattern is:

  • top-level folder for a brand, BU, or team
  • child folders for campaigns, markets, or seasons inside that area

That usually gives enough structure without making the tree too deep to navigate comfortably.

Folder access control​

Folder access control is part of the broader groups and access-control model.

At a high level:

  • leave a folder open if everyone should be able to work there
  • restrict a folder when only specific users or groups should create and manage campaigns inside it

This is often the final step that turns a theoretical access model into a practical day-to-day workflow.

If you want the full model for design systems, integrations, groups, and multi-BU setup patterns, see Groups and access control.

A good folder pattern​

A healthy folder structure usually has these qualities:

  • people can guess where a new campaign should live
  • top-level folders reflect meaningful business boundaries
  • the tree is not deeper than necessary
  • folder names are stable and easy to scan

For many teams, one strong top-level folder per BU or team is better than a large number of deeply nested folders.

Best practices​

  • Keep folder names clear and predictable.
  • Avoid overly deep folder trees unless they solve a real discovery problem.
  • Use top-level folders to create clear workspaces.
  • Let access control follow the folder model instead of fighting it.
  • Revisit folder structures occasionally as the team grows.