Creating Projects

A Project is the core organisational unit in ADD CREATE. Each project has its own knowledge base (your uploaded source documents) and all the content you generate lives inside it.

How to Create a Project

1. Navigate to Projects in the left sidebar.
2. Click the New Project button.
3. Fill in the project details:
   • Name (required): A descriptive name, for example Q3 Product Launch Campaign.
   • Description (optional): Context for your team about what this project is for.
4. Click Create.

Once created, you are automatically set as the project owner with full administrative access.

After Creation: Getting Ready to Generate

A freshly created project cannot generate content immediately. You need to upload documents and let the platform process them first.

1. Upload your source files — Go to the Files tab and upload your documents.
2. Wait for processing to complete — The platform reads and indexes your files in the background. The project status will update as it progresses.
3. Start generating — Once the status shows Ready, the Studio is unlocked.

Status	Meaning	Can generate?
Pending	No files have been processed yet	No
Running	Processing is in progress	No
Ready	Knowledge base is built and ready	Yes
Failed	An error occurred	No

Project Settings

After creating a project you can update:

• Name — The display label for the project.
• Description — A free-text description for your team.

Style Presets & Prompts

Style Presets and Prompt Templates are not set at the project level. They are selected when you launch a generation job in the Studio.

Permissions

As the project creator you automatically have full access. You can then invite other users or teams and choose what level of access to grant them. See Teams & Permissions for details.

Advanced Usage Notes

Use these patterns to get more predictable results:

• Keep inputs specific and scoped to one intent per generation request.
• Save intermediate outputs often, especially before running major edits or regenerations.
• Use review and assignment workflows early to reduce rework late in the lifecycle.

Moving Projects Between Computers

Use the project export/import flow when you need to move a project to another machine.

1. On the source machine, export the project from the Projects page.
2. Import that bundle on the destination machine.
3. If the project also depends on a separately managed Brand Controls profile, import that brand profile bundle as well.
4. After import, open Project Configuration and confirm the expected brand profile is selected for the project.

Project bundles include uploaded source files, generated artifacts, and the template-image assets referenced by saved slide deck states. Older bundles exported before this portability fix may still open with missing template images on another machine and should be exported again from the source machine.

Troubleshooting

If results are not what you expected:

• Verify source quality first (missing context, inconsistent structure, or conflicting inputs reduce output quality).
• Re-check selected options and audience/profile settings before re-running.
• If a job fails repeatedly, wait briefly and retry once; then escalate with the artifact or job context.
• If an imported slide deck shows missing template images, re-export the project from the original machine with the latest build, then re-import it. If you imported Brand Controls separately, reselect that imported profile in Project Configuration.

Frequently Asked Questions

Why did quality change between runs?

Different input context, settings, and model/runtime conditions can produce different outputs.

Should I regenerate or manually edit?

Regenerate when the core structure is wrong; manually edit when only wording, ordering, or style needs adjustment.

What is the best way to reduce iteration cycles?

Start with clear scope, run smaller batches, and use review checkpoints after each major step.