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

# Jinn for your role

> How Jinn helps QA engineers, developers, managers, support, sales, recruiters and founders, and where each of them should start.

Your team sits in the same meetings and reads the same specs, but nobody takes the same thing
away from them. A tester listens for what can break, a developer for what changes in the code,
a manager for who owns what. Jinn keeps the meetings and docs in one place and lets each person
get their own reading of them, without anyone writing the notes by hand.

> [!NOTE]
>
> If you're the first person from your team in Jinn, start with the
> [Quickstart](https://docs.jinn.so/getting-started/quickstart.md). It sets up the workspace and takes one real meeting
> from start to finish. The pages below assume that's done.

## How Jinn works for every role

Whatever your job, you work with the same few things:

* **Projects.** Your team's meetings and docs are kept in [projects](https://docs.jinn.so/projects/manage-projects.md),
  usually one per team, client or stream of work. A private project is open only to the people
  added to it, an open one to everyone in the workspace.
* **Meetings.** Someone records a call from the Jinn desktop app, with no bot joining, or
  uploads a file. Jinn writes out who said what. See [recording a meeting](https://docs.jinn.so/meetings/record-a-meeting.md).
* **Agents.** An agent is AI that reads a meeting the way one role would — a tester, a recruiter,
  a salesperson — and writes up what matters to that role. The **Default** agent writes a summary
  and the action items about every meeting by itself; the others start when you ask. See
  [agents](https://docs.jinn.so/agents/add-an-agent.md).
* **Chat.** Ask a question in plain words about one meeting, one project or everything you can
  open. The answer comes from your workspace, with its sources attached. Type `/` to have it do a common job
  your way — a follow-up, a job description, a weekly brief. See
  [asking a question](https://docs.jinn.so/find/ask-a-question.md).
* **Search.** Press **⌘K** and find a passage by what was said, even months later. See
  [search](https://docs.jinn.so/find/search.md).

The chat and search never show anyone what they can't open.

## Find your role

Each page takes a few minutes to set up and then gives you the steps you'll repeat every week.

> [card] [Founders](https://docs.jinn.so/for/founders.md)
>
> Every important meeting without going to it, answers from anything the company discussed,
> and knowledge that stays when people leave.

> [card] [Managers](https://docs.jinn.so/for/managers.md)
>
> Notes for the whole team from one recording, owners and deadlines in one question, and the
> weekly brief written for you.

> [card] [Support teams](https://docs.jinn.so/for/support-teams.md)
>
> Every customer call written up, answers you can check before you reply, and a hand-over
> nobody has to retell.

> [card] [Sales teams](https://docs.jinn.so/for/sales.md)
>
> A write-up of every call, the follow-up in minutes, and a deal's whole history before the
> next one.

> [card] [Recruiters](https://docs.jinn.so/for/recruiters.md)
>
> The role and the interview plan from the hiring manager's own words, a write-up of every
> interview, and finalists compared in one question.

> [card] [QA engineers](https://docs.jinn.so/for/qa-engineers.md)
>
> Know what changed in every meeting, even the ones you missed, and what to retest because of
> it.

> [card] [Developers](https://docs.jinn.so/for/developers.md)
>
> Ask a skipped call what was decided, find out why the code was written that way, and hand
> the spec to your coding assistant as Markdown.

## What each role gets from a meeting

The same recording gives each person something different, and nobody writes notes by hand.

| Role | What Jinn hands you after a call |
| - | - |
| Founder | The decisions from a meeting you didn't go to |
| Manager | The blockers, who owns what, and who's waiting on whom |
| Support | What the customer tried, what you promised, and a follow-up to send |
| Sales | What the customer needs, what they objected to, and the next step |
| Recruiter | The candidate's strengths and concerns, read the same way for everyone |
| QA engineer | What changed and what needs testing again |
| Developer | What was decided about your part, and by whom |

Every write-up stays on the recording, so the next person who opens it reads it too.

## When your role isn't listed

These pages cover the jobs most teams start with. Jinn has more ready-made agents — for product
managers, analysts, researchers and marketers among others. Find the one closest to your job
under **Agents** in the left sidebar, and if it isn't there, ask your workspace admin to add it:
only admins can add agents. See [adding an agent](https://docs.jinn.so/agents/add-an-agent.md).

## Where to go next

> [card] [Customer feedback](https://docs.jinn.so/feedback/customer-feedback)
>
> Coming soon: bugs, ideas and questions from the people using your site, filed in the project they belong to.

> [card] [Jinn for founders](https://docs.jinn.so/for/founders.md)
>
> One workspace instead of five tools, and every meeting without going.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.