Review tab
Review the selected node's status, relations, and attributes, and add related nodes.
Select a node and open Review.
Use the relation action buttons to add a related child node: Answer, Support, Oppose, Require, or Refine.
Use the status, relation, and attribute summaries to understand what still needs review.
Decide tab
Use this tab on decision nodes to select an answer option, assign approvers, capture approvals, and manage the decision lock.
Select a decision node and open Decide.
When the node has multiple incoming Answer relations, assign a decision-maker and select one option.
After an option is selected, add approvers if the decision needs explicit approval.
Approvers set their own response. When all selected approvers approve, the decision locks automatically.
The assigned decision-maker can unlock the decision, which clears approvals and allows another review cycle.
If options are missing, create Answer relations to the current node first.
If option selection is disabled, confirm you are the assigned decision-maker and the decision is unlocked.
If approval controls are disabled, confirm you are the relevant approver or decision-maker.
Details tab
Write and revise the selected node, and manage files attached to that node.
Select a node in the tree, list, or table.
Edit the node body in the rich-text editor. Drafts autosave while you work, and committed edits are recorded in history.
Add up to five attachments, one file at a time.
Use attachment controls to download clean files, preview clean images, reorder files, or delete attachments.
If edits are disabled, check your role and whether the node is locked by a workflow.
If a file cannot be downloaded, check its scan status.
If the Add file button is disabled, the node may be read-only or already at the five-file limit.
Relations tab
Maintain explicit source-to-target relations for the selected node and inspect its local relation graph.
Open Relations for the selected node.
Click Add relation to add a row.
Choose a relation and target node. Rows auto-save after both values are selected.
Use the delete button on a row to remove that relation.
Use the subgraph filters to inspect all relations over the selected node.
Review shared terms and similar nodes at the bottom of the tab.
If a row will not save, choose both relation and target.
If you see a duplicate warning, remove one identical source, relation, and target tuple.
If the target list is missing a node, confirm the node exists in the loaded log.
Tags & Attributes tab
Add tags and structured metadata for filtering, grouping, reporting, and review consistency.
Enter comma-separated tags and click Apply.
Add or edit custom attributes in the inline attribute list.
Attribute edits auto-save after changes are valid.
Use the status text to confirm whether changes are saved or need correction.
If autosave reports an error, fix duplicate or invalid attribute rows first.
If a governance or attachment field is not listed, it is reserved and managed by the app.
If tags do not highlight as expected, normalize spelling and casing.
History tab
Inspect the selected node's audit trail and use permitted note, revert, and restore actions.
Open History for the selected node.
Filter by change badge when you need a narrower view.
Expand entries to inspect deferred diffs and context.
Edit eligible history notes where permitted.
Use revert or restore controls only after confirming the target entry.
If the timeline seems incomplete, confirm the correct node is selected and reload details.
If revert or restore is unavailable, the entry type or your role may not allow it.
If two entries look similar, compare timestamps, actor labels, and notes.
Actions tab
Track follow-up work tied to the selected node, including assignees, deadlines, and required completion evidence.
Open Actions and review the Open, Overdue, and Assigned to me summaries.
Use filters to focus the open action list.
Create a new action from a template or custom description.
Select the required completion relation, assignees, and optional deadlines.
Assignees complete their work by selecting or creating descendant evidence that satisfies the configured relation.
The action creator can complete or cancel the whole action for all assignees.
If Add action is disabled, enter text and choose a required completion relation.
If completion is blocked, create or select matching descendant evidence first.
If an action is hidden from detail view, only the creator and assignees can open it.
AI tab
Generate candidate sub-nodes and relation mappings for the selected node, then apply selected suggestions.
Open AI and wait for the organization AI availability check.
Select one or more relation intents: Answers, Supports, Opposes, Requires, or Refines.
Add optional prompt guidance.
Generate suggestions, review text and relation badges, then select the suggestions to apply.
Click Apply selected to create generated sub-nodes and persist relation mappings.
If AI is unavailable, ask an organization admin to configure the AI key.
If generation is disabled, confirm edit access and select at least one relation intent.
If output is too broad, narrow the prompt guidance to a specific domain or constraint.
Type tab
Confirm the canonical node type used by current logs.
Open Type.
Review the selected type value.
If editing is allowed, choose an available type option. Current logs use the canonical node type.
If Type is disabled, check your edit permissions.
If older data contains legacy type labels, current save flows normalize them to the canonical type.
Agreement tab
Maintain the older agreement view for participant positions, decision-maker assignment, lock state, and status override controls.
Open Agreement where it is available.
Update your own agreement value when permitted.
Assign a decision-maker while the node is unlocked.
The decision-maker can lock or unlock the node and set a status override.
If you choose Disagree, the app can create a related explanation sub-node.
If the app opens Review instead, use Review for the current decision workflow.
If lock controls are unavailable, confirm you are the assigned decision-maker.
If values are disabled, the node may be locked or your role may be read-only.
Still stuck on something?
Please reach out with your questions.