Everything people ask before they connect.

A Microsoft account tied to a Teams calendar. Sign in, run the first sync, and your last 120 days of meetings appear.

Free access is currently closed while we work directly with early customers. Existing development and evaluation workspaces keep their current access.

Capture pauses for the rest of the month and the meetings you already have stay searchable. Calendar events still appear so you can see what was missed, and upgrading picks capture back up immediately.

Not to try it on your own calendar. Some tenants require admin approval before a third-party app can read transcripts; if yours does, htgr shows a consent flow your Global Admin can complete once for the whole organisation.

Usually a few minutes. Calendar events land first, then transcripts are processed in the background — the app shows coverage as it climbs.

Yes. A personal workspace can be upgraded to an organisation, and members you invite keep their own to-do list inside the shared record.

No. htgr reads the transcripts Teams already produces through the Microsoft Graph API. Nothing joins the call and no participant sees an extra attendee.

A summary lives and dies with one meeting. htgr keeps a durable, searchable record across every meeting in a project, so a decision from six months ago is still retrievable with its context.

The first sync pulls the last 120 days, which is the window Teams keeps transcripts for. From then on htgr keeps its own record, so your history grows past that limit.

A project groups meetings that belong to the same body of work. Attach a meeting to one, or set a rule so a recurring series always lands there. Everything that meeting produced — summary, decisions, open actions, indexed passages — joins the project record, and a running timeline is assembled as new meetings arrive.

Yes. Scoping a question to a project restricts retrieval to that project's meetings, so the answer is drawn from the relevant history rather than everything in the workspace. Unscoped search still covers the whole record.

It still appears with its calendar details — subject, attendees, recurrence — marked as not processed. Nothing is fabricated from an absent transcript.

They are drawn strictly from what was said, with a citation back to the moment. Where the conversation left an owner or a date implicit, the action item stays unassigned rather than guessing.

Only members of your workspace. The organisation boundary is enforced by row-level security in the database, so it holds even if application code is wrong.

No. Passages are sent to the model provider only to embed and answer your own questions, and only when AI search is enabled.

Yes. Capture, notes and keyword search run entirely on our infrastructure. Generated answers are only available on paid plans and only when requested.

Read-only access to calendar events and meeting transcripts. We will send the full scope list with the reason for each on request.

Disconnect from your connections page, or revoke the application in Entra ID. Syncing stops immediately and stored data can be deleted on request.

Pro, Business, and Enterprise include asking questions across your meeting history with cited answers. Free is not currently open to new workspaces.

Both include AI search, unlimited history, and owner-managed spend caps. Business adds a larger seat allowance. Enterprise adds SSO, SCIM provisioning, advanced controls, and tailored support.

The pricing page shows monthly and annual preview figures. Checkout, invoices and renewal management are not connected yet.

By active workspace members and live invitations. Owners can see seats used and available from Settings → Plan & usage.

Capture keeps running and nothing is lost. The assistant pauses until the cap resets or an owner raises it, then queued meetings are processed automatically.

Not yet. The current plan controls are internal and owner-managed; payment-provider checkout and invoicing are a later phase.