Communities

A community is a named group with its own feed, members, moderators, and (optionally) its own embed footprint. Communities live at zeeker.com/c/<slug>.

Joining

• Public communities let you read posts without joining. The Join button on the community header toggles to "Joined" after you join.
• Private communities show their overview to non-members, but posts and participation are available only to members.

Zeeker visibility is a separate choice. Connected to Zeeker communities can appear in Zeeker feeds, search, and discovery where access permits. Direct access only communities stay out of those surfaces; use a permitted direct link, their own domain, or an embed on an allowed website. Private posts remain members-only in either mode, and website or app sign-in requirements still apply.

Before joining, Zeeker shows a confirmation popover with the community's rules and a notice that the community may send occasional emails. Confirming joins the community and enables that community's emails by default. You can disable them anytime from Settings -> Notifications -> Community Emails.

Member view

Once you've joined, a community shows you:

• Feed — community posts with either Trending / Popular / Recent lanes or an automatic All lane followed by up to four admin-selected tag-filter lanes.
• About — description, rules, moderators, links.
• Members — searchable directory; counts visible to all members.
• Pinned — up to 5 posts the moderators have pinned.

Community discovery, feeds, member directories, and blocked-community lists load in bounded server-ordered pages. Load more uses the returned continuation, so large communities do not require downloading or sorting the complete member or post history in the browser.

You can post into the community from the composer's community picker; non-members cannot post into a public community without first joining (unless the community has Allow guest posts toggled on by admins). That setting still requires a signed-in identity; it is not unauthenticated Embed guest publishing.

Content capabilities and embeds

Community settings define the content and permission ceiling shared by zeeker.com and every Embed configuration. Owners/admins can choose the allowed existing post types, post and reply tags, default sort, whether the community header shows sort lanes or up to four post-tag filters, whether a post or reply accepts one or multiple descriptive tags, whether normal post pages show related posts, whether that related set may include eligible external/source posts, and whether community chat is enabled.

Tag-filter mode always starts on a text-only All lane, which displays every community post, followed by the configured tags in their selected order. Tag names are shown in full; when the row is wider than its available space, the lane strip scrolls horizontally instead of shortening labels with an ellipsis. All and the tag lanes support the same horizontal swipe navigation as the standard sort lanes. The member's Trending / Popular / Recent preference still orders posts within the selected lane and remains available from Preferences. A full community Embed uses the same lanes and scrolling treatment. Individual post pages do not add these community-feed filters, even though replies can carry configured reply tags.

Community admins do not author an Embed information block. For implementation types that need one, Embed applies an implementation-owned, bounded box programmatically when the preset is created. Support Forum currently uses this contract: the standard community card starts hidden, the preset-supplied support box sits immediately above Social's feed-filter header, and community-scoped search remains enabled. The box is capped at 300px, uses the same border treatment as the adjacent Embed surfaces, and keeps an opaque themed surface even when the fixed Embed canvas is transparent.

Embed Elements are presets that select and present a subset of these capabilities. They do not add new post types, headers, feeds, support workflows, ratings systems, or moderation behavior. An embed may hide information, narrow post types/external content, or remove actions, but it cannot widen the community settings.

Community SSO

When an admin enables SSO for a community, that community's SSO method is the primary option on the first Zeeker ID screen. The same community-scoped sign-in experience applies wherever someone enters or participates in the community:

• the community home and its custom domain;
• individual post pages and shared deep links;
• page discussions, community embeds, and widget surfaces;
• sign-in prompts opened by posting, replying, reacting, saving or bookmarking, and joining.

Zeeker keeps the community context when a gated action opens sign-in, including when the action starts from a specific post. The configured SSO button appears first; phone, email, and social sign-in methods remain available after selecting Other Options.

If SSO is disabled for the community, Zeeker ID shows the standard sign-in methods directly. SSO configuration and host-site integration are covered in Admin SSO and Embed SSO.

Roles

Role	Granted by	Powers
Member	Joining	Post, reply, react
Moderator	Admin / owner	Remove posts, mute/ban members, lock threads
Admin	Owner	All mod powers + edit settings, manage roles, configure embeds
Owner	Created the community	All admin powers + transfer ownership, delete community

Role changes appear in the Modlog with actor, target and timestamp.

When a staff member enables Admin view for a community, its About panel keeps a Mod Chat action visible. That action opens the selected community's moderator inbox; the ordinary Chat with Moderator action remains the member-facing way to contact staff.

Community and thread post menus use the same verified role. Owners, super admins, admins, and moderators can Pin to Top or Unpin, Accept, Reject, and Remove root posts, connected posts, and replies. Pinning a root post replaces the previous community pin; pinning a reply replaces the previous pin under that parent.

Rules

Every community has a rules list (up to 10 items, 120 chars each). Rules show on the right rail and in the report dialog. Moderators can cite a specific rule when removing content; the citation is shown to the reporter and the removed-author.

NSFW communities require a signed-in adult account with a verified profile birthday. After accepting the content warning, joining shows the community rules for confirmation and updates membership immediately when confirmed; the server rechecks age against the latest saved profile.

Reporting a community

Choose Report community below the community rules, select one or more reasons, and optionally add details. Anyone who can view the community can file a report without logging in or creating an account. The report goes to Zeeker's moderation system and is anonymous to the community.

Cross-posting

A post can be "cross-posted" into multiple communities by sharing it; the cross-post is a repost record scoped to the target community. The original counts continue to accumulate on the source post.

Discovery

• The Communities tab lists communities eligible for discovery under their access rules, sorted by recent activity. Direct access only communities stay out of global discovery even when you are a member; use their permitted direct entry instead.
• Search at zeeker.com/search?type=communities&q=... finds eligible communities by name, slug or description.
• The home feed surfaces communities you might like under "Communities to explore" once a week.

Older Unlisted communities keep their existing discovery restrictions until an administrator deliberately saves their access settings. Their publicly readable community page uses the Public access label.

Creating a community

Communities are created from the admin center — see Create a community. This puts new communities behind a deliberate setup flow with rules, branding, and (optionally) an embed config and SSO from the very first day.