---
title: "2. Adding a Decision Matrix"
slug: "2-adding-a-decision-matrix-1"
updated: 2026-08-27T20:20:59Z
published: 2026-09-23T13:00:19Z
canonical: "wiki.cobblestonesoftware.com/2-adding-a-decision-matrix-1"
---

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

# 2. Adding a Decision Matrix

**COBBLESTONE SOFTWARE**

Contract Insight — User Guide

**2. Adding a Decision Matrix**

*03. Admin User Manual › Decision Matrices › 2. Adding a Decision Matrix*

**Note:** Each procedure in this guide begins at the Contract Insight homepage, so any section can be followed on its own. Custom fields are configurable, so the exact field list on a contract category record may vary between environments.

# 1. Overview

A new decision matrix is created from Surveys > **Decision Matrices** via the **+ Add** button, which opens the same kind of header form seen on an existing matrix record: Name, Description, an **Active** toggle, and a **Public** toggle, alongside system-managed audit fields (Created By, Date Created, Decision Matrix ID, UpdatedBy, Date Updated). This QA environment's decision matrix records do not expose a separate, granular per-employee assignment picker on the record itself — the **Public** field is the closest visibility control found: a matrix's audience appears to be governed by this **Public** Yes/No flag rather than by an explicit list of named employees on the matrix record. Once created, a matrix's actual question content is built separately in the **Decision Matrix Designer** (reached from the list's builder icon), which is where the tree of questions, answers, and endings is assembled before the matrix is put to use.

# 2. Key Elements

- A new decision matrix is created from the **Decision Matrices** list via **+ Add**, using the same Name/Description/**Active**/**Public** header fields as an existing matrix record.
- The **Public** toggle (Yes/No) is the visibility-related control found directly on a decision matrix record in this environment.
- No separate, per-employee assignment list was found on the matrix record itself in this QA environment; audience/visibility appears governed at the **Public**-flag level rather than by naming individual employees on the record.
- After a matrix is created, its actual question-and-branch content is assembled separately in the **Decision Matrix Designer**, reached via the builder icon on the **Decision Matrices** list.
- Decision Matrix ID and audit fields (Created By, Date Created, UpdatedBy, Date Updated) are system-managed and not editable on the creation form.

# 3. Quick Reference Summary

[TODO: content needed]