Spaces

A space is a room in your community — a named channel with its own member roster, posts, and moderation. Everything else in Communities (feeds, intros, lobbies, cohorts) is built on spaces. This page is the studio’s side of a space: how you create one and what you decide about it. What a member sees when they open one is the member room.

Kinds of space

  • Open — a general community channel; the kind most studio rooms use, and what the starter spaces are.
  • Membership — a deliberately curated group. Open and membership spaces behave the same way today (both have a roster the studio manages); the kind records your intent.
  • Cohort — reserved for the automated cohort-space lifecycle. You don’t create these by hand.
  • Pre-class — reserved for the automated pre-class lobby lifecycle. You don’t create these by hand either.

A space is also active or archived. Archived spaces are read-only — moderation still works, but authors can no longer post or edit. (A third state, pending, exists only for member-requested spaces awaiting approval.)

Visibility: private by default, public by choice

Every space is private unless you decide otherwise — visible only to its members (and to community managers and moderators). The one alternative is public read: an admin can make an open or membership space publicly readable, which gives it a calm, indexable page at /community/{slug} with OG tags, schema.org markup, and a sitemap entry. Three guarantees hold on that public page:

  • Cohort and pre-class spaces can never be public. This is enforced in the storage layer — no setting, no API call, no filter can override it.
  • Member identity follows each member’s own settings. A public space never overrides anyone’s consent; an author whose profile isn’t world-visible appears as “A member”.
  • Only deliberately authored, published posts appear. Member activity — joins, reactions, timelines — never surfaces on a public page.

A private, pending, or archived space serves the theme’s ordinary 404 to outsiders — never a “this space is private” confirmation that it exists.

Posting controls: rooms and broadcasts

Each space chooses who writes there, right on the Communities → Spaces screen:

  • Posting — everyone on the roster (the default, a conversation), or moderators only (a broadcast — the shape an Announcements room wants).
  • Comments — on or off for the space. A broadcast room with comments on is “we speak, you respond”; with comments off it’s a pure bulletin.
  • Post kinds — a checkbox per available kind. Give this room announcements, proposals, both, or (the default) neither.

Members who can’t post in a broadcast room still read, react, and comment (when comments are on) exactly as everywhere else.

Roster & moderation

Each space has a roster with roles — member, moderator, and instructor. Moderators are scoped to their space, and instructors and moderators carry a quiet badge beside their name in the room. A member’s role can be changed in place, without removing and re-adding them (which used to lose the date they joined). New people can also arrive already in the right role — see invites. Two moderation tools ship:

  • Mute — a muted member can still read but not post in that space.
  • Ban (with reason) — a banned member loses access to the space; the reason is recorded.

Site-wide, the gg_moderate_communities capability moderates everywhere and gg_manage_communities manages everything. A space’s own moderator can act through the API without either.

Who holds authority in a room

A room’s three roles are ranked: instructor is senior to moderator, which is senior to member. Instructors and moderators both curate that room — its materials and links, its moderation queue, pinning, and announcements — so a studio that rosters its facilitators as instructors doesn’t have to also make them moderators to let them run their own room.

That authority is inside one room, and only rooms that person belongs to. Creating a room, renaming it, archiving it, and changing who can see it all still require a site administrator: an instructor cannot make a private room public. Nothing here changes what a member can do.

Member-created spaces

Off by default. Switch Communities → Settings → Member-created spaces to Request mode and members holding the gg_create_spaces capability (you grant it deliberately — it isn’t given to anyone by default) can propose spaces:

  • Proposed spaces are always open and private — no caller input changes either.
  • Each member can have up to 3 requested spaces.
  • Proposals wait unannounced in the Spaces screen. Approving one announces it; rejecting deletes it without anything ever being announced.
  • The creator becomes moderator of their own space — and only theirs.

Instant (“auto”) creation is planned for 1.1; today the studio approves every member-proposed space.

Instructors are the exception. Switch on Communities → Settings → Instructor-created rooms and any instructor linked through Booking gets a Start a room form on their community portal tab. Their rooms go live immediately — staff trust — with the same hard constraints (open, private, creator becomes the room’s own moderator).

Each space has two curated shelves — Materials (things with a file, uploaded right there) and Links — which the room’s instructors and moderators fill, order, and annotate from inside the room itself rather than from wp-admin. Visibility follows the space: members of a private space see its shelves; a public-read space shows them on the public page too.

Starter spaces

The Create starter spaces button on the Settings screen seeds Studio Welcome and Ask the Instructors, each with a warm first post. It’s idempotent — spaces that already exist are never duplicated.


Applies to Gather Grove Communities v1.78.0. Last synced October 15, 2026.