> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/end-users/participating-in-posts.md).

# Participating in Posts

Follow, respond to, and manage documentation-related discussions, questions, and incidents.

## Overview

**Posts** is your personal hub for staying informed and engaged in documentation-related conversations. Whether you're tracking a discussion, following up on a question, or checking the status of an incident, this is where everything comes together.

***

## What are Posts?

**Posts** are comment threads related to documentation items. A post can be one of the following:

* A **discussion** (e.g., clarification or suggestion)
* A **question** (e.g., about accuracy or usage)
* An **incident** (e.g., reported issues or errors)

***

## Using the Posts Workspace

### Interactive Tour

Learn how to access and explore your Posts.

{% @howdygo/embed url="<https://app.howdygo.com/share/71f36804-42a7-4459-ad6f-8af761c3f504>" fullWidth="true" %}

{% stepper %}
{% step %}

### Accessing Posts

Select the **Posts** tile in the side navigation bar. The module opens in the main workspace, displaying an organized list of posts.

***

{% endstep %}

{% step %}

### Browsing Posts

On the left, you'll see the list of posts, one for each thread you're involved in.

Posts appear here if you:

* Created the post
* Replied to the post
* Are assigned to the related documentation item through **RASCI-VS**
* Subscribed to the documentation item

{% hint style="info" %}
**Unread posts** are indicated by a colored bar and bold text. Once opened, they are automatically marked as **read**.
{% endhint %}

***

{% endstep %}

{% step %}

### Opening Posts

Select a post from the list to view its contents. You’ll see:

* **Comments and replies** in the center
* **Related documentation** on the right

***

{% endstep %}

{% step %}

### Replying to Posts

* At the bottom of the comments panel, click **Reply to this discussion**.
* Enter your message, then click the **arrow** icon to **send** it.

Everyone involved in the post will be notified.

***

{% endstep %}
{% endstepper %}

***

## Creating Posts on Documentation

You can create a post directly from a documentation item to ask a question, start a discussion, report an issue, or suggest a change.

### Interactive Tour

Learn how to access and explore your Posts.

{% @howdygo/embed url="<https://app.howdygo.com/share/130c4896-6cb1-4cb7-8ebf-3568d85d0f73>" fullWidth="true" %}

{% stepper %}
{% step %}

### Opening the Posts Panel

* In the **Library**, open the documentation item's [**Details** panel](/interfacing-help-files/end-users/library.md).
* Click the **Posts** ( <i class="fa-messages">:messages:</i> ) icon.
* The **Posts** panel opens, displaying any existing posts for the item.

***

{% endstep %}

{% step %}

### Adding a New Post

Click the <i class="fa-plus">:plus:</i> to start a new post.

***

{% endstep %}

{% step %}

### Completing the Form

You'll be asked to provide the following:

* **Comment**\
  Enter your message.
* **Post Type**\
  Choose from Discussion, Question, or Incident.

***

{% endstep %}

{% step %}

### Publishing a Post

Click **Add Comment** to publish your post.

After publishing, you and anyone involved can:

* View the post and replies in the **Posts** panel or module
* Reply to the thread
* Receive notifications when others respond

***

{% endstep %}

{% step %}

### Editing & Deleting a Post

Update or remove your posts as needed:

* Click on the **More Options** (<i class="fa-ellipsis-vertical">:ellipsis-vertical:</i>) icon.
* In the menu, select either **Edit** or **Delete**.
  * **Edit:** The Post form opens, allowing you to update your message or change the post type.
  * **Delete:** The post is immediately removed from the panel.
    {% endstep %}
    {% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><p><strong>Raising a Change Request</strong></p><p><br>Learn how to request formal changes to documentation.</p></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FrHuKwH5xcs33XXemh6QC%2FIMS-V16-NAV-Library-Icons-114.png?alt=media&amp;token=bd1f7bed-13bc-4eac-b145-eaac7da57532">IMS-V16-NAV-Library-Icons-114.png</a></td><td><a href="/interfacing-help-files/end-users/raising-change-requests.md">Raising Change Requests</a></td></tr></tbody></table>

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/end-users/participating-in-posts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.