> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Project Discussions

> Threaded team messaging inside a project

Project Discussions is a per-project threaded message board for your team. It's where design feedback, decisions, client comms, and status updates live — all scoped to the specific project you're working on.

```
Project > Discussion
```

<CardGroup cols={3}>
  <Card title="Start a thread" icon="plus">
    Create a new discussion
  </Card>

  <Card title="Reply inline" icon="reply">
    Respond in an existing thread
  </Card>

  <Card title="Convert to task" icon="list-check">
    Turn a thread into work
  </Card>
</CardGroup>

## Starting a Thread

<Steps>
  <Step title="Click Create Thread">
    From the Discussion tab, click **Create Thread** in the top right.
  </Step>

  <Step title="Write a title and body">
    Titles should be specific — *"Homepage hero copy feedback"* beats *"Question"*. The body supports rich text, code blocks, and inline images.
  </Step>

  <Step title="Pick a category">
    Categories are color-coded:

    * **Design** — visual, layout, UX feedback
    * **Development** — code, builds, deploys
    * **Marketing** — copy, campaigns, launches
    * **Executive** — decisions, strategy, approvals
  </Step>

  <Step title="Set priority">
    **Low**, **medium**, or **high**. Shows as a badge on the thread card.
  </Step>

  <Step title="Pick visibility">
    * **Public** — anyone on your team can see it
    * **SaaS only** — visible to users with SaaS-level access
    * **Account only** — visible only to account-level members
  </Step>

  <Step title="Attach files (optional)">
    Drag in screenshots, PDFs, or mockups. Useful for design reviews.
  </Step>

  <Step title="Post">
    Thread appears at the top of the Discussion list and notifications fire to visible team members.
  </Step>
</Steps>

## Replying to a Thread

Open any thread and use the reply box at the bottom. Replies are inline and threaded — no sub-sub-threads, just a clean conversation.

Features in replies:

* **@mentions** — type `@` and pick a teammate. They get notified.
* **Reactions** — thumbs up, heart, and more on any message
* **File attachments** — same drag-and-drop as the original post
* **Code blocks** — triple-backtick fenced blocks with language highlighting

## Converting a Discussion to a Task

When a discussion becomes something actionable, you don't lose the context — convert it straight into a PM task.

<Steps>
  <Step title="Open the thread">
    Navigate to the thread you want to convert.
  </Step>

  <Step title="Click Convert to Task">
    Button in the thread toolbar.
  </Step>

  <Step title="Pick a project and assignee">
    Modal shows your PM projects. Pick one and assign to a teammate.
  </Step>

  <Step title="Task is created">
    The new task links back to the original discussion so context stays intact.
  </Step>
</Steps>

## Role Badges

Each team member's name shows their role badge (Owner, Admin, Member, Viewer) — helpful for clients scanning who said what.

## Project Discussions vs. Hiveku Discussions

| Project Discussions                            | Hiveku Discussions                                              |
| ---------------------------------------------- | --------------------------------------------------------------- |
| Scoped to one project                          | Scoped to the whole account                                     |
| Good for per-project design/dev/marketing work | Good for account-wide announcements, cross-project coordination |
| Lives at **Project > Discussion**              | Lives at **top-nav > Discussions**                              |

Both use the same threading system, so you'll feel at home in either.

## Verifying a Thread Posted

<Steps>
  <Step title="Check the Discussion list">
    Your new thread appears at the top.
  </Step>

  <Step title="Have a teammate reply">
    Ask them to open the project and check the Discussion tab — they should see your post and be able to reply.
  </Step>

  <Step title="Confirm notifications fired">
    Mentioned teammates get a notification (bell icon, top right). Check that they received it.
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Teammate can't see my thread">
    Check the visibility setting. **Account only** hides the thread from SaaS-level members. **SaaS only** hides it from account-only members. Use **Public** for team-wide visibility.
  </Accordion>

  <Accordion title="Mentions aren't sending notifications">
    Check the recipient's notification preferences (Settings > Notifications). Project Discussion mentions are opt-in per user — if they muted project notifications, they won't get pinged.
  </Accordion>

  <Accordion title="File attachment upload fails">
    Check file size limit (varies by plan). Unsupported types — executables, archives above the cap — are rejected silently. Compress large images or link to external storage (Drive, Dropbox) for anything oversized.
  </Accordion>

  <Accordion title="Converted to task but it didn't appear">
    Open the **PM Projects** item in the top nav (not Project > Tasks — that's scoped to one project). The converted task lives wherever you selected in the convert modal.
  </Accordion>

  <Accordion title="Can't edit my own post after posting">
    Edits are allowed within a short window after posting. After that, post a follow-up reply instead — this preserves history for other team members who may have already read the original.
  </Accordion>
</AccordionGroup>

## What's Next?

<CardGroup cols={2}>
  <Card title="Manage Project Tasks" icon="list-check" href="/how-tos/manage-tasks">
    Track to-dos, bugs, and features per project
  </Card>

  <Card title="Invite Your Team" icon="user-plus" href="/how-tos/invite-team">
    Add teammates so they can participate in discussions
  </Card>
</CardGroup>