> For the complete documentation index, see [llms.txt](https://postjamm.gitbook.io/postjamm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postjamm.gitbook.io/postjamm/projects/working-with-projects-in-postjamm.md).

# Working with projects in Postjamm

### Understanding projects <a href="#understanding_projects" id="understanding_projects"></a>

Postjamm organizes your work in a simple structure:

* Folder: Used to group related projects
* Project: A single video or asset you are working on
* Versions: Different iterations of the same project
* Notes: Instructions or references for your team
* Comments: Feedback added directly on the video

This structure helps you keep all your work, feedback, and revisions organized in one place.

***

### Version management <a href="#version_management_1" id="version_management_1"></a>

Postjamm allows you to manage multiple versions of the same project without losing context.

#### Add a new version <a href="#add_a_new_version_1" id="add_a_new_version_1"></a>

To upload a new version:

1. Open your project
2. Click on the version selector at the top, near the project name<br>

   <figure><img src="https://desk.zoho.com/galleryDocuments/edbsna0a2e55b9e24dd8690dbbf4783f372ce74674944a17fcbb12181c6fe3dc6609ca1432f2a7232320a06de62d87c08284c?inline=true" alt=""><figcaption></figcaption></figure>
3. Select Add new version
4. Upload your updated video

The new version will be added to the project while keeping previous versions intact.

You can switch between versions using the version selector dropdown at the top of the project.

This allows you to review previous iterations at any time.

***

> 💡Version behavior\
> When a new version is added, commenting on older versions is automatically disabled. This ensures that all new feedback is focused on the latest version

***

#### Manage versions <a href="#manage_versions" id="manage_versions"></a>

To manage existing versions:

1. Open the version selector
2. Click on Manage versions<br>

   <figure><img src="https://desk.zoho.com/galleryDocuments/edbsna0a2e55b9e24dd8690dbbf4783f372ceb7854e695163fd3c11f5b7a6417c488e837979f4883bff2abff87aaac85d4421?inline=true" alt=""><figcaption></figcaption></figure>

#### Version behavior <a href="#version_behavior" id="version_behavior"></a>

* When a new version is added, commenting on older versions is automatically disabled
* This ensures that all new feedback is focused on the latest version \</aside>

From here, you can edit any version listed.<br>

> Note: Editing a version will remove all comments associated with that version

***

### Notes <a href="#notes" id="notes"></a>

Notes are used to provide context, instructions, or references for your team.

You can use notes for:

* Creative briefs
* Scripts
* Raw file references
* Editing instructions

To add a note:

* Enter your content in the notes section
* Click Save to ensure the note is stored<br>

  <figure><img src="https://desk.zoho.com/galleryDocuments/edbsn4e8b459225da46bc614e4fefe87ef46346f30c77ca2f639080ba3174622cfe291619cf8d45791c66be271c2981d397f2?inline=true" alt=""><figcaption></figcaption></figure>

<br>

***

### Comments <a href="#comments" id="comments"></a>

Comments allow you to review videos and provide precise feedback.

To add a comment:

* Scrub the timeline to the desired frame
* Type your comment and submit

Postjamm supports four types of comments:

* Text comments: Standard written feedback
* Annotations: Mark specific areas directly on the video
* Attachments: Add reference files or supporting material
* Voice notes: Record audio feedback with optional text explanation

***

### Comment visibility modes <a href="#comment_visibility_modes" id="comment_visibility_modes"></a>

You can control who sees each comment using visibility settings.

#### Available modes <a href="#available_modes" id="available_modes"></a>

* Everyone: Visible to team members, collaborators, and reviewers
* Team only: Visible only to team members and collaborators
* Reviewer only: Visible only to reviewers

#### Default behavior <a href="#default_behavior" id="default_behavior"></a>

* Comments are set to Team only by default
* This allows internal discussions before sharing feedback externally

#### Access control <a href="#access_control" id="access_control"></a>

* Workspace owners can use all visibility modes
* Team members and collaborators can use team-level visibility

***

### Managing comments <a href="#managing_comments" id="managing_comments"></a>

Postjamm provides tools to organize and track feedback efficiently.

***

#### Resolve comments <a href="#resolve_comments" id="resolve_comments"></a>

* Each comment includes a checkbox
* Checked = resolved
* Unchecked = unresolved

***

#### Filter comments <a href="#filter_comments" id="filter_comments"></a>

You can filter comments to focus on specific feedback:

* Show only unresolved comments using the Unresolved only filter
* Show or hide comments by:
  * Team members
  * Collaborators
  * Reviewers

***

### Project stages <a href="#project_stages" id="project_stages"></a>

You can track the progress of your project using stages.

Available stages:

* Yet to start
* In progress
* Internal review
* Client review
* Approved

These stages help you manage workflow and keep your team aligned.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://postjamm.gitbook.io/postjamm/projects/working-with-projects-in-postjamm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.