Create Posts and Manage Visibility
How posts work, what the main fields mean, and how replies, mentions, audience tags, and sharing affect the buyer or viewer experience.
What a post can be
A post in GetPaidX can represent several different user-facing jobs:
- a normal update,
- a planned event or check-in,
- a reply to another post,
- a paid offer,
- a workspace-backed or artifact-backed deliverable.
The same post page can carry both explanation and functionality, so it is important to think about the post as the container for the whole offer, not just as a text update.
Core post fields
The common post fields are:
| Setting | What it means to the user |
|---|---|
| Title | The main promise or label for the post |
| Body | The explanation, scope, or invitation text |
| Place | Connects the post to a venue or local context |
| Scheduled time | Signals when the event or availability matters |
| Audience tags | Limits who is intended to see or access the post |
The end-user meaning matters more than the storage details. For example, scheduling tells visitors whether your post is current, upcoming, or already in the past.
Audience and visibility
Audience tags are how you narrow who a post is meant for.
Use them when the post should be oriented to a subset of your members or collaborators instead of the whole public audience. Leaving them empty is the broadest and simplest option.
When you add audience restrictions, think of them as changing who the post is for, not merely hiding text.
Replies and mentions
Replies are separate posts that live in the thread of a parent post.
Mentions let you involve other people in a post, but the mentioned person may still need to approve visibility before it shows in the way they expect on their side. This means a mention is not always an instant public endorsement.
Sharing and reference links
Posts can also be shared through reference links such as /r/{referenceId}.
These links are useful when you want a stable, citation-style URL that is simpler to reference than an internal post ID.
Most common post workflows
This page is the right starting point when you want to:
- publish a general update or offer,
- create a venue-linked post or scheduled event,
- understand which core fields shape what viewers see,
- decide whether a post should stay broad or be narrowed by audience rules.
For pricing-specific behavior, continue into the pricing and purchase docs after you understand the basic post container first.
See it in action
Previous
Profile Workspace Title, Body, and Bio Fallbacks
How the app chooses a first title and body for a profile workspace when a user has partial or missing profile details, and how professional title, about text, bio, and email fallback rules affect that first draft.
Next
Audience Tags, Memberships, and Visibility
How audience tags work in the post UI, how they relate to followers and memberships, and what viewers should expect when a post is restricted.