---
name: granola-install-auth
description: 'Install and configure Granola AI meeting notes with calendar and audio permissions.

  Use when setting up Granola for the first time, connecting Google/Outlook calendars,

  granting macOS Screen Recording permission, or configuring Windows audio capture.

  Trigger: "install granola", "setup granola", "granola calendar", "granola permissions".'
allowed-tools: Read, Write, Edit, Bash(brew:*), Bash(open:*), Bash(pgrep:*), Bash(defaults:*), Bash(ls:*)
version: 1.13.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
  - saas
  - granola
  - granola-install
compatibility: Designed for Claude Code
title: granola-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/granola-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/granola-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/granola-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/granola-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/granola-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/granola-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/granola-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Granola Install & Auth

## Overview

Install Granola, the AI notepad that captures meeting audio directly from your device (no bot joins the call), transcribes with GPT-4o/Claude, and produces structured notes with action items. Supports Zoom, Google Meet, Teams, Slack Huddles, and WebEx.

## Prerequisites

- macOS 12+ or Windows 10+ (iOS/Android for mobile)
- Google Calendar or Microsoft Outlook account
- Active internet connection for initial auth

## Instructions

### Step 1 — Download and Install

```bash
# macOS via Homebrew
brew install --cask granola

# Or download directly
open "https://www.granola.ai/download"
```

Windows: download the installer from `granola.ai/download` and run the `.exe`.

### Step 2 — Create Account and Authenticate

1. Launch Granola
2. Click **Sign up** — authenticate with Google or Microsoft
3. Granola uses WorkOS for SSO; enterprise users may see their IdP login (Okta, Azure AD)

### Step 3 — Grant System Permissions

**macOS (critical — both required):**

```
System Settings > Privacy & Security > Microphone
  → Enable Granola

System Settings > Privacy & Security > Screen & System Audio Recording
  → Enable Granola
```

The Screen Recording permission is required because macOS bundles system audio capture under that category — Granola does **not** record your screen.

**Windows:**
Microphone permissions are granted automatically. Confirm at:

```
Settings > Privacy & Security > Microphone → Granola enabled
```

### Step 4 — Connect Calendar

1. Granola Settings (avatar bottom-left) > **Calendar**
2. Connect Google Calendar or Microsoft Outlook
3. Select which calendars to sync (personal, work, shared)
4. Granola detects meetings from synced calendars with video/conference links

### Step 5 — Verify Audio Capture

```bash
# macOS — confirm Granola is running
pgrep -l Granola

# Check installed version
defaults read /Applications/Granola.app/Contents/Info.plist CFBundleShortVersionString 2>/dev/null || echo "Check Granola > About"
```

Join or start any meeting (Zoom, Meet, Teams). Granola shows a floating notepad when it detects a calendar event with a conferencing link. Verify the live transcription indicator appears.

### Step 6 — Configure Preferences

| Setting | Location | Recommended |
|---------|----------|-------------|
| Auto-start with calendar | Preferences > General | On |
| Default template | Preferences > Templates | Match your meeting type |
| AI model | Uses GPT-4o/Claude | No configuration needed |
| Auto-update | Preferences > General | On |

## Output

- Granola installed and running on login
- Calendar connected with meeting auto-detection
- System audio + microphone permissions granted
- Live transcription verified on a test call

## Error Handling

| Error | Cause | Fix |
|-------|-------|-----|
| No audio captured | Missing Screen & System Audio permission (macOS) | System Settings > Privacy & Security > Screen & System Audio Recording > enable Granola, then restart |
| Calendar not syncing | OAuth token expired or wrong account | Disconnect calendar in Settings, re-authenticate |
| App won't launch | macOS Gatekeeper block | Right-click Granola.app > Open, or `xattr -cr /Applications/Granola.app` |
| Meeting not detected | Event has no video link | Add a Zoom/Meet/Teams link to the calendar event |
| Bluetooth audio drops | BT device causes transcription stops | Switch to built-in mic or wired headset |

## Granola Architecture (How It Works)

```
Your Device Audio ──→ Granola Desktop App ──→ Granola Cloud (transcription)
                           │                        │
                     Local notepad            GPT-4o / Claude
                     (your typed notes)       (enhance + summarize)
                           │                        │
                           └────── Merged Output ───┘
                                   │
                          Structured meeting notes
                          with action items
```

- Audio is transcribed server-side; Granola does **not** store raw audio after processing
- Your typed notes are merged with the transcript for context-aware summaries
- No bot joins your meeting — capture happens via system audio

## Examples

`env=sandbox; secret_ref=granola-client-v4; scope=meeting-read; destination=approved; synthetic_probe=200; rotation_owner=platform-ops` proves setup without exposing a credential.

## Resources

- [Download Granola](https://www.granola.ai/download)
- [Setup Guide](https://docs.granola.ai/help-center/getting-started/setting-up-granola-for-the-first-time)
- [Transcription Troubleshooting](https://docs.granola.ai/help-center/troubleshooting/transcription-issues)
- [Security Standards](https://docs.granola.ai/help-center/consent-security-privacy/our-security-standards)

## Next Steps

After installation, proceed to `granola-hello-world` for your first meeting capture.
