Skip to main content

​
What this article shows you

A Project keeps one workstream’s Chats, instructions, files, and linked Products together. This guide shows you how to create a focused Project and confirm its first Chat is saved in the right place.

​
Practical use cases

Run one campaign

Keep the brief, working files, decisions, and deliverable Chats together for one launch or promotion.

Repeat one workflow

Reuse short instructions and source files for recurring ad, email, landing page, or research work.

Separate client work

Give each client or durable workstream a clear home so its Chats and files do not mix with unrelated work.

Prepare a team handoff

Keep the decision trail and reusable context together before sharing the required Project, Product, and Chat with a teammate.

​
Video walkthrough

Create a Project, save one reusable instruction, and start its first Chat.

​
How Projects work

A Product holds reusable context about an offer. A Project organizes the work that uses that context. A Chat holds one focused execution or decision trail. Use a Project when several Chats should share the same workstream, instructions, or files. Start a regular Chat when the job does not belong to an ongoing workstream. Keep Project instructions short. Add only guidance that should apply across every Chat in the Project. Put task-specific details in the relevant Chat or file.

​
What you will do

  1. Create and name a Project.
  2. Add one short reusable instruction.
  3. Start the first Chat from the Project.
  4. Confirm the Chat appears under the Project’s Chats section.

​
Before you start

Choose:
  • A clear Project name that identifies the campaign or workstream.
  • One or two instructions that should apply to every Chat in the Project.
  • The first focused result you want from the Project.
You can add files and link Products after creating the Project. You do not need to fill every section before starting the first Chat.

​
Follow along

1

Create the Project

Open Projects in the sidebar, then select New Project.Enter the Project name. As you type, StefanBrain picks an icon and a color that fit the name. To choose your own, select the icon beside the name.Turn on Share with team if your team should see the Project from the start. It is off by default, and you can share the Project later from its Share button.Select Create. StefanBrain opens the new Project.
Create Project dialog filled with the Knowledge Base rollout name, a blue color, and a briefcase icon

Use a recognizable workstream name, then choose one simple color and icon before creating the Project.

2

Add one reusable instruction

Select the Instructions card at the top of the Project. Add only guidance that should apply to every Chat in this Project.
Select Save Instructions. The panel closes, and the Instructions card shows the saved text.
Knowledge Base rollout Project overview showing its saved concise-checklist instruction and no Chats yet

After saving, the reusable instruction appears on the Project overview beside its Chats, Files, and Products.

3

Start the first Project Chat

Use the composer at the bottom of the Project. It reads New chat in [Project name].Ask for one focused result:
Knowledge Base rollout Project composer showing a kickoff-checklist request beside the saved Project instruction

Start the first Chat from inside the Project so the saved instruction remains visible beside the request.

Send the request and review whether the result follows the Project instruction.
4

Verify where the Chat was saved

Return to the Project overview and find the new conversation under Chats.Open it again to confirm the decision trail remains inside the intended Project.

​
Make the Project useful

  • Name the workstream, not a one-off task.
  • Keep instructions short enough to apply to every Project Chat.
  • Add only files that should remain available across the workstream.
  • Link the relevant Product when the work depends on stable offer context.
  • Start a separate Chat for each deliverable or decision trail.
Create another Project when the shared instructions, files, campaign, or client boundary changes.

​
Common mistakes and troubleshooting

  • Creating a Project for every small task. Use one Project for the durable workstream and start focused Chats inside it.
  • Putting task-specific details in Project instructions. Keep the temporary brief in the relevant Chat or file.
  • Starting the Chat outside the Project. Return to the Project and use the composer labeled New chat in [Project name].
  • The instruction did not save. Select the Instructions card, make the change again, and select Save Instructions. If the save fails, the panel stays open and says why.
  • The icon does not fit. Select the icon beside the name and choose another icon or color. Your choice stays.
  • The new Chat is not listed. Refresh the Project and confirm you sent the request from its composer rather than a regular Chat.

​
Next steps