Organization Wiki (Second Brain)

What is the Organization Wiki?

The Organization Wiki is your team’s second brain — a shared, persistent knowledge base that every agent in your organization can read and write during conversations. Product specs, compliance rules, buyer profiles, FAQs, meeting outcomes, research findings — anything your team learns once becomes knowledge every agent can use forever.

Tell your agent “save this to the wiki” — and from that moment, every agent in your organization knows it.

Shared Across All Agents

Unlike personal memory, wiki knowledge belongs to the organization. Every orchestrator agent reads the same wiki.

Zero Setup

Wiki tools are automatically available to all orchestrator agents. No configuration, no tool assignment needed.

Built by Conversation

Any member can grow the wiki just by chatting. Agents save research results, decisions, and facts as they work.

Always-Current Index

The wiki index is generated automatically from your documents — it never goes stale and needs no manual upkeep.

How Agents Use the Wiki

During any conversation, your orchestrator agent can:

Action	What Happens
Check the index	Before answering, the agent scans the wiki index (every document + its one-line summary) to see if your organization already knows the answer
Read a document	Opens the full content of a relevant document and uses it to answer
Create a document	Saves new knowledge when you ask (“save this to the wiki”, “remember this for the team”) or after completing research
Update / edit	Replaces a document or makes a precise partial edit without touching the rest
Append	Adds new entries to an existing document over time — FAQ items, meeting notes, new cases

Deletion is human-only. Agents can create and edit wiki documents, but only admins can delete them — from the Team → Wiki page. This protects your knowledge base from accidental loss.

Example Conversations

You: "우리 제품 반품 정책이 뭐였지?"
Agent: (checks wiki index → reads policy/returns) "반품은 수령 후 14일 이내..."

You: "Research the top 3 competitors and save a summary to the wiki."
Agent: (researches, then creates competitors/overview with a one-line summary)
       "Saved to the wiki — every agent in your team can now reference this."

You: "이번 회의 결론 위키의 회의록에 추가해줘."
Agent: (appends to meetings/notes) "Added today's decisions to the meeting notes."

Managing the Wiki (Team → Wiki)

Admins and owners can manage wiki documents directly in the dashboard at Team → Wiki:

Browse documents

The left sidebar lists all documents with their keys and one-line summaries. Select any document to read it rendered as Markdown, with its last-updated time.

Create or edit

Click New Document to add knowledge manually — give it a document key (e.g. product/faq), Markdown content, and a one-line summary for the index. Edit updates content in place.

Delete when needed

Delete removes a document permanently (agents will no longer see it). Deletion is only possible here — never through chat.

Changes made in the dashboard are visible to agents immediately — the next message in any conversation already uses the updated knowledge.

Document Keys

Documents are organized with hierarchical keys — category/topic — in any language:

product/faq
compliance/광고심의
customers/enterprise-buyers
meetings/notes

Each document also carries a one-line summary shown in the index, which is how agents decide what to read.

Who Can Do What

Action	Members	Admins / Owners
Agents read wiki in chat	✅	✅
Agents save/edit wiki via chat	✅	✅
Manage documents in Team → Wiki	❌	✅
Delete documents	❌	✅ (dashboard only)

The wiki is isolated per organization — one squad’s wiki is never visible to another squad.

Wiki vs Memory vs Soul

Junis has three complementary knowledge systems. Use the right one for the right job:

	Memory	Soul & Identity	Wiki (Second Brain)
Scope	Per user (personal)	Per organization	Per organization
Answers	”Who is this user?"	"Who is our AI?"	"What does our team know?”
Contains	Your profile, preferences, standing instructions	AI philosophy, personality, communication style	Product specs, policies, FAQs, research, decisions
Managed at	Your Memory page	Team → Soul	Team → Wiki
Grown by	Your own conversations	Admins	Every member’s conversations

Rule of thumb: facts about you → Memory. How the AI should behave → Soul & Identity. Facts your whole team should share → Wiki.

Best Practices

Recommended:

Ask agents to save reusable findings: “위키에 저장해줘” after research, analysis, or decisions
Use consistent key prefixes (product/, policy/, customers/) so knowledge stays organized
Keep each document focused on one topic — agents read whole documents
Review the wiki periodically in Team → Wiki and prune outdated documents

Avoid:

Storing personal preferences in the wiki (use Memory instead)
One giant document for everything — smaller focused documents retrieve better
Storing secrets or credentials — the wiki is readable by all organization members’ agents

What’s Next?

Memory System

Personal, per-user persistent memory

Soul & Identity

Define your AI team’s personality

Tools Overview

All built-in agent capabilities

RAG Knowledge Base

Upload large document sets for semantic search

​What is the Organization Wiki?

Shared Across All Agents

Zero Setup

Built by Conversation

Always-Current Index

​How Agents Use the Wiki

​Example Conversations

​Managing the Wiki (Team → Wiki)

​Document Keys

​Who Can Do What

​Wiki vs Memory vs Soul

​Best Practices

​What’s Next?

Memory System

Soul & Identity

Tools Overview

RAG Knowledge Base

What is the Organization Wiki?

How Agents Use the Wiki

Example Conversations

Managing the Wiki (Team → Wiki)

Document Keys

Who Can Do What

Wiki vs Memory vs Soul

Best Practices

What’s Next?