Granola Prod Checklist

Granola Production Checklist

Overview

Comprehensive pre-launch checklist for deploying Granola to a team or organization. Covers plan selection, security hardening, integration setup, pilot program, and go-live execution.

Prerequisites

• Budget approved for Granola licenses
• Team size and meeting volume estimated
• IT/security review completed or in progress
• Admin access to Granola workspace

Instructions

Phase 1 — Plan & License

• Select plan: Business ($14/user/mo) or Enterprise ($35+/user/mo)
• Seat count: Purchase seats for all target users
• Billing: Annual billing for 10-15% savings, or monthly for flexibility
• Contract: Enterprise agreement signed (if applicable)
• SOC 2 report: Requested and reviewed (available on request from Granola)

Phase 2 — Security Configuration

• SSO enabled: Okta, Azure AD, or Google Workspace (Enterprise)
• SCIM provisioning: Auto-provision users from IdP groups (Enterprise)
• AI training opt-out: Enabled org-wide (Enterprise: enforced by default)
• Sharing defaults: Set to Private, external sharing disabled or admin-approved
• Data retention: Configured per data type (notes: 1-2yr, transcripts: 90d)
• DPA signed: Data Processing Agreement for GDPR compliance
• Session timeout: Configured for security policy (Enterprise)

Phase 3 — Integration Setup

Phase 4 — Workspace Configuration

• Workspaces created: Per department/team (Engineering, Sales, Leadership, etc.)
• Folders created: Per meeting type within each workspace
• Templates configured: Default templates per folder/meeting type
• Sharing rules: Per-folder auto-post to Slack channels
• User roles assigned: Admin, Member, Viewer per workspace
• Custom recipes created: Team-specific Granola Chat recipes

Phase 5 — Pilot Program (2 Weeks)

1. Select 5-10 pilot users across different meeting types
2. Define success metrics:

1. Collect daily feedback for the first 3 days, then weekly
2. Fix issues immediately — common pilot issues:
   • Audio permission not granted (macOS Screen & System Audio)
   • Calendar not connected to the right account
   • Templates not matching meeting types
   • Users forgetting to type notes (Enhance is better with typed context)

Phase 6 — Go-Live

Launch day checklist:

• Welcome email sent with setup instructions and support contact
• Slack channel created: #granola-support
• Quick-start guide shared (link to granola-install-auth + granola-hello-world)
• Calendar consent notice template distributed
• User access enabled (SSO/SCIM auto-provision or manual invite)
• IT support team briefed on common troubleshooting steps

First week monitoring:

• Daily adoption check: % of users who captured a meeting
• Support ticket volume and resolution time
• Integration health: Slack/Notion/CRM syncs working
• User feedback collection via survey or Slack poll

Phase 7 — Post-Launch (Weeks 2-4)

• Address low-adoption users with 1:1 support
• Publish internal "tips & tricks" based on power user patterns
• Review and refine templates based on team feedback
• Set up recurring reporting (weekly adoption metrics to leadership)
• Schedule first quarterly access review

Output

• All security controls configured and verified
• Integrations connected, tested, and documented
• Pilot completed with metrics meeting targets
• Full team onboarded and actively capturing meetings
• Support processes established with documented escalation path

Error Handling

Examples

revision=r44; canary=synthetic-calendar; health=pass; delivery=pass; retention=none; destination=approved; outcome=promote; rollback=r43 is a complete canary decision.

Resources

• Setup Guide
• Enterprise API
• Security Standards
• Granola Updates

Next Steps

Proceed to granola-upgrade-migration for version upgrade and plan migration guidance.