Client Onboarding — Requirements Checklist

Established by Vishal Joshi during preparation for Client #2.

Must-Have Requirements

• Slack App Store listing — Boo's Slack app must be in the Slack App Directory
• Artifacts with security — Basic Password, OTP, and SSO protection for generated artifacts
• Generalized WarmUp / Bundled Skills — Default skill set for new deployments (specific list TBD)
• Signup workflow improvements — Smooth flow that distinguishes new signups from invited members
• Onboarding smoothness — Clean experience when Boo first starts in a workspace
• Include/Exclude Channel settings — Ability to control which channels Boo can access
• Billing working — Invoicing must work from day one

Known Bugs to Fix Before Onboarding

Member Invite Creates New Deployment (BOO-245)

When an invited member accepts a join link, the system put them through new-deployment onboarding instead of adding them to the existing org. Root cause: every signup was designed to create Boo for themselves, with no distinction for invited members.

Fix: Skip the deployment creation flow for people invited to an existing org.

Google OAuth Not in Production

Google OAuth only existed in a test GCP project. Gmail and Google Calendar showed connectable: false because no OAuth app was registered in production.

Fix: BOO-245 (Urgent, assigned to Arun) — Set up Google OAuth app on production GCP project.

Slack Marketplace Submission

The Slack marketplace submission requires detailed privacy, data governance, and security responses. Key points for the submission:

• Always list all three LLM providers (Anthropic, OpenAI, Google Gemini)
• Reference boolab.ai/legal/privacy for data retention
• SSO support includes Okta, Google Workspace, Microsoft Entra ID, and any SAML 2.0 IDP
• Test account instructions include: channel summarization, heartbeat creation, artifact building, and web research