EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Comment on a model

Attach a question or decision to a row or period, reply in the thread, mention a teammate, and resolve the thread.

A comment attaches a question or a decision to a model row. You can attach it to all periods of the row or to one period. Use comments to keep the reason for an assumption next to the number.

A team Owner adds, replies to, and resolves comments in the full model.

1. Add a comment

  1. Go to Scenario planning → open a model.
  2. Select Comments in the model toolbar. The Comments panel opens on the right.
  3. In Row, select the row. Sections and groups are not in the list.
  4. In Period, keep All periods, or select one period.
  5. Type the comment. The maximum is 2,000 characters.
  6. Select Add comment.

If the model has no variables yet, the comment box shows "Create a variable before adding a comment."

A row with open comments shows a comment badge with a count beside its name.

2. Reply to a thread

  1. Find the thread in the Active tab.
  2. Type in the Reply… box under the thread.
  3. Select Reply.

A reply goes to the thread root. Each thread has one level of replies.

3. Resolve or reopen a thread

  1. Select the check button at the top of the thread. Its accessible name is Resolve thread.
  2. The thread moves to the Resolved tab.
  3. To reopen it, open Resolved and select the button again. Its accessible name is then Reopen thread.

Only the thread root can be resolved, not a single reply. A resolved thread stays in the model. Resolve a thread after you record the decision.

4. Mention a teammate

Type an @ handle in the comment, for example @morgan.lee. The panel highlights the handle. A handle can contain dots inside it. A full stop at the end is not part of the handle.

A handle is text in the comment. Eigenn stores it with the comment, but it does not send a notification. Tell the person when they must act.

5. Comments follow the scenario

Each thread belongs to the scenario that was active when you started it.

EventResult
You read the baseYou see only the threads started in the base.
You read a scenarioYou see only the threads started in that scenario. The empty state counts the threads that belong to another scenario.
You promote the scenarioIts threads move to the base.
You delete the scenarioIts threads become archived and leave the panel.

6. Comments in a shared view

A teammate who opens a shared view can read the threads only when Eigenn has turned on the planning context panel for your team. The reader sees only the threads on rows, periods, and scenarios that the view includes. Archived threads never show. A reader cannot add, reply to, or resolve a comment. The shared view does not save these actions.

Related

  • Collaboration
  • Share a model and set access
  • Create a scenario
  • Collaborate on a planning model

Collaboration

Discuss a planning model in row comments, share focused saved views with teammates, and control access with team roles.

Common formulas: cash and balance sheet

Formulas that carry a cash or balance-sheet balance from one period to the next.

On this page

1. Add a comment2. Reply to a thread3. Resolve or reopen a thread4. Mention a teammate5. Comments follow the scenario6. Comments in a shared viewRelated

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesApproval PoliciesAssistant AutomationAssistant Command CenterAssistant Workspace and Saved WorkBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer FieldsCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionFiles and Document VaultFinancial Analytics and ReportsFinancial OverviewInbox and ApprovalsInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewPlanning Data and DimensionsPlanning Models and FormulasPlanning Time and ActualsPlanning UncertaintyPlanning Versions and CollaborationPlanning Views and ExportsPlans and AdjustmentsReceivablesReceivables AnalyticsReceivables ControlsRolling Budget CloseScenario PlanningSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransaction CodingTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow OutcomesWorkflow PausesWorkflows
OverviewBudget vs. ActualsBuild a Driver-Based Planning ModelBuild and Review a ForecastBuild Your First WorkflowCollaborate on a Planning ModelCompare and Share Planning ScenariosConfigure Approval PoliciesConfigure Assistant OperationsConfigure Customer FieldsConfigure Notifications and BrandingConfigure Planning Time and ActualsConfigure Receivables ControlsConnect Planning Data and ActualsConnect Transaction RecordsConsolidationCreate and Manage CustomersCreate and Send InvoicesCreate Your First Planning ModelDeveloper API SetupFirst Cash ReviewHeadcount PlanningInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsRevenue ForecastingReview a Customer Finance RecordReview, Restore, and Export a Planning ModelRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Planning Uncertainty AnalysisRun Your First Command Center ReviewSave and Share Assistant WorkSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
Overview

Concepts

DataDimensionsFormulasScenarios

Variables

VariablesChange an input over timeCreate a variableFormat a variableOrganize variablesTime totalsUse a variable from another modelVariable types

Time

TimeLast actual dateRoll the model forwardTime granularityTime settings

Formulas

FormulasBlanks and helpersCommon formulas: cash and balance sheetCommon formulas: cohortsCommon formulas: currency and multiple entitiesCommon formulas: headcount and payrollCommon formulas: SaaS metricsCommon formulas: seasonalityConditionalsDimension referencesFormula syntaxFunctionsTime referencesTroubleshoot formulasValues with uncertaintyWrite a formula

Charts and Dashboards

Charts and dashboardsCompare scenarios and versionsCreate a chartExport and shareTablesTime aggregation in charts

Dimensions

DimensionsApply a dimensionCreate a dimensionDimension examplesDimension totalsThe Dimensions page

Data

DataChoose cash or accrual for XeroConnect a data sourceLink a variable to dataRefresh and check actualsUse transaction categories as actuals

Data Integrations

Data integrationsBank transactionsCSV importFortnoxQuickBooksStripeXero

Views

ViewsCreate and edit a viewFilter a viewShare a view

Versions

VersionsCompare versionsRestore a versionSave a version

Scenarios

ScenariosCompare scenariosCreate a scenarioPlans and adjustmentsStress tests and shocks

Collaboration

CollaborationComment on a modelShare a model and set accessTeam roles and planning access

Managing Models

Managing modelsDuplicate a modelExport a modelModel limits and performanceStart from a templateThe models home and foldersTrash, restore, and delete a model
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API
Overview
Overview