How to Collaborate Using Workspace Conversations in Mydrop

By the end of this tutorial you will have created a message thread in a workspace channel or on a post that includes at least one message, replies in a thread, an attached file visible on a message, an @mention delivered in the thread, and visible reactions or an edited label.

Before you start

Checklist

1. Confirm the correct workspace is selected.

   • Open the workspace switcher or header and verify the workspace name shown matches the brand or client you intend to work in.
   • Working in the wrong workspace causes messages and invites to go to the wrong team.

2. Verify conversation permissions.

   • Open Conversations from the main navigation. If you can see channel lists, Create/Invite controls (for example New channel or Invite members), or compose controls, you have posting and invite permissions.
   • If you cannot post or invite, ask a workspace admin to grant Conversation or member permissions before proceeding.

3. Choose where to discuss the item.

   • Decide whether to use a workspace channel (for broader team discussion) or the Conversation panel inside a specific post (to keep feedback next to that post preview).
   • Using the post Conversation panel keeps comments and the post preview together for review and approvals.

4. Gather files you want to attach.

   • Collect images, documents, or other assets you will attach to messages.
   • Keep files within your team’s size and format limits. If attachment fails, try a smaller or supported format.

5. Prepare teammate handles to mention.

   • Note the exact @handles or display names of teammates to mention.
   • Mentions send focused notifications and are faster than posting general requests.

6. Know the post or channel topic.

   • Confirm the correct channel topic or the correct post preview is open before posting so decisions and assets stay in the intended conversation.
   • If the topic is wrong, switch channels or open the correct post Conversation panel first.

Quick verification before you start

• Open main navigation and click Conversations to confirm channels load and you can see a compose area or channel list.
• Open a post you plan to discuss and confirm the Conversation panel is available on the post.
• Check that you can see common UI labels such as Send, reply, or Invite members. These indicate the features used in this tutorial are visible.

Notes that avoid wasted work

• If you lack permission to create channels or invite members, posting in an existing channel or inside the post Conversation panel is usually allowed; confirm with your admin.
• If a file upload likely exceeds limits, compress or resize images before attaching.
• Use exact teammate handles when mentioning to ensure the right person gets notified.

After this checklist you will be ready to open Conversations or the post Conversation panel, create or pick the right channel, write messages with attachments and mentions, and follow the next steps to start and verify a threaded discussion with reactions and edits.

You will open Workspace Conversations and pick the channel or post thread where your team will collaborate so you can post messages, attach files, and mention teammates.

Step 1: Open the feature

1. From the main navigation, click Conversations.

   • What to click: the Conversations item in the left or top main navigation.
   • What you should see: a list of workspace channels, recent threads, or a prompt to create a channel.

2. Alternatively, open the post you want to discuss, then open the Conversation panel on the post.

   • What to click: open the post preview, then choose Conversation or the conversation tab/panel attached to that post.
   • What you should see: the post preview and the conversation area alongside or under the post.

3. Pick where to post: choose an existing channel from the channel list or select the post thread.

   • What to choose: a channel name from the list if the discussion is workspace-wide, or the post thread if the conversation should live on that specific post.
   • What you should see: either the channel message list or the post thread messages. If the area has no prior messages, you may see a short prompt indicating there are no messages yet.

4. If the channel list is long, use the search or scroll to find the intended channel.

   • What to choose: the exact channel for the content or the post thread that matches the review or approval task.
   • Result to expect: the selected channel opens and shows its header, member count or small member icons, and the message composer at the bottom.

5. Confirm the workspace shown at the top of the screen matches the workspace you intended to work in.

   • Why this matters: posting in the wrong workspace sends context and files to the wrong team.
   • What to check: workspace name in the header or workspace switcher control.

Step 2: Set up the basics

1. If you need a new channel, create one before sending messages.

   • What to click: the New channel button or New channel action in the Conversations area.
   • What to choose: a clear channel name that matches the topic (for example, the campaign or post name).
   • What you should see: the new channel appears in the channel list and opens immediately.

2. Invite the right members to the channel.

   • What to click: Invite members or Add members in the channel header or channel settings.
   • What to choose: teammates by name or handle. Use @name when you post to ensure they are notified.
   • What you should see: invited members listed in the channel header or a confirmation that invites were sent.

3. Confirm channel permissions and membership before posting.

   • What to check: that you and the teammates you need are listed as channel members and that you have permission to post and reply.
   • Result to expect: composer box active and Send available; if you lack permission, Send or Reply will be disabled or you will see a message about membership or permission.

4. Verify the channel topic or purpose is correct.

   • Quick checklist:
     • Channel name matches the task or campaign.
     • Channel description or topic, if shown, reflects the discussion goal.
     • Members invited or present are the reviewers, approvers, or creators needed.

5. If you created a single-user or private channel by mistake, switch to the intended public or team channel.

   • What to do: use the channel list to select the correct channel or use the channel settings to change membership.
   • What you should see: the correct channel with the expected member list and message area.

6. Confirm the message composer is ready and you can attach files.

   • What to check: the text field is active, the send control (Send icon or button) is visible, and an attach or paperclip control is available.
   • What you should see after attaching a file: the attachment upload indicator completes and the file appears on the draft message.

7. Final check before posting: ensure workspace, channel, invited members, and composer readiness are correct.

   • Why this matters: prevents posting to the wrong channel or losing collaborator context.
   • Result to expect: the workspace and channel header show the right names, composer is active, and invited members are visible.

If all checks look correct, the workspace and channel are ready for the next steps: composing the first message, attaching assets, mentioning teammates, and starting threaded replies.

Step 3: Add the content or settings

Outcome: you will post a message, mention teammates, attach at least one file, and start a reply thread.

1. Open the composer.

   • Click the message box at the bottom of the Conversations channel or open the Conversation panel on the post and find the composer.
   • Confirm the composer shows a placeholder or cursor so you can type.

2. Write your message.

   • Type the text you want the team to see.
   • Use @ followed by the teammate handle to mention someone.
   • Select the correct person from the suggestion list to ensure the mention resolves to @name.

3. Add attachments.

   • Attach files by dragging them into the composer or using the attach button in the composer (paperclip or Add file).
   • Wait for the upload indicator to finish before sending. A progress or loading indicator should complete and the file name or thumbnail should appear in the composer.

4. Send the message.

   • Click Send or press Enter (the composer shows a Send icon).
   • After sending, check the message appears in the channel or post thread with your text, the attachment thumbnail or filename, and the timestamp.

5. Start a thread from a message.

   • Locate a published message and click Reply (the reply icon appears on messages).
   • Type the thread reply in the reply box that opens beneath the original message.
   • Send the reply to nest it under the parent message rather than posting at channel top level.

6. React, edit, or delete messages when needed.

   • Add a reaction (for example thumbs up) by clicking the reaction control on the message; the reaction count should update.
   • Edit your message by choosing Edit on your message, make changes, and save. An edited label appears next to the message after saving.
   • If necessary, delete your message using the delete or trash option.

Quick checklist before sending

• Workspace and channel are correct.
• You have permission to post and invite members.
• Files are supported type and within size limits.
• Teammate handle selected from suggestions after typing @.

Step 4: Review the workflow

Outcome: confirm the thread structure, attachments, mention delivery, and visible reactions or edit labels.

1. Verify the main message and attachment.

   • Confirm the original message is visible in the channel or on the post.
   • Confirm attached files show a thumbnail or filename on the message and open when clicked.
   • If the attachment shows an error or file unavailable message, re-upload a supported file or check file size.

2. Verify mention delivery.

   • Open the thread and look for the @name you added.
   • Confirm the teammate name is highlighted or shown exactly as selected from the suggestion list.
   • Optionally, ask the teammate to confirm they received the mention or check the notification badge in Mydrop.

3. Verify replies are threaded correctly.

   • Open the thread from the original message and confirm replies appear nested below it.
   • Confirm each reply shows the reply icon or is indented so the conversation is grouped.

4. Verify reactions and edits.

   • Add a reaction yourself and confirm the reaction count increments.
   • Edit a message and confirm the edited label appears next to the timestamp.
   • If the edited label does not appear, refresh the conversation view or reopen the post Conversation panel.

5. Confirm post preview alignment (when discussing a post).

   • Open the post preview or Conversation panel inside the post.
   • Confirm the discussion references the same post content or preview you are reviewing.
   • Ensure any attachment intended for the post is visible and matches the asset being discussed.

Troubleshooting checks

• If messages do not send: confirm workspace selection and posting permissions.
• If uploads fail: check file type and size; retry using a supported format.
• If mentions do not resolve: re-type @ and pick the teammate from the suggestion list to avoid misspelling.
• If threads appear in the channel instead of nested: use the Reply control on the specific message to nest replies.

Next steps after review

• Continue review in the same thread until approvals are complete.
• Attach final assets discussed in the thread, then move to scheduling or gallery workflows as needed.

Troubleshooting and next steps

Outcome: you should end with a visible message thread that includes at least one message, replies nested in a thread, an attached file shown on a message, an @mention delivered in the thread, and visible reactions or an edited label.

Quick checklist

• Confirm correct workspace is selected.
• Confirm you have permission to post or invite members.
• Have the file ready and confirm it is a supported type and under size limits.
• Know the exact teammate handle to mention (use @name).

Common problems and fixes

1. Message does not send or is missing

   1. Check the workspace shown in the workspace switcher. If it is wrong, switch to the intended workspace and try again.
   2. Make sure you are in the correct channel or the post Conversation panel. If not, open Conversations from main navigation or open the post and open its Conversation panel.
   3. If you lack permission to post, request posting or commenting rights from a workspace admin, then retry.
   4. Refresh the Conversations view and look for the message at the top or in the channel timeline.

2. Attachment upload fails or is not visible

   1. Verify the file type and size. Replace or export the file in a supported format and reduce the size if necessary.
   2. Reattach the file using the message composer attachment control and wait for the upload indicator to finish before sending.
   3. If upload stalls, refresh the channel or reopen the post and try again.
   4. If file still fails, try attaching a different file to confirm whether the problem is specific to that asset.

3. Mentions do not reach teammates

   1. Confirm the handle is exact. Type @ and the first letters of the teammate name, then select the matching suggestion.
   2. Check that the teammate is a member of the channel or invited to the post conversation.
   3. If the teammate does not receive a notification, ask them to check their notification settings or mention them again after confirming membership.

4. Replies or threads appear out of order

   1. Use the reply button on the specific message to start a thread; replies should nest under that message.
   2. If replies appear in the main timeline instead of the thread, move the reply into the thread by replying again using the message reply control.
   3. Refresh the view to ensure the client shows the latest thread order.

5. Reactions or edits are not visible

   1. After reacting, confirm the reaction icon and count appear on the message.
   2. After editing, check for the edited label next to the message timestamp.
   3. If these do not show, refresh the conversation and confirm you are viewing the channel or post thread where the action happened.

Verification checks to confirm setup worked

1. The original message appears in the channel or post conversation with a timestamp.
2. An attached file thumbnail or filename is visible on the message.
3. A reply is nested under the original message in a thread.
4. An @mention appears highlighted in the reply and the teammate is present in the channel or invited to the post.
5. A reaction count increments when someone reacts, and an edited label appears after a message edit.

Next steps after fixing issues

1. Continue the review inside the post preview to confirm discussion aligns with the post content.
2. Attach finalized assets you validated in the conversation.
3. When ready to publish, open Calendar to schedule the post or use Gallery imports for final design files.
4. If the work should follow a repeatable flow, consider creating an Automation that includes notifications or approvals.

Conclusion

This troubleshooting guide helps confirm that a conversation thread contains messages, replies, attachments, mentions, and visible reactions or edit labels. If issues persist, verify workspace and permissions, retry the action, and involve a workspace admin for permission or membership fixes. Once resolved, continue reviewing in the post preview and proceed to scheduling or asset finalization.