Granola system requirements for work laptops

What does Granola need on a work laptop?

Granola needs more than an available download. Confirm the operating system, app approval, audio capture, authentication, network access and update policy together. The following table is a pre-adoption checklist; it is not a list of devices we have independently tested.

A sensible decision is conditional: “approved for this laptop, meeting application and network,” rather than “approved for every Windows computer.” Keep that configuration with the pilot result so another team can see what was actually checked.

Official reference: Granola desktop setup guide.

Does Granola require administrator rights?

There is no reliable universal yes-or-no answer for a managed laptop. Installation policy, access to audio and permission to replace the app during updates are separate checks. Granola describes its default Windows installer as per-user; that does not override a company policy blocking software installation.

Ask IT three specific questions: may this user install Granola, may the app access the necessary audio devices, and may the installed copy update itself? A “yes” to one should not be recorded as approval for all three.

Official reference: Granola managed installations and updates.

Official reference: Granola transcription and web-interface limits.

Which audio permissions must IT allow?

On Mac, check Microphone and Screen & System Audio Recording. On Windows, check microphone access and the setting that lets desktop apps access the microphone. Granola’s troubleshooting guide identifies these settings as relevant to transcription.

During the pilot, open the transcript and verify a sentence spoken by you and one spoken by the remote participant. Hearing the call through your headset does not, by itself, prove that Granola received the remote audio. If a policy prevents changing the required setting, record the dependency for IT rather than assuming a different meeting application will solve it.

Official reference: Granola audio permissions and virtual-desktop limits.

Does Granola work with Teams in Citrix or Azure Virtual Desktop?

Granola does not officially support Citrix, Azure Virtual Desktop or other virtual-machine/VDI environments. Its documentation warns that Teams desktop in these environments does not pass other participants’ audio to Granola, even when your own microphone appears in the transcript.

Granola recommends running the app on your local machine. If that is not possible, the documentation suggests joining Teams in a web browser instead of the Teams desktop app. Treat that suggestion as something to evaluate with IT, not as a promise that your virtual-desktop configuration is supported.

Official reference: Granola audio permissions and virtual-desktop limits.

Before deciding, write down where each app runs. “Windows with Teams” could mean both apps on a local laptop, both inside a remote session, or one in each location. Those are different audio paths. A pilot result from one cannot validate the others.

Can Granola transcribe in a browser without installing an app?

No: Granola’s own web interface is for viewing and editing existing notes, not capturing or transcribing meetings. Meeting transcription requires a Granola desktop or mobile app.

A meeting running in a browser is a different matter: a Granola desktop app can capture computer audio. That does not turn Granola itself into a browser recorder. If your work laptop prohibits all app installation, opening the Granola web interface does not remove that capture requirement.

Official reference: Granola transcription and web-interface limits.

Before an adoption decision, distinguish three permissions: opening a website, installing an application, and allowing that application to capture audio. A company may permit the first while restricting the other two.

Can Granola work behind a VPN, proxy or Zscaler?

A company VPN or filtering product is not automatically incompatible with Granola. The network must allow Granola’s required connections without disrupting transcription or streamed responses. A website loading successfully is not sufficient evidence that those connections work.

The official network guide calls for secure WebSocket connections over outbound TCP 443, including upgrades and long-lived connections. It also specifies that stream.api.granola.ai must deliver response bodies incrementally, without response buffering. TLS inspection can remain enabled for ordinary HTTPS traffic under the documented conditions; an exception may be needed where a product cannot inspect the streaming host without buffering.

Official reference: Granola network requirements and allowlist.

For an IT approval request, use the current official allowlist rather than a copied list of domains that could become stale. Ask IT to check the services used by your proposed workflow: login, transcription, streamed notes or chat, and downloads/updates.

Evaluate the network that employees will actually use, including the required VPN and endpoint filtering. A pass on home Wi-Fi does not establish a pass on the company setup. Keep security controls enabled during the intended acceptance test; any diagnostic change should be agreed with IT.

What should IT check for a managed Granola installation?

Decide how Granola will receive updates before rolling it out. Granola says automatic updates depend on a writable installation location and access to its download services. If device policy blocks self-updates, IT can manage updates using the documented installer and version endpoints.

The managed-installation guide does not provide a complete step-by-step deployment procedure for tools such as Jamf, Kandji, Workspace ONE, FleetDM or WinGet. Do not present the existence of an installer as certification for every management platform.

Official reference: Granola managed installations and updates.

For a small pilot, an approved installation method and a named update owner may be enough. For a wider rollout, IT should also decide how to identify outdated copies, apply a replacement package and confirm that meeting capture still works afterwards. Those are operational decisions for the organization, not capabilities we have independently validated.

How should you test Granola before adopting it at work?

Run one agreed acceptance test on the real laptop, meeting app, headset and work network. The checklist below is our proposed evaluation method. It is not a claimed hands-on test or a vendor guarantee.

1. Describe the setup. Record OS version, whether the computer is local or virtual, meeting app, headset and network controls. Note who approved the pilot.
2. Confirm installation and permissions. Use the approved account and installation process. Record any blocked permission separately.
3. Check both voices. Hold a short, non-sensitive call with a colleague who knows it is being transcribed. Each person should say a different, recognizable sentence.
4. Check the result. Confirm that both sentences appear and that generated notes reflect the conversation. Correct content errors before sharing anything.
5. Check the meeting boundary. End the note deliberately and begin a separate note for another short call. Confirm that the two conversations remain separate.
6. Check maintenance. Have IT confirm the update path, responsible owner and required network access. Record the tested app version.

Decide from the evidence: proceed with the tested configuration, resolve a documented dependency, or keep the setup unapproved. Avoid a vague “works well” result: it gives the next user no way to know whether their configuration is equivalent.

What should you send IT before installing Granola?

Send a specific configuration and a request for approval. This template keeps installation, capture and maintenance separate, so IT can identify the actual dependency.

Include the exact official references below with your request. Avoid presenting the pilot as permission to use the tool on every meeting or every device.

Granola work-laptop questions

Can I use Granola if my company blocks software installation?

Not for meeting capture through the Granola web interface: it only displays and edits existing notes. Ask IT whether an approved desktop installation is available before selecting Granola for that laptop.

Does a Granola per-user installer bypass company restrictions?

No. A per-user installation describes the installation scope; it does not override company application-control policies or approve the use of meeting data.

Does supporting Teams mean Granola supports Teams inside Citrix?

No. Granola explicitly says virtual desktops, including Citrix and Azure Virtual Desktop, are not officially supported. Evaluate the exact environment instead of extending a general Teams compatibility claim.

Is reaching Granola’s website enough to validate a company network?

No. The proposed workflow also needs the required transcription and streaming connections, account access and update access. Check the official network guide and test on the normal work network.

Can IT manage updates if Granola cannot update itself?

Granola documents installer and version endpoints for manual packaging workflows when policies prevent self-updates. IT still needs to validate and maintain its chosen deployment process.

Sources and verification

This is a documentation-based technical guide checked on October 10, 2026. We have not independently tested the listed corporate networks, management platforms or virtual desktops. The checklist and IT-request template are our practical synthesis; compatibility statements are tied to the references below.

• Granola desktop setup guide
• Granola audio permissions and virtual-desktop limits
• Granola transcription and web-interface limits
• Granola network requirements and allowlist
• Granola managed installations and updates

If documentation gives a broad platform claim and a specific environment limitation, use the specific limitation for that environment. Where a requirement is not established by the cited documentation, ask Granola or IT rather than treating an assumption as supported.