How-to

Approve it so the team can rely on it

The candidate becomes approved team knowledge. Until a person approves it, it is only a proposal.

39 sFor: Reviewer or workspace decision owner8 steps

Read the steps OR watch the video. Both teach the same outcome, and neither is needed for the other.Jump to the video

Guided Quick Start

Six steps from sign-in to useful context

Follow the sequence or jump to any lesson. Every step also works on its own, with written instructions alongside the optional video.

Step 4 of 6

  1. Step 1Sign in and choose your workspaceGoal: Reach the right workspace before doing anything else.33 s
  2. Step 2Know where to startGoal: Know the three places you will use: the Home queue, Add to DM and Knowledge.25 s
  3. Step 3Record your first decision and whyGoal: A decision candidate with its rationale is saved for review.37 s
  4. Step 4Approve it so the team can rely on itGoal: The candidate becomes approved team knowledge.39 s
  5. Step 5Find it again laterGoal: Find the decision, its reason and its evidence.44 s
  6. Step 6Put it to workGoal: Ask DM from the decision, and hand it to an agent task as context.45 s

Quick steps

  1. Click ReviewYour candidate waits in Review. Select Review.
    1. Start on DM Home (/).
    2. Click "Review". The next view is "Review queue" (/inbox).

    What it means: Your candidate waits in Review. Select Review.

  2. Click Select the candidate (Review)Open the candidate.
    1. Click "Select the candidate (Review)". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Open the candidate.

  3. Click ContinueCheck the statement and its reason. They are what you recorded.
    1. Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Check the statement and its reason. They are what you recorded.

  4. Click NextPlacing it in a project is optional here.
    1. Click "Next". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Placing it in a project is optional here.

  5. Click Continue to RefineRead the checks. Here, nothing blocks approval.
    1. Click "Continue to Refine". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Read the checks. Here, nothing blocks approval.

  6. Click ContinueYou could correct the wording here. It's right, so continue.
    1. Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: You could correct the wording here. It's right, so continue.

  7. Click ApproveOnly a person can approve. Select Approve.
    1. Click "Approve". The next view is "Two reviewers for production schema changes" (/decisions/dec-review).

    What it means: Only a person can approve. Select Approve.

  8. Review approved decisionIt's now approved team knowledge, with its reason on record. Next, find it again.
    1. Review "Approved decision": "What was decided".

    What it means: It's now approved team knowledge, with its reason on record. Next, find it again.

Editing, requesting evidence, rejecting and conflict handling are not shown; this candidate has no issues for the checks to flag.

Which roles may approve is not verified; the demo signs in as a workspace editor and the simulated backend accepts the approval.

Descriptive transcript

Read the full transcript, including what happens on screen

Demo environment · synthetic workspace and data · backend responses are simulated. Quick Start 4 of 6
The candidate, the checks, the approval and the approved decision are SIMULATED: this guide uses the real DM guided review with a synthetic workspace, and the approval response is fixture data, not a deployed backend. What you may review and approve depends on your role and workspace; nothing in DM approves a candidate automatically. Quick Start clips 1 to 6 follow one example workspace, Acme Platform Team.

A banner reading "Demo environment · synthetic workspace and data · backend responses are simulated" stays on screen for the whole video.

00:00–00:05 · start

On screen: Start on DM Home (/). Click "Review". The next view is "Review queue" (/inbox). A highlight marks "Review".

Narrator: Your candidate waits in Review. Select Review.

00:05–00:07 · pick

On screen: Click "Select the candidate (Review)". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight marks "Review".

Narrator: Open the candidate.

00:07–00:12 · understand

On screen: Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Statement and reason" marks "Any migration that touches production schema needs approval from two…".

Narrator: Check the statement and its reason. They are what you recorded.

00:12–00:17 · place

On screen: Click "Next". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Next" marks "Next →".

Narrator: Placing it in a project is optional here.

00:17–00:22 · check

On screen: Click "Continue to Refine". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Blocking issues" marks "0".

Narrator: Read the checks. Here, nothing blocks approval.

00:22–00:27 · refine

On screen: Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

Narrator: You could correct the wording here. It's right, so continue.

00:27–00:31 · confirm

On screen: Click "Approve". The next view is "Two reviewers for production schema changes" (/decisions/dec-review). A highlight marks "Approve".

Narrator: Only a person can approve. Select Approve.

00:31–00:39 · approved

On screen: A highlight labelled "Approved decision" marks "What was decided".

Narrator: It's now approved team knowledge, with its reason on record.

Narrator: Next, find it again.

Last verified against the product on .

How-to 37 s7 steps

Record your first decision and why

A decision candidate with its rationale is saved for review. Write the decision first. Add the reason while it is fresh.

For: Workspace member who can create decisions

How-to 44 s6 steps

Find it again later

Find the decision, its reason and its evidence. Months later, search beats remembering.

For: Any authorized workspace user

How-to 45 s8 steps

Put it to work

Ask DM from the decision, and hand it to an agent task as context. An approved decision is only useful if it is used.

For: Workspace member and agent user

How-to 25 s4 steps

Know where to start

Know the three places you will use: the Home queue, Add to DM and Knowledge. Three places are enough to get started.

For: Any signed-in workspace member