Posts & Interactions

Posts are the primary way activity appears in MustardHub. A post represents a moment of communication or recognition that becomes visible to others based on where and how it was shared.

Most posts fall into one of these categories:

General messages or updates
Recognitions (with or without points)
Announcements sent on behalf of the company
Automated system-generated posts (covered in other articles)

Posts are not tasks, tickets, or performance records. They are conversational and contextual, and they exist to reflect everyday moments rather than enforce structured workflows.

Creating posts

Users can compose a post from the recognition box at the top of the feed. When selected, this box expands into a full message composer.

[Insert screenshot: recognition box collapsed and expanded]

Posting behavior depends on where the user is in the product:

If the user is viewing the Discovery feed, they will be prompted to choose which Hub the post should appear in.
If the user is already inside a specific Hub, the post will be created in that Hub by default.

[Insert screenshot: hub selection dropdown when posting from Discovery]

This behavior helps ensure posts are intentionally placed without requiring users to understand Hub structure in advance.

For more on how Hubs affect visibility, see C.3: Hubs & Hub Settings (Overview).

Posting as a Member vs an Admin

Most posts are created by individuals and appear as coming from that person.

Admins with the appropriate permission may also post on behalf of the company. When a post is sent on behalf of the company:

The post header reflects the company as the primary sender
The Admin is personally attributed as the secondary author

When posting on behalf of the company, there is also an option to send the post privately rather than publicly inside a Hub.

Private company posts:

Appear only in the recipient’s Discovery feed
Do not appear in any Hub
Are not visible to other Members
May be scheduled for delivery at a future date, either as a one-time post or on a recurring basis

When scheduled, these posts follow the same visibility rules at the time they are delivered.

[Insert screenshot: post composer with “post on behalf of company” and privacy option]

Permissions for posting on behalf of the company are covered in C.5: Members, Roles & Permissions.

Recognitions and points in posts

Some posts include recognition and points. These posts look similar to standard posts but carry additional context.

At a high level:

Points can be added inline during post creation
The post itself becomes the visible record of that recognition
Points awarded are tied to the post and its recipients

Posts may include:

A single recipient
Multiple recipients
No points at all

The presence or absence of points does not change how the post behaves in the feed. It only affects whether value is transferred.

For rules, limits, and configuration for peer-to-peer points, see B.6: Peer-to-Peer Giving.

To learn more about how points are recorded and tracked, see D.5: Wallets, Transfers & History.

Writing posts and inline interactions

MustardHub is designed to support peer recognition as part of everyday communication. Posts support free-text content with inline elements that make it easy to direct messages toward specific people or values.

Users may:

Mention other Members
Tag values
Boost by adding points
Attach images or GIFs

These elements are added inline using symbols that trigger dropdown menus. Optionally, they can also be selected from icons at the top of the recognition box.

[Insert screenshot: composer showing @mentions, #values, and +points dropdowns]

These features are meant to reduce friction and keep posting conversational, not to enforce structure or formatting standards.

How posts appear in the feed

Every post in the feed includes a consistent header and action area.

The post header shows:

Who sent the post (a person or the company)
Which Hub the post belongs to
When the post was created
A three-dot menu for managing the post (where applicable)

Below the post content are action options for:

Reactions
Comments
Boosts

All reactions, comments, and Boosts appear directly beneath the post.

[Insert screenshot: post header, actions, and interaction area]

Reactions, comments, and Boosts

Reactions

Reactions allow Members to acknowledge a post using a predefined set of emojis. Reactions are lightweight signals and do not affect visibility, permissions, or points.

Comments

Comments allow Members to respond directly to a post. Comments appear below the post in chronological order, with the most recent comment shown at the top.

Boosts

Boosting allows eligible users to reinforce a recognition by sending additional Giving Points to the original recipient.

Conceptually:

A Boost adds value to an existing recognition
Points are sent from the Booster’s Giving Wallet
Points are distributed to the recipient(s) of the original post

If the original post mentions multiple recipients, a Boost applies to all of them.

For detailed rules and limits for Boosting, see B.6: Peer-to-Peer Giving.

Pinned posts

Posts can be pinned for quick reference.

Pinned posts:

Remain associated with the Hub they were originally posted in
Appear under a Pins tab within that Hub
Do not change visibility or permissions

[Insert screenshot: Posts and Pins tabs within a Hub]

Pinned posts are typically used to keep important context visible without re-posting or amplifying activity.

Private transfers

Some point transfers occur privately rather than through public posts.

At a high level:

Private transfers do not appear in Hubs
They are visible only to the sender and recipient
They still create a financial record

For private transfer mechanics and history, see D.5: Wallets, Transfers & History.

Visibility and participation behavior

Not all Hubs behave the same, and not all teams interact at the same pace.

It is normal for:

Some Hubs to be quiet for long periods
Activity to cluster around certain roles or moments
Posting frequency to rise and fall over time

Visibility is shaped primarily by:

Hub structure
Where posts are created
Whether a post is public or private

Low visible activity does not necessarily indicate disengagement, and high activity does not automatically indicate alignment or performance.

Common misconceptions

“Low posting means low engagement.”

Not necessarily. Some teams communicate elsewhere or engage asynchronously.

“Boosts are endorsements.”

Boosts add points, not judgment. They are reinforcement, not evaluation.
“Pinned posts are announcements.”

Pinned posts are references. They provide a simple way to save and revisit posts easily.