Posts
Workflows

System posts vs user posts

Identify and filter system, bulk or user posts in the Activity Feed to organise activity.

June 26, 2026
ID:
311

The Activity Feed mixes two kinds of entry: user posts that people write, and system posts that SwiftFox generates automatically. Understanding the difference helps you read the feed and filter it effectively.

User posts

User posts are created manually through the post composer at the top of the Activity Feed. They are the Posts people write by hand and can include:

  • Text, @mentions, attachments, addresses, and tags.
  • A custom date/time and an audience set via Edit permissions (Everyone, Current Circle, Only me, or named users, user groups, or circles).

User posts can be reacted to, commented on, turned into Tasks, edited, and deleted (subject to permissions).

System posts

System posts are generated automatically when actions happen elsewhere in SwiftFox. They give the feed a live record of activity without anyone writing it. Examples include:

  • Member portal updates — when a portal record changes.
  • Form submissions — when a form is submitted.
  • Email sends — when emails go out.
  • Other module activity that surfaces into the feed.

System posts act as an audit trail of what's happening across the account, surfaced in one stream.

Bulk posts

A subset of system activity is bulk posts — Posts generated by bulk actions such as large email blasts. Because a single bulk action can create a lot of entries, these are filtered separately from other system posts.

Telling them apart and managing them

  • Both types appear in the same feed, in chronological order.
  • In the feed's Settings panel (the 3-dot menu, top-right), set the View type to Hide system posts to see only human-written Posts.
  • Set the View type to Hide bulk posts to remove the noise from large sends while keeping other Posts.
  • The view type is single-select, so you choose one at a time. See Filtering the Activity Feed.

When to use each

  • Read user posts for notes, context, and conversation logged by your team.
  • Read system posts to track what the platform and your Contacts have done (portal updates, form submissions, emails) without leaving the feed.