Jinn for managers

This page sets Jinn up for running a team: you record the meeting once and stop rewriting your notes for three different people, and you find out who owns what without pinging anyone. Once it’s set up, you get:

• Notes for the whole team from one recording — a summary, the blockers, who took what on (step 3)
• Owners and deadlines in one question, across one project or all of yours, with a link to where each was agreed (step 4)
• The standup and the weekly brief written from what was said, not from memory (step 5)

Steps 1–2 you do once. Steps 3–6 are what you do every week.

1. Get into your team’s projects

Everything below happens inside projects: usually one per team, product area or client. Ask whoever has Full access on each to add you with Can edit access rights. If you’re starting a new one, click New project in the sidebar, name it, and choose Private or Open.

2. Set up recording

Meetings are recorded from the Jinn desktop app. No bot joins the call: the audio comes from your own machine, so it works with whatever you call from.

1. Download the app and install it.
2. Open Settings → Meetings and turn on Enable meeting notes.
3. Under When meeting starts, choose Show a recording prompt. Jinn notices a meeting and asks before it records.

See recording a meeting for the permissions your computer asks for.

3. Get notes for the team after a meeting

1. When the meeting starts, click Start on the recording bar.
2. Under Select project, pick the team’s project.
3. When it ends, click Stop & Generate. Jinn writes the transcript and opens the recording.

Every recorded meeting gets a write-up from AI agents — each one reads the meeting through a particular role. One of them, Default, is built into every project and writes a summary and the action items on its own, without anyone asking. For a manager’s reading, add one more, depending on what you run:

4. On the recording, click Add agent at the end of the row of agents.
5. Pick the agent:
   • Team Coordinator — for the people and the delivery: what everyone is doing, what’s blocked and what needs a decision.
   • Product Manager — for the product: priorities, scope and what users get. It flags decisions nobody made out loud.
   You can add both. Each writes its own write-up, next to Default’s.

Each write-up stays on the recording, so the developer who missed the call opens it and reads the same thing you did. If an owner is wrong, fix it in place — what you write is what everyone reads from then on. If Team Coordinator or Product Manager isn’t in the list, it isn’t on this project yet. Ask the person with Full access on the project to add it; if the workspace doesn’t have it at all, a workspace admin creates it first.

4. Ask who owns what

Instead of five messages to find out who owns the launch:

1. Choose where to ask:
   • One project — open it and click Chat
   • The whole workspace — click AI in the left sidebar
2. Ask in plain words.
   For example: Who owns the checkout launch, what did they commit to, and what’s blocking it?
3. Before you hold anyone to a date, open the link under the answer and check where it was agreed.

See asking a question.

5. Write the weekly brief

Recurring write-ups don’t need a prompt from scratch. Jinn ships built-in skills for them.

1. Open the project and click Chat.
2. Type / in the message box and pick Weekly team brief, Standup summary or Meeting follow-up.
3. Say what the brief is for, and send.

See skills.

6. Check what’s waiting on you

• Inbox, in the left sidebar, collects what needs a person: a recording that still needs a project, an agent that failed to write, a doc with no project. See checking a recording.
• Action items go into your tracker by copy and paste: Copy above a write-up takes the whole of it. There’s no automatic hand-off to a tracker.

Where to go next