> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/scenarios/collaboration/commenting.md).
# Commenting
Comments let you discuss scenarios with teammates — ask questions, provide feedback, document decisions, and tag collaborators (@mention), all within your planning work.
## How to Add a Comment
1. Open the scenario
2. Click the **Comments** icon in the left panel
3. Type your comment
4. Click **Post**
**When to use:**
* General questions about the scenario
* High-level feedback and suggestions
* Summarizing changes you made
* Requesting review from stakeholders
## Viewing and Managing Comments
**View all comments** — Click the **Comments** icon in the left panel to see all comments, sorted by most recent.
**Delete comments** — Open a comment > click **⋮** > **Delete**. Only comment authors and scenario owners can delete comments.
## Common Commenting Workflows
#### Documenting Decisions
Add a comment after each major change to document your reasoning, for example:
* "Closed this role due to budget constraints — $120K savings"
* "Added 5 new SDE roles to support the AI initiative roadmap"
When the scenario is approved, comments serve as the historical record.
#### Collecting Feedback
1. Share the scenario with stakeholders (View Only or Comment Only access)
2. Add a comment explaining what you need: "Please review and leave comments by Friday"
3. Stakeholders add their own comments
4. Resolve comments as you address each piece of feedback
#### Coordinating Between Planners
If two planners are working on the same scenario:
1. Planner A adds a comment: "Working on Engineering section now"
2. Planner B sees the comment and adds: "Got it, I'll handle Sales"
3. Both resolve comments as work progresses
## Best Practices
* **Comment liberally** — Explain your reasoning for key decisions
* **Be specific** — "Should this role report to the Engineering VP?" is better than "Thoughts?"
* **Resolve when done** — Keep the comment list focused on active discussions
## Troubleshooting
| Problem | Solution |
| -------------------- | ------------------------------------------------------------------- |
| Comments not showing | Refresh the page; check if you're filtering to show only unresolved |
## Next Steps
* Learn [Notifications](/admin-capabilities/notifications.md) to stay updated on approvals and invitations
* Explore [Sharing Scenarios](/scenarios/collaboration/sharing-scenarios.md) to control who can comment
* Return to [Scenario Collaboration](/scenarios/collaboration.md) overview
---
# 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://docs.agentnoon.com/scenarios/collaboration/commenting.md?ask=&goal=
```
`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.