Comments

Allow users to comment directly in your app.

The Comment Collection is a special type of Collection Component that allows users to comment directly in your app. Users can add new comments and see previous comments.

For the comment feature to work properly, your app should have a sign-in method enabled and the user must be signed in with their email address.

Setting up Comment Collections

  1. In Layout Editor of your app, hit the plus (+) symbol to add a new component.

  2. Select the Comments component.

  3. Choose the Data Source where you want your comments to be stored.

  4. If you’d like, give the component a new Title.

  5. Finally, pick the column in the data source where new messages should be stored under Save Comment.

Configuring Comment Collections

Comment collections are specifically designed for comment threads with the following Display fields:

  • Comment: The user’s comment.

  • Timestamp: The date and time the comment was made.

  • User photo: The photo of the user who made the comment.

  • User name: The name of the user who made the comment.

After mapping the fields you want to display with columns in the data source, populate Additional Columns for each new message. This will store the values that you want to display in the data source.

  • Timestamp: The date and time when the comment as made.

  • User name: The name of the signed-in user who made the comment.

  • User photo: The photo of the signed-in user who made the comment.

  • {A Unique Identifier}: In our example, this was the candidate’s name. We recommend storing at least one unique value for the thread in which you want this comment to appear. This will allow you to set up a Relation or Filter to segment your comments.

In addition to the standard options available with collections, the comment collection also comes with an Empty screen option. This is the message that will be displayed when there are no previous comments to show.

Adding Actions to your Comment Collections

The Comment Collection supports two types of actions:

After Submit Action: Triggers every time a new comment is added. This is often used to send a notification through one of Glide’s Integrations.

After Submit Action

Collection Item Actions: These can be triggered on each comment in the collection. This is often used to allow users to edit or delete a comment.

Collection item Actions

Comment Collections Case Study

Darren is a freelancer helping businesses get the most out of Glide. When he meets with his clients, they establish a few tasks to work on. Each task is tracked to completion in a Kanban Collection.

Darren's Kanban Collection

When Darren has questions, he will shoot his clients a quick email, expecting a reply. But lately a few of his clients have mentioned losing his emails in their inbox. And to make matters worse, Darren’s having trouble keeping up with all the email threads as he brings on more clients.

To help Darren and his clients get organized, we can use the Comment Collection to allow them to message back and forth on the tasks they are already tracking.

First, let’s create a new comments table with these fields:

  • Task

  • Comment

  • Timestamp

  • User Photo

  • User Name

Next, let’s add a new Comment Collection to the task screen and map each of the fields we just created.

Finally, let’s add a filter to only show comments with this task as the topic and sort by the Timestamp.

Amazing! Now Darren and his clients have a centralized single source of truth to discuss each of the tasks when they are working asynchronously.

Frequently Asked Questions

Have a question about Comments? Ask the Glide community.

Updated more than a week ago
Was this article helpful?