Use a post's Preview settings to choose whether people can comment where the platform supports it. For example, an announcement that directs people to a support desk may need different comment settings from a question inviting discussion.
Choose the setting for each destination before publishing. A setting for Instagram does not change the Facebook copy of the same post.
Platform support
| Destination | Post-level choice | What to expect |
|---|---|---|
| Instagram Feed and Reels | Allow comments on this post | Turn it off to disable comments after the post is created. Postly checks Instagram's reported state. Story replies use Instagram's own settings. |
| Allow comments on this post | Turn it off for a new post. LinkedIn accepts a separate request to close comments after publishing. Closing comments also deletes any comments already added; it is not available here for reshares or provider drafts. | |
| TikTok | Disable comments | The publishing request includes this choice. TikTok's creator and privacy restrictions still apply. |
| Bluesky | Allow replies on this post | Turn it off to prevent replies. A separate reply-permission record is created after the post. |
| WordPress | Site default, Allow comments, or Turn off comments | Applies to the individual article on WordPress.com or a connected self-hosted site. Choose Site default to keep the site's normal behavior. |
| Hashnode | Disable comments | Applies the article's comment choice through Hashnode's publishing API. |
| Facebook and Pinterest | No supported disable-all switch in Postly's publishing integration | Manage available comment permissions directly on the platform. Postly does not promise that a publishing preset can disable all comments there. |
X and Threads offer reply restrictions, such as allowing replies from mentioned accounts. A restricted audience is different from disabling all replies. Do not rely on those choices to close a discussion completely.
Change one publication
- Select the intended channels in the editor.
- Open the destination's settings in Preview.
- Choose its comment or reply permission.
- Remove follow-up comments or thread replies when comments are disabled.
- Publish or schedule the post, then review the result and live link.
For Instagram, LinkedIn and Bluesky, publishing and applying the comment setting are separate platform operations. Someone may be able to comment briefly between those operations. If a post requires comments to be closed before it is ever visible, check the platform's native publishing options rather than assuming this workflow guarantees that timing.
Save defaults with Publishing presets
Open Workspace Settings → Publishing presets to save the supported choices you use most often. Select a preset in Preview, then adjust the settings for the individual destination when needed.
An explicit per-post choice takes precedence over a default. Editing a saved preset does not retroactively change a live post. Review older drafts individually before publishing them.
For CSV and Google Sheets, use instagram_allow_comments, linkedin_allow_comments, or bluesky_allow_replies with yes or no. Use wordpress_comment_status with inherit, open, or closed. Blank optional fields can inherit a selected publishing preset. The API and MCP schemas describe the corresponding settings: allow_comments, allow_replies, and comment_status.
If the post is live but its setting failed
A Post published: review comment settings alert means the content was accepted, but its requested setting was not accepted or confirmed. Open the existing post on the platform and inspect its permissions. Do not publish the content again to fix a comment setting: that can create a duplicate.
Reconnect the account if a permission is missing, and review the specific platform result. A successful publishing receipt confirms the content was created; it does not turn a failed settings request into a success.