Space Setup (Guided Assistant)¶
| Field | Value |
|---|---|
| Status | Approved |
| Version | 1.0 |
| Last Updated | 2026-07-27 |
| Author | Claude |
| Reviewed By | — |
The guided assistant "Räume einrichten (geführt)" (set up spaces, guided) answers the question many fresh instances get stuck on: how should content find its spaces? You name districts and topics, the assistant proposes spaces plus the matching routing vocabulary (areas and keyword rules) — and only at the very end is everything created in one go. Browsing through is safe; nothing is created before the last step.
It is aimed at instance admins setting up their first spaces — or extending an existing setup later.
Where do I find the assistant?¶
In the app the assistant is called "Räume einrichten (geführt)" and lives in administration at
the address /governance/setup/spaces. Three paths lead there:
- The "Räume einrichten (geführt)" row in the governance hub — a permanent entry right beside the spaces directory, so re-running it to extend the setup is never buried.
- The first-space choice under Governance → Spaces: as long as the instance has no active space yet, "Geführt einrichten (empfohlen)" (guided setup, recommended) and "Direkt anlegen" (create directly) sit side by side there. Once spaces exist, the single create button returns — the assistant stays reachable via the governance hub.
- The finish step of the instance setup: the link "Jetzt Räume einrichten" (set up spaces now) leads straight here — the natural continuation once the essentials are in place.
Re-callable — extends what exists¶
The assistant is not a one-shot run. On opening, the overview shows under "Bereits eingerichtet" (already set up) which districts, topics (keyword rules), and spaces already exist. The assistant extends what exists instead of duplicating it: existing districts, keyword rules, and spaces are reused; an existing topic is extended with new keywords, not created twice. So the setup can be run again at any time — for example to add another district or a new topic.
The seven steps¶
| Step | Title | Content |
|---|---|---|
| 1 | Overview | What the assistant does + what is already set up |
| 2 | Structure | By districts, by topics, or both? |
| 3 | Districts | Which districts get a space? |
| 4 | Topics | Which topics get a space — with which keywords? |
| 5 | Spaces | Adjust the proposed spaces (name, access, code of conduct) |
| 6 | Preview | "This will be created" + a worked example |
| 7 | Create | Create everything in one step — on any error, nothing is created |
Depending on the answer in step 2, the assistant skips what is not needed: structuring by topics only means no districts step — and vice versa.
Step 1 — Overview¶
Explains what happens and shows under "Bereits eingerichtet" the existing districts, topics (keywords), and spaces. On a fresh instance it says honestly: "Nothing is set up yet — this assistant starts from zero."
Step 2 — Structure¶
The fundamental question: how should spaces be structured? Three answers are available:
| Choice | What is produced |
|---|---|
| By districts | One space per district — e.g. "Nord" and "Altstadt". A post mentioning a district lands in its space. |
| By topics | One space per topic — e.g. "Sport" and "Kultur". A post with matching keywords lands in the topic space. |
| Both | District spaces and topic spaces side by side — a post can land in several spaces, e.g. "Fußballturnier in Nord" in "Nord" and in "Sport". |
Step 3 — Districts¶
Which districts should get a space? Districts are entered as chips. Each district becomes a routing area: a post is assigned to it when the area name is recognised in the text. Hence the naming hint: pick the spelling that actually appears in articles — "Altstadt", not "OT 3". Already-configured areas are offered as suggestions and adopted with a click.
Step 4 — Topics¶
Which topics should get a space? The assistant ships a topic catalogue; custom topics can be added via "Thema hinzufügen" (add topic). Every topic brings a keyword rule with it: a post whose text contains one of the keywords gets the topic. The keywords are editable per topic — in German, because they have to match the text of your sources. A new topic needs at least one keyword; an already-existing topic honestly says: "vorhanden — n Stichwörter, wird erweitert" (exists — n keywords, will be extended).
Keyword rules apply instance-wide
Keyword rules apply to the whole instance — they also tag posts for future sources and spaces, not just the ones created here. The assistant says so right where it matters.
Step 5 — Spaces¶
"Diese Räume werden vorgeschlagen" (these spaces are proposed) — derived from the structure: one space per district and/or per topic. Per space you can adjust:
- Name and description — the name also determines the later web address (slug).
- Access (join mode) —
Open,Request,Invite only, orManaged. A note right in the step: spaces with access "invite only" or "managed" are not publicly visible. - Code of conduct (optional) — the house rules new members see before joining; can be added later in the space settings.
- Deselect — every proposed space can be deselected entirely via its checkbox.
Every space carries a line stating how it collects: "collects by district", "collects by topic" — or, for intersection spaces, "area AND topic required".
Intersection spaces (optional)¶
With the structure choice "Both", the assistant additionally offers intersection spaces — deselected by default, pure opt-in. An intersection space collects only posts that match area AND topic: "Sport in Nord" gets football from Nord, for example, but not all sport and not everything from Nord. Technically this creates a space with the hybrid combination AND.
Step 6 — Preview¶
The preview "Das wird angelegt" (this will be created) lists the complete plan: districts, keyword rules, and spaces — each with honest badges (new, exists, will be extended). If a space's address collides with an existing one ("Adresse bereits vergeben" — address already taken), the preview says clearly: rename the space in the previous step, otherwise nothing is created.
Below it, "Einmal durchgespielt" (played through once) runs the plan against an example: a post with a title like "Fußballturnier in Nord" — and the list of spaces it would land in, computed with the same rules that will really apply later: district spaces match via the area name in the text, topic spaces via keywords — intersection spaces need both.
Step 7 — Create¶
"Jetzt alles anlegen?" (create everything now?) — everything from the preview is created in one step. Creation is atomic: if anything fails, nothing at all is created — you can adjust and try again. On success the assistant summarises what was created, extended, and reused, and reminds you: content flows once sources are connected — routing can be observed under Governance → Routing.
Related pages¶
- Spaces — the spaces directory with lifecycle actions and direct creation
- Routing rules — the four routing phases and the hybrid combination OR/AND
- Areas and Keyword tags — the routing vocabulary in detail
- Instance setup — the essentials setup that comes before