# 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**

<figure><img src="https://2094208261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCZc46qaaBbVmMuYXPfgz%2Fuploads%2FD7TZfVjxLPYwpFQ6BX5z%2FScreenshot%202026-03-05%20at%201.36.54%E2%80%AFPM.png?alt=media&#x26;token=a3fc9f37-b57a-4f25-a47a-7699762417c3" alt=""><figcaption></figcaption></figure>

**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

&#x20;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](https://docs.agentnoon.com/admin-capabilities/notifications) to stay updated on approvals and invitations
* Explore [Sharing Scenarios](https://docs.agentnoon.com/scenarios/collaboration/sharing-scenarios) to control who can comment
* Return to [Scenario Collaboration](https://docs.agentnoon.com/scenarios/collaboration) overview