> ## Documentation Index
>
> Fetch the complete documentation index at: https://lithi.ai/llms.txt
>
> Use this file to discover all available pages before exploring further.

Team Knowledge lets approved teammates reuse a defined source for a defined purpose. SwarmOS keeps that shared context separate from private inboxes and drafts, so your team can review each answer before acting.

## Purpose of team knowledge

Team knowledge answers a practical question: can an approved teammate use an approved source for an approved purpose? A **Knowledge Base** is the approved collection of documents, facts, and rules Lithi may use to help prepare an answer. It is not a free-form memory or a copy of every company file.

Use this boundary when your team needs consistent answers about a policy, process, product rule, or operating practice. Start with a defined question and named owner. A narrow purpose makes review easier than a broad instruction to share everything.

## Approved source boundary

An authorized person deliberately allows a source for a defined team purpose. The source can be a document, fact, rule, or other approved context. Approval for one source does not silently include another source, a different document, or a private inbox.

A connection or team membership also does not turn unrelated material into shared context.

Before adding a source, record:

- Who owns the source and who is responsible for keeping it current?

- Which document, section, or fact is included?

- Which team, role, or project may use it?

- What question or task is the source meant to support?

- When should someone review it again?

If those answers are unclear, leave the source out or ask the owner to narrow the scope. Approved Team Knowledge describes permission and purpose; it does not make every company record available to every reader.

## Use shared context carefully

SwarmOS lets approved teammates reuse a rule, procedure, or source-backed fact. Keep the shared result limited to the question, source, audience, and purpose that were approved.

Private inbox content, drafts, credentials, and unrelated personal knowledge remain outside this boundary. A citation shows which source supports an answer, but your team still decides what to do next.

## Review and revocation

Review is part of the source lifecycle. An owner or administrator can check whether the source still serves its purpose, whether the audience is right, and whether its content needs an update. Teammates should flag stale wording, an unexpected audience, or a question beyond the source scope.

When circumstances change, an owner can narrow a grant, change a role’s purpose, pause a permission, set an expiry, remove a member, or **un-share** a source. Un-sharing revokes the grant and handles cached answers under the applicable policy. A revoked permission is not an active approval for a new request.

The review record can preserve that an approved use occurred while making the changed permission clear for future work.

## Review before you rely on an answer

Check the requesting person, selected source, purpose, and permission in force. A grant for one source or purpose does not apply elsewhere.

If a source is missing, narrowed, paused, expired, or revoked, keep the request outside the approved context. Ask the knowledge owner to resolve conflicting sources or an unanswered question.