Bring your community together
Use a community for conversations, announcements, questions and feedback around your work. It is separate from your private creator workspace. Members cannot open your projects, form answers, research or AI tools.
Create, review and publish#
In your creator workspace, open Community, then Create community. Choose a permanent link, write a short description and explain your rules. New communities are drafts. Save the details, create at least one group and review the joining policy before publishing.
Your link looks like app.campfold.io/creatorhub/community/your-name. A published community shows its title, description and rules to visitors. Discussions, member profiles and conversations require current approved access.
Choose Open joining to let verified accounts join after accepting the current rules, or choose approval to review each request. The published community card has Open community for the member experience and Manage for owner settings. Drafts have no public-opening shortcut. Directory listing is a separate choice. An unlisted community can still be reached through its link.
Join and find your way around#
Visitors can create a community account from your link, verify their email and sign in. They then choose Join or Request to join. Verification does not join a community automatically. Existing creators can use their usual account.
A community account provides community access only. It does not create a creator workspace, subscription or AI allowance. Joining is not newsletter consent.
Active members see:
- Home for an introduction and links to the available channels.
- Channels for discussions or announcements. Restricted channels need a separate approval.
- Members for profiles within this community.
- Messages for their own conversation requests and accepted private conversations.
- My profile for a community bio, profile accent and messaging preference.
The community team also sees the review or access tools permitted by its role. A pending or blocked member cannot open the feed, member directory or private conversations. Use Refresh to check new activity. This release does not provide real-time chat, online indicators or push notifications.
Choose the right team role#
Community roles do not grant WordPress administrator access or access to creator workspaces.
| Role | What it can do |
|---|---|
| Member | Read approved channels, participate where posting is allowed, report posts and use accepted private conversations. |
| Reviewer | Review and resolve reports in channels they can read. Cannot change membership, moderate posts, change settings or read other members' private conversations. |
| Moderator | Review ordinary member requests, mute or block ordinary members, review reports and moderate posts. Cannot change community roles or owner settings. |
| Owner | Manage community settings, publication, channels, roles, member access and the community banner. |
| Platform administrator | Manage the service and its platform notice. This does not grant an application route for opening other members' private conversations. |
Only the owner can appoint or remove reviewers and moderators. Role changes have an explicit confirmation. Moderators cannot promote themselves or change a peer moderator's access.
A muted member can read approved channels but cannot post. Private conversations also pause while either participant is muted. Leaving and rejoining does not clear a mute. Restricted-channel approvals are removed when a member leaves or is blocked.
Channels and announcements#
Create channels for questions, announcements or project feedback. A channel can be available to all active community members or require a separate approval. Choose moderator-only posting for an announcement channel. Members can read its updates without gaining permission to publish there.
Discussions use topics and replies. Owners and permitted moderators can pin topics, lock replies, hide posts and review reports. Reporting does not remove a message automatically. Hidden posts are removed from ordinary member views while permitted moderators retain access for review.
The owner can also open Announcement banner in community management. Save a short title and message, optionally add an HTTPS link and explicitly choose to show the banner. It appears above the channels for active members of that community. It does not appear in unrelated communities or creator workspaces. A platform notice is a separate administrator control.
Profiles and private conversations#
Each community profile has a display name, optional bio, accent and initials avatar. Profiles do not display email addresses or memberships in other communities. Keep sensitive information out of your bio.
Messaging starts off. In My profile, save your choice to allow conversation requests. Both people must have messaging enabled and current active access to the same community. Then use Request a conversation from a member's profile.
A request contains no message. The recipient can accept, decline or block it. Neither participant can send text until the request is accepted. Accepted conversations support plain-text messages and manual refresh. There are no attachments, group direct messages, voice calls or email notifications for messages.
Only participants can open a conversation through Campfold. Community staff cannot browse other members' private conversations. Messages are stored by the service and are not end-to-end encrypted. Never send passwords, payment details or sensitive personal information.
Declining or blocking removes the conversation from the active inbox and prevents another request between those accounts in the same community. This version cannot undo that decision. Turning messaging off, leaving, losing membership, being muted or withdrawing the community makes its conversation history unavailable while that access condition remains in effect. Earlier records are retained.
Share a form or poll#
The community owner can use Create form or poll above a channel to open the existing Forms builder. Create and publish the form there first.
Back in the community, choose Share a form, select one of your published public forms, choose a channel where you can post and add a short introduction. Saving creates a discussion with an Open form or Open poll button. The button opens the actual public form in a new tab. A poll is a form with one single-choice question. It does not enforce one vote per person or show public results.
Responses stay in the creator's private workspace. Sharing does not copy answers, voter identities or results into the discussion, and it does not invent a vote count. If the source form is withdrawn or no longer eligible, the active button disappears when the discussion is refreshed. Earlier message text may still contain its old URL.
Limits and retained data#
Free allows 1 non-archived community, 5 active channels per community and 100 active or pending members. An existing unpaid temporary capacity allocation allows 5 non-archived communities, 20 active channels per community and 500 active or pending members while active. Campfold launches completely free; these allocations are not subscriptions or payments.
A topic is limited to 4,000 UTF-8 bytes and a reply or private message to 2,000 bytes. A bio or banner message allows 500 bytes. Characters such as emoji can use more than one byte.
Private conversations have finite retained allowances: 100 conversation records per account, 500 per community and 500 messages per conversation. There is also a community-wide message allowance. Requests are limited to 5 per sender per day and 10 per recipient in a community per day; sending is limited to 100 messages per account per day. Shared service limits may pause activity sooner. These safeguards are not reset by leaving, withdrawing or archiving.
Leaving keeps earlier contributions. Withdrawing closes member access while retaining discussions. Archived communities remain closed in this version. For account or data help, email [email protected].
When a save is uncertain#
If the connection breaks after saving, use Check saved state first. The original text and submission identity are kept only in the current page. Reconcile the same action when prompted. Do not create a new message or request to guess whether the earlier action was saved.
If access changes, protected content and local drafts are cleared. An unconfirmed save is not a confirmed new post, message, member or delivery.