1D2Abetter decisions
Decision log reference

Help Hub

Understand every control in the log list, tree view, and detail pane, without leaving your decision workflow. Detail tabs, log-level panes, and visitor/user flows are documented below.

22 help topics
01

Review tab

Purpose

Review the selected node's status, relations, and attributes, and add related nodes.

How it works
1

Select a node and open Review.

2

Use the relation action buttons to add a related child node: Answer, Support, Oppose, Require, or Refine.

3

Use the status, relation, and attribute summaries to understand what still needs review.

Field definitions
Relation actions
Buttons that create a child node and persist the selected relation back to the current node.
Status
Whether the selected node has standing opposition that still needs to be resolved.
Relations
Incoming and outgoing relation links for the selected node.
Attributes
Visible attributes that can also be used as tree filters.
02

Decide tab

Purpose

Use this tab on decision nodes to select an answer option, assign approvers, capture approvals, and manage the decision lock.

How it works
1

Select a decision node and open Decide.

2

When the node has multiple incoming Answer relations, assign a decision-maker and select one option.

3

After an option is selected, add approvers if the decision needs explicit approval.

4

Approvers set their own response. When all selected approvers approve, the decision locks automatically.

5

The assigned decision-maker can unlock the decision, which clears approvals and allows another review cycle.

Field definitions
Decision-maker
The assigned user who can choose an answer option, manage approvers, and unlock a locked decision.
Options
Source nodes with an Answer relation targeting the current node.
Approvers
Users who must approve the selected option before the decision automatically locks.
Decision lock
The locked state created after all approvers approve. Unlocking starts approval again.
Troubleshooting

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.

03

Details tab

Purpose

Write and revise the selected node, and manage files attached to that node.

How it works
1

Select a node in the tree, list, or table.

2

Edit the node body in the rich-text editor. Drafts autosave while you work, and committed edits are recorded in history.

3

Add up to five attachments, one file at a time.

4

Use attachment controls to download clean files, preview clean images, reorder files, or delete attachments.

Field definitions
Node editor
The main editor for selected-node content.
Attachments
Per-node files. Images can be previewed after clean scan; non-image files download after clean scan.
Scan status
Clean files can be opened. Pending, blocked, or failed files remain unavailable until scan state permits access.
Troubleshooting

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.

04

Relations tab

Purpose

Maintain explicit source-to-target relations for the selected node and inspect its local relation graph.

How it works
1

Open Relations for the selected node.

2

Click Add relation to add a row.

3

Choose a relation and target node. Rows auto-save after both values are selected.

4

Use the delete button on a row to remove that relation.

5

Use the subgraph filters to inspect all relations over the selected node.

6

Review shared terms and similar nodes at the bottom of the tab.

Field definitions
Source
The selected node.
Relation
The relationship type: answers, supports, opposes, requires, or refines.
Target
The related node selected from the current log.
Subgraph
A local graph view showing relations over the selected node.
Troubleshooting

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.

05

Tags & Attributes tab

Purpose

Add tags and structured metadata for filtering, grouping, reporting, and review consistency.

How it works
1

Enter comma-separated tags and click Apply.

2

Add or edit custom attributes in the inline attribute list.

3

Attribute edits auto-save after changes are valid.

4

Use the status text to confirm whether changes are saved or need correction.

Field definitions
Tags
Reserved metadata stored under the tags key. Tag words are highlighted when they appear in node text.
Attributes
Custom key/value metadata. Reserved governance and attachment keys are not editable here.
Duplicate attribute name
A validation state shown when two editable rows use the same key.
Troubleshooting

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.

06

History tab

Purpose

Inspect the selected node's audit trail and use permitted note, revert, and restore actions.

How it works
1

Open History for the selected node.

2

Filter by change badge when you need a narrower view.

3

Expand entries to inspect deferred diffs and context.

4

Edit eligible history notes where permitted.

5

Use revert or restore controls only after confirming the target entry.

Field definitions
History entry
A recorded change for text, attributes, relations, moves, actions, attachments, or other node state.
Notes
Editable context for eligible entries. Some system entries are note-locked.
Revert / Restore
Revert applies eligible prior state; Restore re-adds a removed child node where supported.
Troubleshooting

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.

07

Actions tab

Purpose

Track follow-up work tied to the selected node, including assignees, deadlines, and required completion evidence.

How it works
1

Open Actions and review the Open, Overdue, and Assigned to me summaries.

2

Use filters to focus the open action list.

3

Create a new action from a template or custom description.

4

Select the required completion relation, assignees, and optional deadlines.

5

Assignees complete their work by selecting or creating descendant evidence that satisfies the configured relation.

6

The action creator can complete or cancel the whole action for all assignees.

Field definitions
Action template
A starter action that prefills text and the required completion relation.
Required completion evidence
A descendant node with the configured relation to the action's parent node.
Assignee deadline
An optional per-assignee due date, with overdue highlighting.
Completion evidence node
An existing or newly created descendant used to prove the assignee's work is complete.
Troubleshooting

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.

08

AI tab

Purpose

Generate candidate sub-nodes and relation mappings for the selected node, then apply selected suggestions.

How it works
1

Open AI and wait for the organization AI availability check.

2

Select one or more relation intents: Answers, Supports, Opposes, Requires, or Refines.

3

Add optional prompt guidance.

4

Generate suggestions, review text and relation badges, then select the suggestions to apply.

5

Click Apply selected to create generated sub-nodes and persist relation mappings.

Field definitions
AI availability
The organization-level policy and provider-key status. AI is disabled when unavailable or when the current role is read-only.
Relation intents
The relation types the generation request may use.
Prompt guidance
Optional text to steer the generated suggestions.
Generated suggestions
Proposed child-node text with relation and optional rationale.
Troubleshooting

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.

09

Type tab

Purpose

Confirm the canonical node type used by current logs.

How it works
1

Open Type.

2

Review the selected type value.

3

If editing is allowed, choose an available type option. Current logs use the canonical node type.

Field definitions
Selected type
The normalized type for the selected item.
Node type
The available type option for current decision-log nodes.
Troubleshooting

If Type is disabled, check your edit permissions.

If older data contains legacy type labels, current save flows normalize them to the canonical type.

10

Agreement tab

Purpose

Maintain the older agreement view for participant positions, decision-maker assignment, lock state, and status override controls.

How it works
1

Open Agreement where it is available.

2

Update your own agreement value when permitted.

3

Assign a decision-maker while the node is unlocked.

4

The decision-maker can lock or unlock the node and set a status override.

5

If you choose Disagree, the app can create a related explanation sub-node.

Field definitions
Agreement value
Your participant position for the selected node.
Decision-maker
The user allowed to manage lock and override workflows.
Status override
An explicit status value set through callable-managed governance fields.
Troubleshooting

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.

12

Share pane

Purpose

Manage private workspace access for the current log without making the log public.

How it works
1

Open Share from the log top bar.

2

Copy the workspace link when you need to send the current private log URL to someone who already has access.

3

Enter one email address per line, choose Viewer or Editor, and send invites.

4

Use People with access to review members, change roles, remove users, and refresh pending invites.

Field definitions
Workspace link
A private app link. It does not grant access by itself.
Viewer
A member who can read the log but cannot edit it.
Editor
A member who can edit the log according to app permissions.
Pending invite
An email invitation that has been sent but not yet accepted into active access.
Troubleshooting

If Share is unavailable, confirm you are in a workspace log and have owner permissions.

If an invite fails, check the email format and retry after refreshing access.

13

Publish pane

Purpose

Create read-only snapshots of a log or template and control who can view them outside the editable workspace.

How it works
1

Open Publish from the log top bar.

2

Choose private, internal, or public visibility for a decision or template snapshot.

3

Publish a snapshot, then preview, copy its link, activate a version, or unpublish it from the snapshot list.

4

For public snapshots, choose whether to list them in the Decision Library and allow search indexing.

5

Maintain library details such as description, tags, and industry metadata.

Field definitions
Snapshot
A read-only copy of the log or template at publish time.
Internal
A visibility mode for shared users and users in the log's organization.
Public
A visibility mode where anyone with the published URL can read the snapshot.
Active version
The published version readers see for the current content type.
Troubleshooting

If public options are disabled, confirm the selected visibility is public.

If a published link is unavailable, confirm the snapshot has a slug and active version.

14

Articles pane

Purpose

Review and create articles that explain the current log with references back to its decision nodes.

How it works
1

Open Articles from the log top bar.

2

Review articles connected to the current log, including status, author, update date, references, and reading time.

3

Click an article row to open your draft or a published article that is available to read.

4

Use New article when you have edit permission and want the current log preset as the primary source.

Field definitions
Primary log
The log an article is chiefly explaining or using as evidence.
References
Decision nodes cited from the current log.
Article status
Draft, review, published, returned, or archived state for the article.
Troubleshooting

If New article is missing, confirm you have edit permission for the log.

If an article does not open, confirm it is your draft or has been published.

15

History pane

Purpose

Review log-level notifications and change history across the current decision log.

How it works
1

Open History from the log top bar.

2

Use author filters and date range controls to narrow the timeline.

3

Expand entries to inspect change context, linked nodes, and recorded notes.

4

Use unread/read state to keep track of activity you have already reviewed.

Field definitions
Notification
A log activity entry produced by edits, comments, actions, relations, publication, or other tracked changes.
Author filter
A control for showing or hiding entries from selected actors.
Date range
A time window used to focus the visible history entries.
Troubleshooting

If History is empty, confirm you are viewing a workspace log rather than a published read-only route.

If expected entries are missing, clear filters or reload the log.

16

Visitor landing

Purpose

Introduce 1D2A to signed-out visitors and route them to public examples or sign-in.

How it works
1

Use the landing page to understand the decision-log model and preview example decisions.

2

Choose Library to browse published logs and templates without signing in.

3

Choose Sign in / up or Create your first log when you are ready to create a private workspace.

17

Public Library

Purpose

Browse published decision logs and templates that are available before sign-in.

How it works
1

Open Library from the visitor navigation.

2

Select a published decision log or template to inspect its read-only viewer.

3

Use Create decision log to sign in and start a private log based on your own decision.

Field definitions
Public log
A published snapshot anyone can open by URL.
Template
A published reusable decision-log structure that signed-in users can copy to their workspace.
18

Published viewer

Purpose

Read a published snapshot without changing the original workspace log.

How it works
1

Open a published log or template from the Library or a shared public URL.

2

Select nodes to inspect their text, relations, attributes, and visible context.

3

Use relation links and attribute filters to stay inside the read-only viewer.

4

Sign in when you want to create your own log or reuse a template.

Troubleshooting

If editing controls are missing, you are viewing a published read-only snapshot.

If access is denied, the snapshot may be internal to an organization or no longer active.

19

Sign in

Purpose

Create or access a private workspace where decision logs can be edited, shared, and published.

How it works
1

Use Google sign-in for the fastest handoff, or enter email and password.

2

Use Create account from the email form when you do not yet have an account.

3

Use Forgot password after entering your email to request a reset message.

4

After sign-in, the app returns you to your logs or the workflow you started from.

20

My logs

Purpose

Find and open private decision-log workspaces you own or can access.

How it works
1

Open My logs from the user menu or after signing in.

2

Select a log to open its editable workspace.

3

Use role, publication, and open-action badges to understand current access and activity.

4

Use Create decision log or Import decision log to add new workspace logs.

21

Signed-in Library

Purpose

Browse public and organization-internal published snapshots available to your account.

How it works
1

Open Library from the user menu.

2

Filter by title or summary to narrow public, template, and internal entries.

3

Open a published item to read it, or use a template to copy it into your workspace when available.

22

Create & import

Purpose

Start a new decision log from scratch, generate an AI draft where enabled, or bring in a JSON export.

How it works
1

Use Create decision log to name a new private workspace and choose the applicable organization context.

2

If AI drafting is available, provide the decision prompt and review the generated log before relying on it.

3

Use Import decision log to load a supported JSON export into a new workspace log.

4

After creation or import, review permissions, title, nodes, and relations before sharing or publishing.

Troubleshooting

If import fails, confirm the file is valid JSON and below the size limit.

If AI draft is unavailable, the selected organization may not have AI configured.

Still stuck on something?

Please reach out with your questions.

Contact support