What a project is#
A project is the operational hub for a marketing effort. It connects five things:
- Catalogs — one or more product-feed sources scoped to this project.
- Product sets — the rules that decide which products from those catalogs are in scope.
- Channels — the outgoing feeds (Meta, Google Shopping, TikTok, custom) that export a product set as ads.
- Prompts — the AI rules that write ad copy and select content for this project's products.
- Fallback content — project-level images, videos, and ad copy used when an individual product doesn't have its own.
Everything downstream — enrichment, review, and export — happens inside the scope of a project.
Creating a project#
- From the Projects list, click + New project. The project is created straight away and opens.
- Name it at the top of the page — until you do, it shows as "Untitled project". From there you can also set a description, add catalogs, build product sets, and create channels.
A new project starts with no catalogs attached — the next step is almost always adding a catalog.
Project settings#
At the top of the project page you can edit the name and an optional description — click either to change it. There are no start or end dates: a project keeps running until you archive it.
Copying a project#
Use the copy icon in the project toolbar — or Copy or move… in the project's row menu on the Projects list — to open the copy dialog. It gives you a full, independent duplicate of everything the project owns, as it was last published. The name field suggests "{project name} copy". (If you belong to more than one organization the dialog offers Copy and Move; pick Copy.)
What gets copied:
- Catalogs. Each live catalog's setup — feed URL, mapping, rules, image processing — is copied as a new catalog, and its products are imported again from the feed. Import history doesn't carry over.
- Product sets, channels and prompts. The copy's channels get their own feed URLs, so a destination reading the original keeps reading the original. Prompts are copied switched off, so nothing generates or spends credits until you turn them on.
- Content edits. Approvals, rejections, main-image choices and content you uploaded carry over to the same products in the copy.
- Fallback content — the project's images, videos and ad copy.
What doesn't get copied:
- Archived catalogs, channels and prompts.
- Unpublished changes. Publish first if you want them in the copy.
The new catalogs and channels count against your plan's limits, so a copy is refused if your plan can't fit it.
Copying into another organization#
If you belong to more than one organization, the dialog also lets you copy the project into another of your organizations — useful for reusing a proven setup across clients. The templates its channels render and the rulesets its catalogs apply are copied there too, so the copy works on its own. Switch to that organization to find it. If the copy's channels are used with Renable Options, connect Meta in that organization as well.
Moving a project to another organization#
Move takes the whole project — catalogs, channels, prompts, product sets, content and its edits — to another organization you belong to. Nothing is copied and nothing is imported again: it's the same project with the same feed URLs, so your destinations keep working with no change on their side. The templates and rulesets it uses are copied into the new organization; the originals stay where they are.
Move only appears if you belong to more than one organization.
- Click the copy icon in the project toolbar, or Copy or move… in the project's row menu on the Projects list.
- Switch to Move.
- Choose the Target organization.
- Read the warning the dialog shows, then click Move project. There's no second confirmation step — the move starts when you click.
Afterwards the project sits on that organization's Projects list.
Four things change:
- Access. Members of the old organization who aren't members of the new one lose access to the project. Invite them there if they still need it.
- Meta. Integrations belong to an organization, so Meta has to be connected in the new organization before Renable Options can show the project's designs again. Your feeds never stop: the move keeps every feed URL, so nothing has to be re-pointed at the ad networks.
- Monitors. A monitor in the old organization that watched this project's catalogs or channels loses them from what it watches. One that watched only this project is switched off; one that watched more keeps the rest. Set up the watching you still want in the new organization.
- History. Aimée conversations and credit history stay with the old organization. The project's catalogs and channels count against the new organization's plan from now on, and the move is refused if that plan can't fit them.
A move can't be undone from the old organization. Once the project has moved, only someone in the new organization can move it back.
Archiving a project#
Archiving isn't a control on the project's own page — it's done from the Projects list:
- Go to the Projects list (
/projects). - Open the ⋯ menu at the right end of the project's row.
- Choose Archive.
The archive happens immediately — there's no confirmation prompt, so double-check before clicking.
Archived projects are hidden from the list by default. To see them — or to unarchive one via the same ⋯ menu — click the filter button next to the search field and switch on Show archived.
Warning — this is not reversible. Archiving a project archives every catalog inside it, and every channel exporting those catalogs is emptied, so your destinations stop showing products that would no longer be updated. Once a catalog is archived, its products are queued for permanent deletion after 30 days. Un-archiving the project afterward does not bring the catalogs or products back — you'd need to recreate the catalogs and re-import the feed from scratch.
Only archive a project you're confident you're done with.