# Comments
## Specs
| Label | Value |
| ------------------------- | ----------------------------- |
| **Version** | 3.3.0 (updated on 2025-10-29) |
| **Developer** | Labii Inc. |
| **Type** | Section |
| **Support Configuration** | No |
## Overview
The Comments widget enables users to add threaded, timestamped comments directly to any Labii record, keeping all related communication in one place alongside experimental data. Users can manually type comments or import email conversations from Gmail or Outlook, eliminating the need to copy-paste external communications. Importantly, the widget operates in read-only mode — meaning comments can be added even when the record itself is locked — ensuring uninterrupted dialogue and comprehensive record-keeping throughout a record's lifecycle.
{% hint style="warning" %}
The Comments widget is **not GLP compliant**. Data entered cannot be used for patient applications or submissions subject to FDA regulation.
{% endhint %}
## Use Cases
* **Customer Communication Tracking**: Log email exchanges with customers, leads, or vendors directly on a CRM record to maintain a complete communication history.
* **Experiment Collaboration**: Leave inline observations, questions, or reviewer feedback on an experiment record without altering the locked experimental data.
* **Email Thread Archival**: Import Gmail or Outlook email threads into a record to preserve the full conversation context alongside the related sample or project.
* **Project Updates**: Post status updates and discussion notes on project records so all team members have visibility into progress without switching tools.
* **Audit Commentary**: Add explanatory notes to completed or locked records during audits or reviews, since the widget accepts comments regardless of record lock state.
## Configuration
The Comments widget requires no configuration. It is ready to use immediately after being added to a record — no setup or adjustment is needed.
{% hint style="info" %}
Because the widget has no configuration, the same comment thread interface is available on every record in the table automatically.
{% endhint %}
## Interface
### Read-only View
The widget displays a chronological list of comments. Each entry shows the commenter's name, the timestamp, and the full comment content. Action buttons at the top of the widget allow users to add a new comment or import emails from Gmail or Outlook.
The Comments widget displays a threaded comment list with author names, timestamps, and import/add controls
## Additional Functions
### Add Comment
{% stepper %}
{% step %}
Click the **Add Comment** button at the top of the widget.
{% endstep %}
{% step %}
A modal opens with the current user's name and timestamp pre-filled. Type your comment in the text field.
{% endstep %}
{% step %}
Click **Submit** to save the comment. It appears immediately in the comment list.
{% endstep %}
{% endstepper %}
### Import Emails from Gmail or Outlook
Many record-related conversations happen over email. The widget supports direct email import from both Gmail and Outlook so you can bring those conversations into the record without manual copy-pasting.
{% stepper %}
{% step %}
Authorize the widget to access your Gmail or Outlook account if prompted.
{% endstep %}
{% step %}
Click the **Gmail** or **Outlook** import button. A modal opens displaying the 10 most recent emails from the connected account.
{% endstep %}
{% step %}
Optionally enter search keywords in the search bar to filter the email list.
{% endstep %}
{% step %}
Choose how to insert the email:
* **Insert** — Adds the full HTML version of the email as a comment.
* **Insert Text** — Adds the plain-text version of the email as a comment.
* **Insert Summary** — Uses AI to generate a bullet-point summary of the email and inserts it as a comment.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**Import from Gmail**: Requires a Google Workspace or personal Gmail account. Once authorized, you can import emails from your Gmail inbox directly into the record.
**Import from Outlook**: Requires a Microsoft Outlook account. Once authorized, you can import emails from your Outlook inbox into the record.
{% endhint %}
### Edit Comment
Click the **Edit** button next to any existing comment to modify its content. The author and timestamp are preserved.
### Delete Comment
Click the **Delete** button next to a comment to permanently remove it from the record.
{% hint style="warning" %}
Comment deletion is permanent. There is no undo — confirm before deleting important communications.
{% endhint %}
## Best Practices
### Communication Organization
* Use comments to log the outcome of verbal or phone discussions so that all communication about a record is captured in one place.
* When importing emails, prefer **Insert Summary** for lengthy threads to keep the comment list concise and readable.
* Include the email subject or ticket number in manually typed comments so team members can find the original message if needed.
### Collaboration
* Mention context in each comment (e.g., the decision made, the question asked) rather than just forwarding raw email text, so comments remain meaningful to future readers.
* Add a comment when locking a record to explain the lock reason — since the widget remains open on locked records, this is an effective handoff mechanism.
### Compliance Awareness
* Do not use comment entries as evidence for regulated workflows (GLP, FDA 21 CFR Part 11). Use dedicated regulatory section widgets for compliance-critical documentation.
* Treat comments as supplemental context, not primary data.
### Common Pitfalls to Avoid
* **Avoid** deleting comments that contain decision rationale — edit them instead if a correction is needed.
* **Avoid** importing entire long email threads as HTML if only one reply is relevant — use **Insert Text** or **Insert Summary** to keep the record clean.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.labii.com/widgets/section-widgets/productivity/communication/comments.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.