Integrations and permissions

With native recording, Teams records the meeting itself and no notetaker joins. Setup has three parts: Teams settings (a Teams admin allows cloud recording, transcription and Microsoft Graph access to transcripts), a one-time admin consent, and each organizer signing in to Zime once.

• The two organization-wide permissions are read-only. Zime uses them only to receive Microsoft's notices that a recording or transcript is ready. The notice carries identifiers, not content.
• Zime makes one change, acting as the organizer: about 10 minutes before a meeting your recording settings select, it turns on the meeting's Record and transcribe automatically option. It does not create, move or cancel meetings, edit attendees or calendars, post messages, or touch files.
• To receive the notices, Zime creates and renews two Microsoft Graph notification subscriptions in your tenant.
• Zime reads meetings, recordings and transcripts only for organizers who have signed in to Zime. To limit who can sign in, set Assignment required on the Zime native recording app in Microsoft Entra ID and assign only the people or group you choose. Assigning a group needs Microsoft Entra ID P1 or P2.
• Native recording is used only when the organizer belongs to your company's Zime workspace. Otherwise the Zime notetaker joins instead, if your workspace allows it.
• One region or team only: it goes by who sends the invite, not who attends. Have only the organizers in that region or team enable native recording; everyone else keeps the notetaker.
• For a recurring meeting the option applies to the whole series and stays on until the organizer turns it off in the meeting's Teams options.
• It does not use Outlook mail, contacts, OneDrive, SharePoint, Teams chats or channel messages.

See Teams native recording guide and Microsoft 365 guide for IT.

A Teams admin uploads the app and can make it available to selected people or groups only. The app requests no Microsoft Graph permissions. It uses the standard capabilities Teams gives an app: receive the messages people send it and reply, read the basic profile of the person using it, and, in teams and chats it is added to, read the name, channel list and member list.

Optional: thread reading lets Zime answer with the thread as context. It needs a Global Administrator to approve ChannelMessage.Read.All, a read-only permission. Zime reads only the thread in which someone mentions it.

See Zime app for Teams guide.

Calendars.Read (read-only), User.Read and offline_access. Sign in with Microsoft also requests openid, email, profile and User.ReadBasic.All; Zime reads only the profile of the person signing in.

Zime does not connect to mailboxes.

See Outlook calendar guide.

Read-only access to calendar events, plus sign-in. Zime requests no Gmail, contacts or Drive access.

See Google Calendar guide.

The notetaker joins as a visible participant under your notetaker name and records what any participant can see and hear. On Zoom it asks the host for permission to record. In a waiting room or lobby it must be admitted by a person, and it leaves if it is not admitted. Your recording settings decide which meetings it joins.

See Notetaker guide and Recording security.

The Zime app for Zoom is approved in your Zoom account. It has account level permissions to read users and their plan, read meetings, update meeting and recording settings, and read cloud recordings. About 10 minutes before a selected meeting, Zime sets the meeting to record to the Zoom cloud. Removing the app in Zoom makes Zime delete its stored Zoom credentials.

See Zoom app installation guide and Zoom native recording guide.

Salesforce: Zime reads opportunities, accounts, contacts, leads, users, tasks, logged emails and stages. HubSpot: Zime reads deals, contacts, companies, owners, users, leads and logged emails.

Zime writes to your CRM only where CRM updates are set up for your workspace, and only the fields and records configured for it.

Email analysis reads the emails logged in your CRM.

Disconnecting the CRM in Zime revokes Zime's access token.

See Salesforce guide, HubSpot guide and CRM updates guide.

Needed only where your Conditional Access requires an app protection policy. Your Entra and Intune admin grants admin consent to the Zime Mobile enterprise app (application ID e9b17ec8-756d-4c74-9ba9-2b761c3b42cb; permissions: User.Read for sign-in and the Intune app protection permission), adds Zime Mobile to an Intune App Protection Policy (Android package com.zimemobile, iOS bundle ai.zime.app), and confirms the users hold an Intune licence. Devices need Microsoft Company Portal on Android or Microsoft Authenticator on iOS.

See Zime Mobile with Intune guide.

The Zime connector signs in as the user with OAuth. There is no API key, and the assistant sees only what that user can see in Zime.

For skills shared across your company, Zime hosts a private repository and gives your Claude owner's GitHub account read access. You need that one GitHub account, not a repository of your own.

See Zime connector for AI assistants, Zime plugin and Zime in Claude guide.

The API key is read-only and scoped to your company. A separate ingest key can only send calls to Zime; it cannot read.

See API reference and Call Ingest API.