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

# Prompt collaboration: annotations and version control

> Comment on specific lines of a prompt, propose edits, and roll back to any previous version. Treat your prompts the way your engineers treat code.

Prompts in the iBlueprint Prompt Library are collaborative documents. Every prompt has an annotation thread for inline discussion and a full version history you can diff and roll back to — so your team can iterate without losing the wording that already works.

## Annotations

Annotations are inline comments attached to a specific line or selection inside a prompt. Use them to suggest rewrites, flag risky instructions, or capture why a particular phrasing exists.

### Leaving an annotation

1. Open a prompt and switch to **Edit** mode.
2. Highlight the text you want to comment on, or click a line gutter to attach the comment to the whole line.
3. Click the **comment** icon that appears, write your note, and press **Send**.

Annotations support `@mentions`. Mentioned teammates get an in-app notification and an email if their account has email alerts enabled.

### Resolving annotations

Each annotation thread has a **Resolve** button. Resolved threads collapse into the prompt's sidebar and can be reopened from the **Resolved** tab. The full history of who said what — including resolved threads — is preserved permanently.

<Tip>
  Annotations follow the line they were attached to as the prompt is edited. If the line is deleted, the annotation moves to the **Orphaned** section of the sidebar so the conversation is never lost.
</Tip>

### Suggesting an edit

Inside an annotation, click **Suggest edit** to attach a proposed replacement for the highlighted text. Reviewers can **Accept** the suggestion (which applies the change as a new version) or **Dismiss** it.

## Version control

Every save creates a new version. iBlueprint keeps the full history — there is no retention limit on versions for prompts in the Organization or Personal scopes.

### Viewing history

Open a prompt and click **History** in the top-right toolbar. The history panel lists every version with:

* Version number (`v1`, `v2`, …) and timestamp
* The author of that version
* A short commit-style message (optional, prompted on save)
* The model the prompt was tested against at the time

### Diffing versions

Click any two versions in the history list to see a side-by-side diff. Inserted lines are highlighted in green, removed lines in red, and changed lines show the inline word-level diff. Variables and metadata changes (default model, tags, description) are diffed in a separate panel below the body diff.

### Rolling back

From the history panel:

1. Select the version you want to restore.
2. Click **Restore this version**.
3. Confirm the restore. iBlueprint creates a new version that is a copy of the selected one — your history is never rewritten, so the rollback itself is an auditable event.

<Warning>
  Rolling back a prompt that is referenced by published Blueprints takes effect on the **next** execution. Already-running executions continue with the version they were started against.
</Warning>

### Branching and merging

For larger edits, click **Branch** in the history panel to create a named working copy of the prompt. Branches live alongside the main prompt and have their own version history. When you are ready, open the branch and click **Merge into main** — iBlueprint shows a final diff and creates a single squashed version on the main prompt.

## Permissions

| Action                     | Personal scope | Organization scope         | Public scope            |
| -------------------------- | -------------- | -------------------------- | ----------------------- |
| Read prompt and history    | Author only    | All org members            | Everyone                |
| Leave annotations          | Author only    | All org members            | Disabled                |
| Edit prompt body           | Author only    | Members with `prompt.edit` | Disabled — fork to edit |
| Restore a previous version | Author only    | Members with `prompt.edit` | N/A                     |
| Delete prompt              | Author only    | Admins                     | N/A                     |

`prompt.edit` is granted by default to the **Member** role. Admins can scope it down per workspace in **Settings → Roles**.