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

# Mibyan Work

> An AI-native workspace that turns organizational goals into projects, tasks, decisions, and meetings, with humans approving what matters

**Mibyan Work** is the organization workspace. Instead of asking you to write every task, it starts from your organization's **goals**, proposes a strategy, staffs the work with people and digital specialists, and brings only the decisions that need a human to your **Decision inbox**.

<Note>
  Mibyan Work is for teams. If you work alone, start with [Chat and agents](/features/chat-and-agents) and come back when you need shared goals, approvals, and audit.
</Note>

## The idea in one picture

```mermaid theme={null}
flowchart LR
  A["Goals<br/>what we are working toward"] --> B["Strategy draft<br/>proposed plan and team"]
  B --> C{"Human approval"}
  C -- "Approve" --> D["Projects and tasks"]
  C -- "Reject" --> A
  D --> E["People and digital specialists"]
  E --> F["Deliverables and evidence"]
  F --> G["Leadership home<br/>progress and exceptions"]
  E -. "needs authority" .-> C
  G --> A
```

Every artifact stays connected to its context: a meeting, a decision, a task, a document, and a project form one traceable graph, and every accountable action is written to the [audit log](#audit-log).

## Where things live

<CardGroup cols={2}>
  <Card title="Home" icon="gauge">
    The leadership command center: organization indicators, items that need your attention, the top goal, and your team of people and digital employees.
  </Card>

  <Card title="Goals" icon="bullseye">
    A goal tree. Start with the top goal, then add the strategic goals that lead to it, so every project and task has a measurable reason.
  </Card>

  <Card title="Projects" icon="folder-tree">
    Turn approved goals into initiatives. Each project links to a goal, so the team knows why it exists.
  </Card>

  <Card title="Work" icon="list-check">
    Tasks the executive layer created and delegated from your goals, with their state: queued, claimed, working in the background, waiting for approval, timed out, or stopped for budget.
  </Card>

  <Card title="Approvals" icon="stamp">
    The Decision inbox. Review strategy, specialist hiring, budgets, and sensitive actions. Nothing proposed starts before you approve it.
  </Card>

  <Card title="Meetings" icon="video">
    Meetings tied to the organization, with transcripts and summaries. See [Mibyan Meet](/products/meet).
  </Card>

  <Card title="Ask Mibyan" icon="comments">
    One answer grounded in the organization's context: goals, projects, work, decisions, and meetings.
  </Card>

  <Card title="Audit" icon="clock-rotate-left">
    Who did what, and when, for every accountable action inside the workspace.
  </Card>
</CardGroup>

## How a new organization starts

<Steps>
  <Step title="Create the organization and its charter">
    Describe the organization and what it exists to do. Mibyan reads the charter, the goals, and the current state of work.
  </Step>

  <Step title="Review the strategy draft">
    The executive layer builds a first strategy draft and proposes a team of specialist agents. It appears in **Approvals** as a decision waiting for you.
  </Step>

  <Step title="Approve to start">
    Approving creates the organizational record, goals, projects, and tasks in one step. Tasks start in the queue. Rejecting the draft changes nothing.
  </Step>

  <Step title="Let the work run, and step in on exceptions">
    The leadership assistant delegates tasks within the authority you approved. Anything outside those limits comes back to you as a decision.
  </Step>
</Steps>

<Warning>
  Approving a strategy does not approve external actions. Any external action, budget spend, or outbound message still needs its own separate approval.
</Warning>

## Autonomous execution and budget

The executive layer can keep working after you close the page. This is controlled from the **Work** page:

| Control | What it does |
| - | - |
| Enable / disable the worker | Turns background execution on or off. When off, nothing runs automatically. |
| Monthly budget (USD) | A strict monthly cap on autonomous work. Tasks that hit it move to *stopped for budget*. |
| Run a cycle now | On the Home page, triggers an executive cycle immediately instead of waiting. |

When a task needs a human it moves to *waiting for approval* and appears in your Decision inbox. If a task cannot finish in time it is marked *timed out*, and a blocked task is flagged so you can remove the blocker.

## Decisions you will see

<AccordionGroup>
  <Accordion title="Strategy and operating plan" icon="chess">
    A versioned strategy draft with proposed goals, projects, tasks, and the proposed agent team. Approve to start, or reject the draft.
  </Accordion>

  <Accordion title="Hiring a specialist agent" icon="user-plus">
    The executive layer may propose adding a specialist digital employee when it finds a gap in the team. You approve or decline the hire.
  </Accordion>

  <Accordion title="High-risk agent actions" icon="triangle-exclamation">
    Agents surface risky actions for a decision. You can **approve and resume**, or **reject and stop**.
  </Accordion>
</AccordionGroup>

## Members and roles

The **Members** page shows who holds which role in the workspace. A member's role decides which autonomy zone they can approve.

* Only an organization **owner or manager** can create goals, and approving strategy or agent decisions requires the matching role or higher.
* To invite someone, enter their email to create an **invitation link that is valid for 7 days**. Copy and share it yourself; no email is sent automatically.

## Audit log

The audit page records every accountable action in the organization: who acted, what they did, and when. Because AI work carries an owner, evidence, status, and approval, you can always answer *why did this happen* without reconstructing context from several tools.

## Good to know

* Mibyan Work reuses your Mibyan account. External guests join only narrowly scoped experiences such as a meeting or an approval.
* Arabic right-to-left is a first-class experience, and mixed Arabic and English content is supported.
* The inbox is for decisions and exceptions, not activity noise.

<Card title="Next: run meetings with summaries" icon="video" horizontal href="/products/meet">
  Mibyan Meet transcribes and summarizes, then feeds decisions and tasks back into the organization.
</Card>