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

# Pharen Hub documentation

> Start here to understand Pharen Hub, the AI workspace that brings team work, knowledge, workflows, communication, and agents into one shared context.

Pharen Hub is an AI workspace for teams that want less tool chaos and more shared context.

It brings docs, lists, communication, workflows, approvals, and AI agents into one place. Not as another tab next to your existing stack, but as a workspace where people and agents can work from the same source of truth.

## What you can do here

This documentation helps you understand the product, set up a workspace, and build with Pharen without guessing where things belong.

<CardGroup cols={2}>
  <Card title="Understand the workspace" icon="layout-dashboard" href="/general/concepts">
    Learn the core ideas behind workspaces, docs, lists, workflows, approvals, and agents.
  </Card>

  <Card title="Run it locally" icon="terminal" href="/general/local-setup">
    Set up the development repo, run quality checks, and contribute changes without fighting the toolchain.
  </Card>

  <Card title="Explore Hub modules" icon="boxes" href="/hub/overview">
    See how docs, lists, channels, mail, workflows, and AI agents fit together in the product.
  </Card>

  <Card title="Use the API" icon="code-2" href="/api-reference/introduction">
    Authenticate, create pages, update resources, and connect Pharen with your own systems.
  </Card>
</CardGroup>

## The short version

Most teams already have enough software.

They write in docs, plan in tasks, talk in chat, store process data in spreadsheets, approve work in email, and ask AI in a separate window. The work happens between those tools, so the context gets lost.

Pharen Hub is built around a different idea:

<Note>
  AI becomes useful when it can work inside the same context as the team.
</Note>

That means an agent can read the right document, inspect a list record, trigger a workflow, request approval, and leave a clear trace for the team. It also means humans stay in control. Agents prepare, route, summarize, and execute work, but approvals and permissions remain part of the system.

## Where to start

If you are new to Pharen, start with these pages:

<Steps>
  <Step title="Read the core concepts">
    Start with [Core concepts](/general/concepts) to understand the language used across the docs.
  </Step>

  <Step title="Set up a workspace">
    Use the [Quickstart](/quickstart) if you want to try the hosted product with a real workspace.
  </Step>

  <Step title="Set up local development">
    Use [Local setup](/general/local-setup) if you are contributing to the product or working with the monorepo.
  </Step>

  <Step title="Go deeper into a module">
    Jump into [Workflows](/workflows/overview), [Lists](/lists/overview), [Studio](/studio/overview), or [AI Agents](/hub/ai-agents) once you know what you want to build.
  </Step>
</Steps>

## A note on tone

Pharen is not documented as a generic SaaS dashboard. The product is opinionated: context matters, agents need guardrails, and work should not be scattered across five disconnected tools.

The docs follow that same line. They should be practical, clear, and human. If a page does not help someone make a real decision or complete a real task, it needs to be tightened.