Projects

Projects are the command centers for your strategic content initiatives. They bring together team members, documents, and specialized context into a single, organized workspace.

Project Structure

1. Project Context

One of the most powerful features of a Project is its Context Layer.

  • Inheritance: Every Project automatically inherits your team's global Reference Library. You don't need to re-upload your brand guidelines or company profile.
  • Specific Context: You can upload Project-Specific Context items that are relevant only to this project.
    • Example: For a "Product Launch" project, you might upload the specific PRD (Product Requirement Document) and competitor battlecards for that product. These won't clutter the global library but will be used by the AI for any document created within this project.

2. Project Brief

You can designate a specific document (usually a Canvas) as the Project Brief.

  • This document sits at the top of your project.
  • It serves as the "North Star" for the project, outlining goals, timelines, and key messages.
  • The AI can specifically reference the Brief to ensure all deliverables align with the project's core mission.

Core vs. Supporting Documents

Projects distinguish between your primary outputs and your working files:

  • Core Output Documents: The final assets you are creating (e.g., the blog post, the whitepaper, the email sequence).
  • Supporting Documents: Research notes, interview transcripts, or rough drafts that helped you get there. You can drag and drop documents between these sections.

Visibility Levels

Even within a Project, you have granular control over who sees what. Each document has a visibility setting:

  • Private: Visible ONLY to you. Even other project members cannot see it. Great for personal drafts inside a project container.
  • Project: Visible to all members of the Project, but hidden from the rest of the team.
  • Team: Visible to your entire organization (anyone in the workspace can find it).

Members and Roles

You can invite specific team members to join a Project.

  • Collaborators: You can add users to your account as "Collaborators". These users generally have restricted access to the wider app but can be added to specific Projects to view and edit content. This is perfect for freelancers, clients, or subject matter experts.
  • Creators/Admins: Have full access to create projects and manage the workspace.

The "Collaborator" Role

A key workflow is adding an external partner (like a freelancer) as a Collaborator in your Admin settings.

  1. Add them to the team as a Collaborator.
  2. Add them to a specific Project.
  3. They will only see that Project and its contents. They cannot see your global Reference Library or other private projects.
Scroll to Top