Creating a community

A community is the unit of ownership on Zeeker. Anyone with a Zeeker account can create one — there's no approval, no application form. Communities are created in under a minute.

The flow

1. Sign in to https://admin.zeeker.com.
2. Click + Create new community in the sidebar (or Create a community on the empty-state marketing page).
3. Fill out the New community wizard:
   • Name (display name, 3–50 chars).
   • Slug (URL identifier, lowercase a–z, 0–9, hyphen, 3–30 chars). Used as zeeker.com/c/<slug>. Auto-suggested from the name.
   • Tagline (one-line description, ≤ 140 chars).

• Category (optional — picks a default color and helps discovery).
• Community access:
  • Public — anyone can read posts without joining the community.
  • Private — only community members can read posts.
• Zeeker visibility:
  • Connected to Zeeker — can appear in Zeeker feeds, search, and discovery where access permits. Private posts stay members-only.
  • Direct access only — hidden from Zeeker feeds, search, and discovery. Use a permitted direct link, your own domain, or an embed on an allowed website.
• Zeeker AI — choose whether automated posts, curated third-party content, replies, grounded replies, and reactions are enabled.
• Content & Tags — select up to four post tags, optional reply tags, the visible community-feed header (sort tabs or tag filters), and whether each post or reply may use one or multiple descriptive tags. Tag-filter mode automatically adds All as the first/default lane.

4. Click Create. The community is provisioned instantly.

Community access and Zeeker visibility are independent. Neither choice bypasses website or app sign-in requirements, allowed websites, membership, or posting rules. Per-embed connection (connected or, when supported, embed_only) is a separate policy. Review Community settings → Access to manage these choices and Zeeker links after creation.

What happens on create

When you create a community we:

• Assign the calling user as the owner (highest role).
• Reserve the slug — it's globally unique.
• Provision a community feed at zeeker.com/c/<slug>.
• Set sensible defaults for theme (matches Zeeker neutral palette), rules (empty), members (just you).
• Initialise an empty embed config list — you can create the first one from the embed configurator.

Next steps after creation

The first time you land in your new community, the admin center walks you through a 5-step Onboarding checklist in the sidebar:

1. Add a logo & cover — see Community settings → Theme.
2. Write your rules — up to 10 short rules. These show on your community page and in the report dialog.
3. Invite moderators — see Members.
4. Create your first embed config — if you plan to use the widget, this generates a config ID for your script tag.
5. Wire up SSO (optional) — if you want your users to sign in to the widget automatically. See SSO.

Before publishing an Element, also review the community's allowed post types, post/reply tags, feed-header mode, tag cardinality, default sort, related-post/external-content policy, and chat availability. These are the Social capabilities an embed may narrow and present. Implementation-owned additions such as the Support Forum information box are applied by the Embed preset and are not Community Settings fields.

The checklist is dismissable. You can come back to it from the dashboard at any time.

URL & branding

After creation, your community is reachable at:

• zeeker.com/c/<slug> — the public community page on the network.
• Embeds you create for this community pick up the community's theme automatically (unless you override per-config in the configurator).

Renaming & changing the slug

• Name can be changed any time from Settings → General.
• Slug can only be changed within 7 days of creation, and only once. After that it's permanent — slug changes break inbound links and embed scopes, so we lock them down.

Limits

	Limit
Communities per account	10 (raise on request)
Slug length	3–30 chars
Rules	10 max, 120 chars each
Moderators per community	50
Embed configs per community	20

Deleting a community

From Settings → Danger zone:

• Archive — the community becomes read-only; nobody can post or react. Reversible.
• Delete — permanent after a 7-day grace period during which the owner can undelete.

Deletion removes the community feed and unbinds embed configs (the widgets stop rendering on host sites). Posts authored by individual users remain on zeeker.com in their personal timelines unless those users delete them.