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

# Comments and collaboration

> Use comments and collaboration features to work together inside Oculon.

Comments are most useful when the discussion stays attached to the exact metric, assumption, or report being reviewed.

![Comments panel in Oculon](https://mintcdn.com/oculon/X89F3z_YFDceIY6n/images/getting-started/fr-comment.png?fit=max\&auto=format\&n=X89F3z_YFDceIY6n\&q=85\&s=b803d9d2cff30d1977218813e17bd44c)

## Use comments for decisions, not just reactions

Good comments move work forward. They explain what changed, what needs a response, or what decision is still open.

Use comments when you need to:

* ask for review on a specific metric or assumption
* explain why a value changed
* capture the business context behind a planning choice
* close the loop on an open question without leaving the model or board

## Comment on the smallest useful object

Keep the conversation close to the thing being discussed.

* Comment on the specific item under review, not only the broader page.
* Describe the business question, not just the symptom.
* Mention the assumption, time period, scenario, or filter context when it matters.

That makes the thread easier to understand later, especially when the same model is reviewed by several people.

## Keep review cycles structured

Comments work best when they are paired with a clear review surface.

Useful patterns include:

* a named scenario for in-progress planning changes
* a shared view for one filtered slice of the model
* a board review for decision-ready output

That structure reduces back-and-forth because everyone is looking at the same context.

## Close loops when the work is done

Comments should not stay open forever.

* Resolve comments when the issue is closed.
* Add a final note if the decision changed the model or the expected next step.
* Start a new thread when the topic changes instead of overloading the old one.

Comments are most valuable when they leave a clear trail of what was decided and why.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.