Administrator User Manual

Audience: site admins, editors, operators
Entry: /admin
Member-facing manual: user-manual-member.en.md
Chinese version: user-manual-admin.md
Knowledge base product plan: knowledge-base-product-plan.md

Day-to-day operations only—no deploy or source deep-dives. For handoff, upgrade, and rollback see ops-delivery.md.

---

0. Which sections apply? (module packs)

Site shape	Focus on	Often ignore
Tech / link nav	§3 Navigation, dashboard, settings	Forum / Space if disabled
Blog-first	§4 Content, comments, submissions, SEO	Nav tabs if pure blog mode
Community	§5 Forum & Space, users, moderation	Ads unless sold
Full stack	All sections	—

If a sidebar tab is missing, the module is off or the role lacks permission.

---

1. Sign-in and permissions

1. Open /admin and sign in with an admin account.
2. Sidebar tabs follow role permissions and module switches.
3. Super-admins have everything. Typical grants:
   • Nav: nav.links / nav.categories
   • Content: content.posts / content.pages / comments / submissions
   • Community: forum.moderate / space.manage
   • Knowledge base: kb.manage
   • Settings: settings.*, users users.*

Prefer least privilege: editors need content rights, not system settings.

---

2. Admin sidebar overview

Tab	Purpose
Dashboard	Traffic, outbound clicks, content snapshot
Links / Categories / Home layout	Nav directory structure
Posts	Blog posts, SEO, publish state
Pages	Static pages (about, friends, …)
Media	Shared image/file library
Tags	Post tags
Submissions	Front-end submissions queue
Comments	Moderation
Forum	Boards, threads, reports
Space	Channels and policies
Feedback & appeals	User feedback and moderation appeal review
Feed	Timeline sources / health
Ads	Brand placements
Notifications	Email / push channels
Webmail	In-site mail (if enabled)
Users	Members and roles
Translations	Content translation versions
Knowledge base	Public/team workspaces & docs
Jobs	Scheduled tasks / backup jobs
Settings	Brand, modules, SEO, …

Disabled modules hide their tabs and front-end entry points.

---

3. Navigation site

1. Categories first, then links under them.
2. Home layout controls homepage order and featured areas.
3. Use trash/recycle flows when available before hard-deletes.
4. Spot-check dead links and search after large link changes.

---

4. Blog and content

1. Posts: title, Markdown body, tags, cover, draft/publish.
2. Use SEO checklist (title, summary, slug).
3. After publish verify /blog, detail page, RSS/sitemap as configured.
4. Pages for evergreen pages—not the blog timeline.
5. Media for uploads; avoid hotlinked assets.
6. Submissions and Comments: review queue daily.

---

5. Community: forum and Space

• Forum: boards, pins, lock, reports; encourage “save to knowledge base” for durable conclusions.
• Space: channels, pins, abuse handling; chat is ephemeral—docs belong in KB or blog.

5.1 Feedback and moderation appeals

1. Open Feedback & appeals with the feedback.manage permission.
2. Routine forum removal is a reversible hide. Hiding a published thread/reply, removing a Space message, muting, or banning creates a seven-day appeal record.
3. The administrator who applied an action cannot review that action; route it to another administrator or the super administrator.
4. Approval restores content, forum counters/feed visibility, or Space access. Both approval and rejection require a written response.
5. Permanent forum deletion remains super-admin only and should not be used for routine report handling.

5.2 Space ↔ Telegram bridge (mention-only)

Admin Space → Telegram bridge:

1. Configure Bot Token under Notifications (shared with system alerts).
2. Add the bot to the TG group; note the group chat_id (usually negative).
3. Set webhook to https://your-domain/api/telegram/webhook (HTTPS).
4. Bind Space channel + chat_id; toggle TG→Space / Space→TG as needed.

Direction	Trigger	Effect
TG → Space	@Bot mention or reply to bot	Post text, files, or media into the bound channel
Space → TG	Editor Send to Telegram action	Forward through the stable internal bridge marker
Other	No @	Not forwarded (no mirror)

Loop-safe: ignore bot messages; bridge shadow user posts do not bounce back to TG.

Reply to target media and send only @Bot, or send /fwd or /forward, to sync an image, GIF, file, video, audio, or sticker. Video stickers are supported; animated .tgs stickers are not supported yet. Other messages remain mention/reply gated.

5.3 Media and content safety

• Configure temporary Space media and the private Telegram storage channel under System settings → Storage. Telegram audio/video is proxied on demand and is not cached locally.
• Preview support covers images, audio, video, PDF, Markdown, and the first Excel worksheet. Word and other files download. HTML, scripts, and executables are rejected.
• spam_bad_words accepts comma/newline-separated additions. Forum, blog, and Space mask matching terms on write instead of deleting the complete content. Keep the list limited to clearly disallowed terms.
• Use Security Center for administrator 2FA, recovery codes, and login audit. Do not manage 2FA through ordinary system settings.
• Configure in-app, email, Telegram, and browser notifications under Notifications. Test announcements and broadcasts with a small audience before a full send.
• Space supports anonymous channels, member/channel permissions, and temporary-media cleanup. Anonymous mode changes display identity only; set cleanup for the available disk capacity.
• S3/R2 backup retention is configurable with a minimum of one copy. Review backup jobs, restore drills, and object cleanup regularly.

---

6. Knowledge base (operators)

Three layers:

Layer	Who writes	Who reads	Admin edits body?
Public	Admins with kb.manage	Everyone (published)	Yes
Team	Admins	Signed-in users	Yes
Personal	Owner only	Owner (+ optional share link)	No

Manage spaces and docs

1. /admin?tab=kb
2. Create/enable public or team workspaces (often a docs public space).
3. Manage documents: tree of folders/articles, drag reorder.
4. Create → Markdown → set status to published for public read.
5. Prefer slug URLs: /kb/w/{workspace}/{doc}.

Acceptance checklist

• /kb lists public space
• Published docs have stable slug URLs
• Drafts invisible to anonymous users
• Site search finds public published KB only (never personal)
• Footer/nav KB entry when kb_enabled

Settings keys (names may match UI)

• kb_enabled master
• kb_public_enabled / kb_team_enabled / kb_personal_enabled

Do not edit members’ personal notebook bodies in admin—privacy boundary.

---

7. Users and roles

Enable/disable accounts and assign roles. Accounts may belong to multiple user groups: backend roles control administration, while groups drive invite attribution, targeted broadcasts, and Space channel visibility. The system Registered Users group automatically contains every account and cannot be deleted.

Invite codes can set a usage limit, expiration, and an additional group assigned after signup. They never bypass the master registration switch.

---

8. Settings and SEO

Site name, description, default locale, module toggles, robots/sitemap, mail for verify/subscribe/comments. Under Brand & media, the OG image studio can combine a local backdrop with brand copy, export a 1200×630 PNG, or upload it into the global OG field. The source backdrop stays in the browser; save system settings after generating to publish the new URL.

After module changes, smoke-test front-end in a private window.

---

9. Feed, ads, jobs

Confirm feed sources; ads without creatives should not force placements; watch scheduled job logs for backup/push failures.

---

10. i18n

UI is Chinese/English. User content stays original; use Translations for optional versions. API errors should localize in English UI.

---

11. Cadence

When	Do
Daily	Comments, submissions, reports; dashboard spikes
Weekly	Public KB updates; link health sample
Monthly	Roles review; backup/job success
After release	ops-delivery.md checklist

---

12. FAQ

No KB tab? Login, kb.manage, and kb_enabled.
/kb empty? Public workspace enabled + published docs.
Stale front page? Status published? Correct workspace? Hard refresh.
Users can’t find personal KB? Point to /kb/me or Me → Knowledge base; personal layer must be on.
Share link indexed? Pages are noindex and out of site search; revoke if leaked.

---

13. Related docs

Doc	Role
Member manual (EN)	Signed-in members
Member manual (ZH)	中文会员
KB plan	Feature matrix
Ops delivery	Deploy / upgrade

---

Aligned with knowledge base P1–P16. Prefer live UI labels when they differ from this text.