Creating a Post

The administrator has granted permission to view Conversations.
The administrator has granted you the required Conversations permissions to read and create posts.
You have access to supported records (contract, contract request, supplier, supplier request, and accounts).
At least one valid participant exists.

A Post is the starting point of a conversation and represents the first message in a unique conversation. Posts can be initiated at any stage and status of the supported record's lifecycle.

Each post:

is linked to the record it was created from and is accessible only within that record'sConversations page.
Creates a dedicated conversation to track all related messages and attachments.
Is visible and accessible from the Conversations page of the record.

Participants may include internal users, user groups, customer contacts, supplier contacts, and external users such as administrator contacts, or ad hoc email

External Participant Badge

When you add participants to a post, the application visually distinguishes external participants from internal users in the participant list and in the message content area:

Internal users (users within your organization) are displayed with their name only.
External participants (contacts, supplier contacts, and ad hoc external email addresses) display an External badge next to their name.

The External badge helps you identify at a glance which participants are outside your organization before you send the post, so you can review the recipient list and confirm that sensitive content is appropriate to share externally.

@Mentions

Note: The External badge is visible in the Create Post dialog and in the conversation thread view. It is not displayed in outbound email notifications.

Typing @ in the post message content editor opens a mention dropdown. Search requires a minimum of 2 characters after @. You can @mention internal users, user groups, contacts, and supplier contacts.

If a user group is mentioned, it is expanded into individual users after the post is created. The group itself is not shown as a tagged group in the details view (it appears as individual users).
Your @mention text is highlighted with a distinct background style in the message content area within the application.
Note: @Mention highlights are visible in the application only. When a post or reply containing an @mention is delivered to participants by email, the mentioned participant's name appears as plain text in the email body without any visual emphasis. This is by design—the application uses a different rendering approach for email notifications than for the in-application conversation view. To see @mention highlights, participants should open the conversation directly in the application using the link provided in the email.

(Optional) You can upload maximum 10 documents upto 21MB in total along with the post. The supported formats are .pdf, doc, docx, .rtf, txt, xls, .xlsx, .png, .jpg.

Open a supported record (for example, a Contract, Contract Request, Supplier Request, Account, or Supplier).
Click Manage Conversations to open the Conversations page for the selected record.
Click Create Post.
In the Create Post dialog, fill in the required fields.
1. (Required) Subject: Enter a subject for the post.
2. (Required) Participants: Search and select participants, by first name or email (results appear after entering at least two characters.)
  
  Note: You can add up to 50 participants.
3. (Required) Message Content: Enter the message using the rich text editor, which provides formatting options like text styling (bold, italics, underline), lists, links, and alignment to help format your reply.
4. (Optional) Add Attachment (s): Attach documents if required and review or remove them before posting.
Click Post to send the message.

Upon successful posting, a unique conversation is created and linked to the record. The post message and attachments are saved and tracked within the conversation and displayed in the record's Conversations page (list view).

All participants receive a single email notification containing the post content and attachments. They can view and download attachments. All participants receive a direct link to the record and a direct link to the conversation in the email. These links are accessible only to users who have access to the application and the associated object or record; users without the required access cannot open the links.

Note: Email links always open the all-records view (for example, All Contracts, All Requests) for the associated object type. Filtered views such as My Requests or Recently Viewed are not used as link targets, because the same link must be accessible to all participants, including those who may not have records in their personal view.

Participants can respond either by replying to the email (all participants) or by replying within the application (internal participants only).

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Creating a Post

Footer Section

Explore