1. Docs
  2. Cases
  3. Overview of cases
  4. Case content

Case blocks

Last updated Open markdown version

Case blocks let you divide case content into discrete, reorderable sections below the description — each with its own title, type, color, and visibility settings.

When to use blocks

Use blocks when a case has enough content that a single description isn't sufficient. Blocks let you create clearly separated sections like "Evidence," "Timeline," "Remediation Steps," or "Approval."

Description section

The description is the beginning of the case content and is followed by case blocks. It supports a large volume of text and the contents of the description are included in search results. You cannot re-order the description within the case structure or table of contents.

Case blocks and groups

Click each button in the toolbar at the bottom of the case to add content below the description section. Cases use a concept called "Blocks" to help structure and format your content. Each block can be added via the case toolbar at the bottom of the case below. Add blocks to the case, then add your content.

  • Blocks can be grouped together

  • You can re-arrange blocks or groups of blocks using the table of contents or options menu within a block

  • Blocks can be set to one of 8 pre-defined colors.

References & formatting

  • Use the / shortcut to open the formatting menu. The formatting options support Headings, bullet lists, ordered lists, task lists, a code block, a quote, inserting an image via link, pasting an image, a table, or a callout.

  • Use the @ shortcut to open the reference menu. The reference options support mentioning stories, users, pages, other cases, as well as blocks within the current case. You can also include shortcuts to case primitives like fields and case actions.

Types of blocks

Cases support several block types. Some are multi-instance (you can add many per case) and some are single-instance (one per case, automatically created or added once).

💡 Tip: Single-instance blocks are created once and cannot be duplicated. If you don't see an option to add one, it already exists in the case.

Adding a block

Click the buttons in the toolbar at the bottom of the case to add a block below the description. The new block appears at the end of the case content by default.

Block titles

Every block has a title (max 100 characters) that appears in the table of contents. Set a clear, descriptive title — it's the primary way teammates navigate the case structure.

Block color

Note blocks can be assigned a background color to visually distinguish sections. Available colors include standard palette options visible in the block settings.

💡 Tip: Use color consistently across your team. For example: blue for evidence, red for critical findings, green for completed remediation, gold for pending review.

Block groups

Block groups let you nest related blocks under a collapsible parent. In the table of contents, a block group appears as an expandable section.

  • Create a block group via the toolbar.

  • Drag existing blocks into the group, or set the block_group_id via the API.

  • Child blocks within a group can be reordered independently.

Block groups are especially useful for phases of an investigation (Triage → Analysis → Remediation) or for organizing large cases with many blocks.

Reordering blocks

Blocks can be reordered by:

  • Dragging in the table of contents sidebar.

  • Using the API to set block position.

⚠️ The description is always pinned to the top of the case. It cannot be reordered or placed below blocks.

Hiding blocks

Select Hide from the block's options menu to hide it from the main case content view. Hidden blocks:

  • Are still listed in the table of contents (dimmed).

  • Can be spotlighted by clicking them in the TOC — this temporarily displays their content inline without unhiding them.

  • Remain accessible via the API.

Use this to keep raw data, verbose logs, or intermediate evidence accessible without cluttering the case view.

Sensitive blocks (hidden from exports)

Note blocks and HTML blocks have a Sensitive toggle. When enabled:

  • The block is labeled "Sensitive — Hidden from exports."

  • The block's content is excluded from PDF exports of the case.

  • The block remains fully visible and editable within the case itself.

⚠️ Important: This is not an access control — all case viewers can see sensitive blocks. It only controls export behavior.

PDF export behavior

When a case is exported to PDF, the export includes:

  • The case description

  • Note blocks (and note blocks nested inside block groups) — unless marked as sensitive

  • Case details, fields, tasks, activities, and records

The following block types are not rendered in the PDF body: file blocks, HTML blocks, linked cases, closure conditions, metadata, and case action blocks. If content must appear in a PDF export, place it in the description or a non-sensitive note block.

Table of contents interaction

The table of contents sidebar reflects the full block structure:

  • Description headings and block titles are listed.

  • Block groups are collapsible.

  • Hidden blocks appear dimmed but are clickable (spotlight behavior).

  • Click any item to scroll directly to that section.

The TOC can be toggled between persistent and peek mode via the Contents button at the top of the sidebar. In peek mode, the sidebar hides until you hover near the left edge.

Automation: blocks via the API

Blocks can be created, updated, and deleted programmatically:

  • Create a block — POST /api/v2/cases/{case_id}/blocks with block_type, title, optional block_group_id, position, hidden, and content.

  • Update a block — PUT /api/v2/cases/{case_id}/blocks/{block_id} to change title, position, visibility, group membership, or content.

  • List blocks — GET /api/v2/cases/{case_id}/blocks to retrieve all blocks in a case.

Use action templates from the template library to integrate block management into your story automations.

Best practices

  • Standardize block structures using case templates so every case of the same type starts with the same sections.

  • Use block colors consistently across your team to create visual conventions.

  • Hide verbose blocks (raw logs, API responses) to keep the case readable — they remain accessible via the TOC.

  • Use block groups for investigation phases (Triage, Analysis, Remediation) or logical groupings (Evidence, Actions, Approvals).

  • Mark sensitive blocks to prevent confidential content from appearing in PDF exports.

  • Max 50 blocks per case — if you're approaching this limit, consolidate related content or use block groups.

Was this helpful?