Support

Contact info@minut.ing for account access, privacy requests, or security concerns. Minuting is operated by LGTM HK Limited.

Sign in & reconnect

Start again from Sign in, using the same browser throughout and allowing essential cookies. If Google denies access, check the message it provides. Your organization may require administrator approval. If you still cannot sign in, contact us rather than repeatedly retrying or changing your account’s security settings.

Signing in shares your Google account identifier, name and email—not access to Meet, Calendar or Drive. Your meeting source is a separate connection and can use a different Google account.

If your source asks to reconnect, open Connections and choose Reconnect Google Meet. Routine reconnect and disconnect controls are in Manage source. Reconnect the same source account; disconnect first to change accounts. Google authorization can expire or be revoked. Renewing notifications does not restore authorization. If Google reports that notifications already exist, use Check status. Minuting checks for a matching subscription authorized by the same Google account and app and reuses it when safe. You do not need to reconnect or remove notifications yourself. If the conflict remains, or setup confirmation was lost, contact support; Minuting will not guess ownership or create duplicates to bypass uncertainty.

Find a missing meeting

In Connections, use Check status to check your Google Meet source. The source account must organize the meeting, and Google must have generated a transcript. An eligible Workspace account and actual transcription are required; attending a call or adding it to Calendar is not enough.

Open Find missing meetings and use Rescan meetings to queue a search of the last 28 days, then Refresh later to see saved progress. Google’s transcript retention and incomplete transcripts can limit recovery. Find captured records in your Library. Search coverage and the last attempt are in Manage source. An incomplete search does not advance complete coverage. Searches can be requested once every ten minutes.

Upcoming & link settings

Upcoming is an optional, read-only view of organizer-owned Meet events on your primary calendar. Calendar access does not itself capture a transcript. Open Calendar details for the last complete search, saved window, Reconnect Calendar and Rescan upcoming meetings. Rescan queues a 90-day search; use Refresh later for the saved result. A failed or incomplete search keeps the previous complete agenda, not current coverage. Cancelled events cannot be joined.

Follow an occurrence’s Link settings to its shared automatic-transcription controls below the agenda. Google grants broader settings permission, but Minuting changes only transcription on explicit request. Check status asks Google; Unknown does not mean Off. Failed checks show Last check attempt, not a successful check. Use Transcription access to reconnect this permission.

Enabling affects every future call on that link, including calls beyond the saved window. It does not promise to start transcription in an active call, change recording or smart notes, or override Workspace eligibility. Minuting has no disable control; manage other settings in Google Meet. Transcript capture works without these optional permissions.

Refresh & check status

Refresh reads saved application state. Check status contacts Google; Check Notion access contacts Notion. Refresh Notion reads saved destination state without contacting Notion.

Last refreshed is when the page received saved state, not a successful Google check. After a failed source check, Last check attempt replaces Last checked; an older saved active notification state does not prove that capture still works.

Pages do not update in the background. Server maintenance runs every ten minutes, and recovery can take several passes—even for a small meeting. Check again with Refresh when you need a new observation. Repeatedly pressing Retry does not make it run sooner. Offline actions fail immediately and are never queued for reconnection.

What records are supported?

Minuting uses Google-generated Meet transcripts, not audio recordings or uploaded files. AI processing supports records explicitly marked as English that fit the whole-record limit. Other or unknown languages are unsupported; nothing is translated or shortened to fit.

The limit depends on the complete text, speaker names and number of speech turns, not a fixed meeting duration. Oversized or incomplete sources cannot be imported as a partial record. If an original was imported but cannot be refined, it remains readable and downloadable with Download original (JSON) in the meeting’s Original view. Retrying or reprocessing cannot bypass these limits.

Retry or reprocess a record

Open the record in your Library. Use the available stage-specific Retry action after resolving its reported problem. Retry keeps the same version and plan. In Record details, Reprocess transcript deliberately creates a new transcript version and new minutes, with more AI processing. Earlier versions stay available; enabled publication can create a separate Notion page for the new result.

Minutes can fail independently of a successful transcript, and publication can fail without losing either. Review AI wording and citations against the preserved speech when accuracy matters. If retries are exhausted or a record remains stuck, contact us rather than deleting it to try again.

Minutes and the complete transcript share one page. Citations open and focus the matching refined turn, including from Original or Compare. Use Record details → Versions for earlier results, hashes and processing history. Show speech evidence reveals the original participant and entry references without changing the text.

Publish to Notion

Notion is optional. In Connections, open Destinations → Connect Notion. Choose an internal connection token or a personal access token, then connect. Use Find parent pages and Save parent page as separate actions. A personal token acts as you and can access more than the selected parent. Readable pages do not prove Insert content permission; setup creates no test page.

Internal connections need Read content and Insert content, and must be added to the parent page in Notion. Personal tokens need Notion API access and use your own page permissions without bot sharing. Availability depends on your Notion workspace’s policy. Track token expiration in Notion; Minuting cannot read it. If no pages are found, check sharing or personal access, wait for Notion search to update, then find pages again. A denied search is not an empty result.

Enable future publications only if you want new completed records sent to Notion. Setup does not backfill your history. For an earlier completed record, use Publish in Notion in the record header. The confirmation identifies the parent and exact versions being sent. Each selected transcript and minutes pair goes together on one new page, without replacing an earlier page.

When publication needs attention

Open Connections → Manage destination for Check Notion access, parent changes, token replacement and disconnect. Restore the token’s access and Insert content permission, then explicitly enable future publications if needed. Replacing a personal access token disables routing and clears discovered pages. Replacing an internal token keeps the same connection, workspace and publication setting only if the parent is still accessible. Neither resumes stopped publications. Disconnect before switching authentication methods. In the meeting, Retry publication verifies the saved page and any uncertain writes before continuing.

Pending or partial publication is not delivery. Only verified complete content gets Open in Notion; a partial-page link is for inspection. If managed content was edited, restore the original content or contact support. For conflicting or ambiguous pages, ask for review. Minuting will not overwrite your edits, blindly append content or create a duplicate page to bypass uncertainty.

Delete data or disconnect

Delete meeting is under Record details in the record; Delete account is in Account in the page header. Confirm only when you intend to permanently remove that data. Access ends immediately, but private storage cleanup starts after a one-day safety period and may take multiple maintenance passes. Disconnecting Google keeps your login and captured meetings. Disconnecting Notion disables future publication but does not revoke your token at Notion. Existing Notion pages, Google originals and downloaded copies remain. See the Privacy notice for retention and third-party copies.

Report a problem safely

Include the action, time with time zone, and visible error message. Do not include provider tokens, authorization codes, browser cookies, or private meeting content. Never post these publicly. The Service status page checks the application connection, not Google capture, AI quality, or Notion delivery.