---
title: "Collaboration"
description: "Work with your team inside an assessment using Messages, @mentions, requirement tags, notifications, and live presence."
version: "en"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.kliper.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Collaboration

Kliper is built for team-based assessments. Each assessment has a **Messages** thread, **@mentions** that notify teammates, **#requirement tags** that link a message to a control, a **notification** system, and **live presence** so you can see who else is in the assessment.

## Messages

Open an assessment and select the **Messages** tab (also available as a panel in the section workbench's right rail). Messages are a single chat-style thread for the assessment.

1. **Write a message**

   Type in the composer at the bottom. The placeholder reminds you: *"Type a message… Use @name to mention or #1.2.3 to tag."*
2. **Send it**

   Click the **send** button to post. Pressing **Enter** does **not** send — in the composer, Enter only confirms a selection in the @mention or #tag dropdown, so you can write multi-line messages freely.
3. **Reply in a thread**

   Click **Reply** under any message to nest a response beneath it. Replies are collapsible with a count ("3 replies").

Messages are ordered **chat-style — newest at the bottom**, grouped under **Today / Yesterday / date** separators.

**Deleting:** you can delete your own messages (trash icon on hover). **Admins and Managers can delete any message** in the assessment.

> **Note**
>
> Messages don't have an **edit** action, and there's no resolve/unresolve or All/Unresolved/Resolved filter — it's a running conversation, not a ticket queue. To correct something, delete and repost.

## @Mentions

Type **`@`** in the composer to open a typeahead of organization members (filter by name or email; each result shows the avatar and role). Pick someone to insert the mention.

- In a posted message, a mention renders as an inline badge (e.g. **@Rivera**); hover it for the person's details.
- A mentioned teammate is notified (in-app and in real time; email/push follow their notification settings). Mentions are limited to people with access to the assessment.

## #Requirement tags

Type **`#`** followed by a requirement number — `#1.2.3`, `#7.1.1`, even deeply nested IDs (or the `req-1` alias) — to link the message to a specific control. A typeahead shows the matching requirement number and label. Tags also auto-detect when you type a `#<number>` pattern.

You can tag **individual controls**, not just sections. Posted tags render as chips (`1.1.1` / `§1.2`); **hover** a chip for the requirement's title and status, and **click** it to jump to that exact control in the editor — from the drawer or the full Messages view. Mention chips get the same treatment, showing the member's photo and role on hover.

These also work in the **section right-drawer composer**, so a conversation can happen next to the control it's about.

## Notifications

The **notification bell** in the top bar shows your unread count (capped at "9+"). Open it for your most recent notifications, grouped under **Today / This week / Earlier** and ordered newest-first. Tabs let you view **All**, **Unread**, or **Mentions**, and **Mark all read** clears the unread state.

| Type | Icon | When it fires |
|---|---|---|
| **Mention** | violet `@` | Someone @mentions you |
| **Task assigned** | amber clipboard | A task is assigned to you |
| **Task due** | red clock | A task you own is approaching its due date |
| **Project assigned** | blue briefcase | You're added to an assessment |
| **Assessment due** | red clock | An assessment you're on is approaching its due date |
| **Cortex** | violet sparkles | A Cortex-related update |
| **Success / Warning / Error** | green check / amber triangle / red alert | System events |

Notifications arrive in **real time**; if the live connection drops, the bell falls back to polling. Browser **push** notifications are delivered too once you grant permission. Click any notification to jump to its source.

## Live presence

When others are in the same assessment, a **live presence** indicator appears in the workbench header:

| State | What you see |
|---|---|
| **Just you** | A muted "Just you" label |
| **Others present** | Overlapping avatars with a pulsing green **Live** dot |
| **4+ present** | Three avatars plus a **+N** overflow badge |

Hover an avatar (or the **+N** badge) to see each person's name and current status (viewing, editing, or typing).

## Assessment collaborators

Who can open and edit an assessment is controlled by its **collaborator** list (roles **Editor** or **Viewer**, plus the pinned **Owner**). Manage it from the **Edit Assessment** dialog — see [Managing collaborators](/guides/scoping-and-workbench#managing-collaborators) in the Workbench guide.

## Audit trail

Collaboration actions (and every assessment change) are recorded in the assessment's **Audit Trail** tab — who did what, when, with before/after values. For a full field-level export, see [Audit trail export](/operations/admin-dashboard#audit-trail-export).

Source: https://docs.kliper.dev/operations/collaboration/index.mdx