Skip to main content

Assigning pages, bundles and cart drawers to a project

How to move one item or many between projects, and what changes when you do.

Written by Eddie Lavandera

Everything you build is normally assigned to a project when you create it. Items become unassigned when the project holding them is deleted, or when you remove them deliberately. This covers moving one item, moving many at once, and what assignment actually changes.

In this article:


Assigning one item

Every row in the dashboard content table carries a small project pill showing where it lives.

  1. Find the row on the dashboard, on any of the Stores and pages, Landing pages, Bundles or Cart drawers tabs.

  2. Select the project pill on that row. An unassigned item shows + Assign; an assigned one shows the project name.

  3. Choose the project you want.

Atlas confirms with Assigned to {name}. Hovering the pill shows where the item currently sits: In {label}. Click to change. for an assigned item, or Click to assign to a project for one that is not.

If it fails you will see Failed to assign to project. Try again, and check that the destination project is not already full.


Assigning several at once

  1. Select the checkboxes on the rows you want to move.

  2. Open the bulk assign control.

  3. Search with Search projects if you have many, then choose the destination.

The popover shows how full each project is as {used}/{max}, so you can see at a glance which have room. A project with no room shows Project full and cannot be chosen. If your selection is larger than the space available, Atlas tells you rather than moving some and failing on the rest: {used}/{max} used — not enough room for {needed}.

💡 Bulk assign is the fastest way to tidy up after deleting a project. Filter the table to Unassigned, select everything, and move it in one go.


Removing an item from a project

Select the project pill on the row and choose Remove from project. Atlas confirms with Removed from project, and the item becomes unassigned.

Unassigned is a normal state, not an error. Unassigned items still work, still appear in your lists, and still serve customers if they are published.

If removal fails you will see Failed to remove from project.


What assignment changes, and what it does not

Changes:

  • Where the item appears in your dashboard

  • Which project's activity log records changes to it

Does not change:

  • Anything on your storefront

  • Whether a page is published, or which theme it is published to

  • Whether a bundle or cart drawer is active

  • Any copy, colour or setting on the item

  • Your bill

ℹ️ Moving a page into a project does not rewrite it with that project's voice or research. Project context is applied when a page is generated, not when it is filed. To apply a new project's voice, build a new page or a page variation inside that project.


When a project is full

Each project holds up to 25 items. If the destination is full you have three options:

  1. Move something out of it first.

  2. Delete items you no longer need. Drafts are usually safe to delete and have no effect on your store or your bill.

  3. Create a new project. You can have up to 25.


Next steps

Did this answer your question?