Community settings

The Settings tab in the admin center is divided into sub-sections. Owners and admins can edit everything; moderators have read-only access.

General

• Name — display name, 3–50 chars.
• Tagline — one-line description shown on the community header.
• Description — long-form text, supports markdown, shown on the About tab. Up to 4,000 chars.
• Category — broad classification used for discovery.
• Primary language — used by content filters and trending algorithms.
• Links — up to 4 external URLs (your website, Discord, etc.) shown on the right rail.

Theme

• Accent color — applied across the community feed and (by default) the embed widget. Hex picker.
• Logo — square image, 256×256 minimum. Auto-cropped.
• Cover — 1500×500 banner shown at the top of the community page.
• Light / dark default — auto, light or dark. Members can still flip personally.
• Custom font (optional) — pick from Inter / IBM Plex / Noto, or paste a Google Fonts URL.

Theme changes propagate to:

• zeeker.com/c/<slug> instantly.
• Embed configs that haven't overridden the theme — within 60 s (boot cache TTL).

Rules

Up to 10 rules, each ≤ 120 chars. Shown on the right rail of the community page 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. We recommend keeping rules short and specific (e.g. "No personal attacks" rather than a paragraph of nuance).

Community access and Zeeker visibility

Community access controls who can read posts:

• Public — anyone can read posts without joining the community.
• Private — only community members can read posts.

Zeeker visibility is a separate choice:

• Connected to Zeeker — the community can appear in Zeeker feeds, search, and discovery where access permits. Private posts stay members-only.
• Direct access only — the community stays out of Zeeker feeds, search, and discovery, including for members. Use a permitted direct link, your own domain, or an embed on an allowed website.

These choices do not bypass website or app sign-in requirements, allowed websites, membership, or posting rules. Changing them does not remove existing members. Posting is configured separately below.

Allow Zeeker links controls access through the community's Zeeker links separately. Turning these links off requires an active, approved own domain. Visitors and members then use the permitted own-domain or embedded entry; moderators, admins, and owners retain read-only access on Zeeker.

For an older Unlisted community, Access initially shows Public and Direct access only. Opening Settings does not change its stored policy. Saving the Access settings deliberately replaces the old policy with that complete pair, or with another combination you select. Saving unrelated settings without changing access retains the old policy.

Posting

• Allow guest posts — let authenticated non-members post into the community (off by default). Despite the historical label, this does not enable unauthenticated Embed guest sessions.
• Default visibility — community-only or public for posts created from the composer with this community selected.
• Slow mode — minimum seconds between posts per user. 0 = off.
• Disable replies / reactions / shares — coarse-grained controls.

Content and feed defaults

• Allowed post types — select the existing Social post types members may create, such as standard, question, review, and poll when those capabilities are available.
• Allowed reply types — select the structured types members may add beneath an existing post. Contextual Elements such as Reviews, Product Q&A, and Polls use this ordinary reply capability beneath the host object's canonical Social post.

Selecting no structured post or reply types is an explicit text-only policy: ordinary discussion posts/comments remain available, while questions, reviews, polls, trivia, media, links, and other structured choices are unavailable. Communities created before these controls existed retain their legacy unrestricted policy until an administrator saves an explicit selection.

• Post tags — choose up to four tags that members may attach to root posts. The ordered selection can also become the community feed's visible filter lanes.
• Reply tags — choose up to four tags available beneath posts. Replies retain their tags, but reply tags never create filter lanes on an individual post page.
• Community feed header — show either the standard Trending / Popular / Recent lanes or an automatic All lane followed by the selected post tags. All is the default and displays every post. When tag filters are visible, members still control the ordering inside each lane from Preferences.
• Tags per post or reply — choose Single to allow one configured descriptive tag or Multiple to retain the multi-tag composer. Type indicators such as Poll or Review are separate from this descriptive-tag limit.
• Default sort — choose the initial community-feed ordering. Individual embeds may choose another permitted initial sort without inventing a separate feed.
• Related posts on post pages — choose whether normal Social post pages may show related content.
• External related posts — choose whether that related set may include eligible external/source posts. An embed can narrow this to community-only content or turn related posts off, but cannot turn external content on when the community disables it.
• Community chat — enable or disable the community's existing chat capability. Embed presets can select chat only when it is enabled here.

Support Forum embeds may show Social's existing community-scoped search alongside this ordinary question feed. During Support Forum setup, Embed programmatically supplies the bounded support-information box and hides the standard community information card. That box is not authored in Community Settings and is not a community capability. Search remains subject to the community's visibility and viewer permissions. Reviews embeds may show Social's optional rating distribution and a separately optional grounded AI summary. These are shared Social presentation capabilities, not Element-specific data models.

These settings form the capability ceiling for Embed Elements. A Support Forum, Reviews, Product Q&A, or Polls preset selects a subset of these ordinary Social capabilities; it does not create a separate product model.

The canonical community view uses the same feed-header mode in Social and in a full community Embed. Tag-filter lanes support the same horizontal swipe navigation as the standard sort lanes, and server-side filtering is retained while loading more posts.

Group chat access and moderation

Under Settings → Access, enable Group Chat to offer the community chat. The optional Require established members for group chat switch appears beneath it and is off by default. Owners, super admins, admins, and platform admins can save this setting; moderators cannot change it. The same option is available during community creation.

When the switch is on, ordinary users must currently be community members and qualify through either route:

• Community participation: at least 30 days of membership and 3 approved posts or replies in this community.
• Activity across Zeeker Social: a Zeeker account at least 30 days old, plus 10 approved posts or replies in the last 30 days across at least 5 distinct UTC calendar days.

Only approved, undeleted contributions count. Automatically linked continuation posts and isolated Embed contributions are excluded. Community moderators and higher roles, and platform admins, are exempt. The rule applies to embedded group chats too, including users who would otherwise contribute through a guest identity.

Members who do not yet qualify can read the available history, but their message composer is disabled with an explanation. Disabling the switch restores the ordinary chat sending rules. This switch does not restrict personal DMs or private moderator-support conversations.

Community moderators and higher roles can use Hide message and Unhide message in community group and moderator chats while Chat is in Admin mode. The Moderate group chat shortcut on the Admin Center's Moderation page opens the selected community's group chat in that mode. Hidden content is replaced with italic placeholders in the message and its reply and conversation previews; unhiding restores the content and previews. See Chat moderation.

Moderation defaults

• Auto-hide low-reputation posts — when on, posts from accounts under 24 h old land in the mod queue rather than the public feed.
• Toxicity threshold — a slider that controls how aggressively the automated classifier pre-filters content into the mod queue (vs publishing immediately).
• Banned-keywords list — substrings that auto-route posts to the queue.

Zeeker AI

The Zeeker AI settings have a master control plus individual capabilities:

• AI posts — allow Zeeker bots to create main posts.
• Third-party posts — curate posts from approved news and external sources.
• AI replies — allow Zeeker bots to reply to member posts and polls.
• Third-party replies — allow replies grounded in approved external conversations.
• AI reactions — allow Zeeker bots to react to community posts.

Turning off the master control pauses all five capabilities without losing their individual selections. Analytics AI summaries and topic/emotion/relevance views require Zeeker AI to be enabled for the community.

Notifications (for admins)

• Email me when:
  • A new member joins (or requests to join if restricted).
  • A new report enters the queue.
  • A moderator removes a post.
  • The community hits a milestone (1k members, 10k members, etc.).
• Digest cadence — realtime, daily, weekly, or off.

Danger zone

• Archive community — reversible. Becomes read-only.
• Transfer ownership — only owners; pick from the community's admin list.
• Delete community — permanent after 7-day grace period.

Each destructive action requires typing the community slug to confirm.