Spaces & page tree
Per-tenant wiki Spaces with access and edit-role controls, resolving to a hierarchical, cycle-guarded page tree of rich-text HTML pages.
Wiki & Help Center
One source of truth, wired into the app.
A per-tenant wiki with spaces, rich-text pages, version history and full-text search — plus a contextual in-app help drawer and a public, branded help center.
Guided tour
A manager creates a Space, drafts a page with the AI copilot as sanitized HTML, and publishes it to the public help center.
app.talentm.net / wiki / agency-playbook
Space · Agency PlaybookAI draft
Creator onboardingEditing
Step 1 — Invite the creator to their portal. Step 2 — Collect the tax and payout details. Step 3 — Publish the first SetCard…
AI-drafted · sanitized HTML
⤒ Publish⧉ Save as template
Published to the public help centerPublic space
What you get
Everything in the module.
Editor & history
A rich-text editor with version history, reusable page templates, markdown import/export and per-page feedback. The AI can draft a page as sanitized HTML.
Agency-wide search
Full-text search across every Space, so the one page that answers the question is a query away — not a folder hunt.
Cross-links & CRM pins
Wikipedia-style page-to-page cross-links plus object bindings — pin a playbook to a deal, a creator or a campaign, right where the work happens.
Contextual in-app help
Feature-key bindings mean the in-app “?” drawer deep-links to the exact article for the screen you’re on; governance gates catch orphaned bindings and features with no help page.
Public branded help center
A public help center at /docs/<agency-slug> — public-space pages only, agency-branded and locale-aware (DE/EN), no login. The same substrate powers the portal and ticket-portal knowledge base.
Facts, not promises
- Spaces have access and edit-role controls; the page tree is hierarchical and cycle-guarded.
- Help pages bind to app features by feature-key, so the in-app “?” drawer opens the exact article for the screen you’re on.
- The public help center at /docs/<agency-slug> shows public-space pages only, is agency-branded and locale-aware (DE/EN), and needs no login.
- It ships as a built-in help center with feature-linked articles — every major feature ships its own — seeded per tenant, so you add and edit your own.
FAQ
Questions, answered.
How many help articles are included?
The help center is tenant-seeded, so there is no fixed number to quote: you get a built-in help center with feature-linked articles, and every major feature ships its own. From there you add, edit and cross-link your own — the count grows with your knowledge base, not with a marketing claim.
How does the in-app help know which article to show?
By feature-key bindings: each help page binds to an app feature, so the “?” drawer deep-links to the exact article for the screen you’re on. Governance gates flag orphaned bindings and features that still have no help page, so the coverage stays honest.
Is the public help center really public — no login?
Yes. /docs/<agency-slug> serves public-space pages only, agency-branded and locale-aware (DE/EN), with no login required. It renders client-side, and the same substrate powers your portal knowledge base and the ticket-portal KB search.
Can we structure and reuse the content?
Per-tenant Spaces resolve to a hierarchical, cycle-guarded page tree with reusable templates, version history, agency-wide full-text search, markdown import/export and Wikipedia-style cross-links. You can pin a page to a deal, creator or campaign, and let the AI draft new pages as sanitized HTML.
Write it once, find it everywhere.
One wiki behind the app, the in-app help drawer and a public help center — no login, no copy-paste, no drift.
No credit card · EU-hosted · GDPR & GoBD-ready