Docs

Documentation

Getting started with Jaha

From “Get Started” to Jaha answering out loud in your first meeting: one admin consent, no installs on anyone’s machine, and about ten minutes.

What you need

A Microsoft 365 organisation, and one person with admin rights in it. That is the entire list. Nobody on your team installs anything, changes how they schedule meetings, or learns a new tool — Jaha is a tenant-wide Teams app that your admin approves once.

Sign-in stays entirely with Microsoft. Jaha never sees a password; sessions are the standard corporate SSO your organisation already trusts.

Your first meeting

Invite Jaha to any Teams meeting — or @mention it in a meeting chat — and it joins, transcribes live with speaker attribution, and listens for its name. Say “Hey Jaha” followed by a question and it answers out loud, in the call, grounded in the conversation and whatever sources you have connected.

When the call ends, the recap is ready in under a minute: summary, decisions, and action items with owners. Everything is searchable from the dashboard immediately.

Scheduled auto-join (optional)

If you want Jaha to create calendar meetings and join them automatically the moment they start, your admin additionally consents to calendar and online-meeting permissions and runs one PowerShell command we provide in the in-app guide. Everything else in the product works without this step.

Bringing in your team

Connect your directory and Jaha syncs it on its own: the org map fills in, joiners appear, leavers’ seats free themselves, and re-orgs simply flow through. Everyone in your directory is recognised by name for free — you only assign paid seats to the people whose meetings Jaha works.

Roles — manager, member, viewer — decide who can change rules, send output to connectors, and manage billing. Guests in your meetings are never charged and never seated.

Did this page help?