Writing and formatting

Use CommonMark formatting, slash commands, and @mentions to write rich, structured content inside case descriptions, notes, and comments.

Where the rich-text editor appears 

The same editor is used across all case content surfaces:

🪄Tip

Slash commands (/) 

Type / anywhere in the editor to open the command menu. The available commands are:

ℹ️Info

Mentions (@) 

Type @ to open the mention picker. Mentions are not limited to users — you can mention a wide range of Tines entities:

🪄Tip

Images and uploads 

You can add images to any rich-text surface:

  • Paste from clipboard — take a screenshot and paste (Ctrl/Cmd + V) directly into the editor. The image renders inline immediately.

  • Drag and drop — drag an image file from your desktop into the editor.

  • Slash command — type /image to insert via the command menu.

Images are uploaded as case files and are subject to the 60 MB file size limit per file.

🪄Tip

Code blocks 

Use code blocks for preserving formatting on structured content like log entries, IOC lists, JSON payloads, or CLI output.

  • Via slash command: type /code and select Code block.

  • Via markdown shortcut: type ``` and press Enter.

Content inside a code block is rendered in a monospace font and is not parsed for formatting.

CommonMark and GFM formatting 

The editor supports CommonMark and GitHub Flavored Markdown (GFM) syntax. You can type markdown directly or use the toolbar and slash commands.

🪄Tip

Formulas in case content 

When formulas are enabled on a rich-text surface, you can embed Tines formula expressions directly in case content. This is primarily relevant when case content is populated by story automations — allowing dynamic values to be resolved at write time.

Best practices 

  • Use headings in descriptions to create a scannable structure — they populate the table of contents.

  • Paste images inline rather than attaching files — they're immediately visible to all viewers.

  • Use @mentions intentionally — mentioning a user subscribes them and triggers notifications.

  • Use code blocks for IOCs, logs, and structured data to preserve formatting and readability.

  • Promote decisions from comments into the description or a note block so they're durable and findable.

Was this helpful?