RecalCore Concepts
Understand organizations, users, and events—the building blocks of Recal's data model.
The Basics
Organizations — Group users together (optional for B2C, essential for B2B)
Users — Connect to calendar providers (Google, Outlook). Support custom IDs.
Events — Calendar entries synced across providers
OAuth Connections — Secure calendar provider authentication tokens
Data Model
Recal's data model is built around four core entities that work together:
- Users connect to calendar providers and can belong to multiple organizations
- Organizations group users together for B2B multi-tenancy
- Events are calendar entries synced across all providers in a unified format
- OAuth Connections securely link users to their Google/Microsoft calendars
For detailed TypeScript type definitions, see the SDK Types Reference.
Architecture Patterns
B2B Multi-Tenant
Create organizations for each customer. Isolates data and enables per-tenant analytics.
Example: Salon booking platform
B2C Direct Users
Add users directly without organizations. Simpler for consumer apps.
Example: Personal calendar app
When to Use What
| Pattern | Use Case | Benefits |
|---|---|---|
| Organizations | B2B SaaS, team scheduling | Data isolation, per-tenant analytics |
| Direct Users | B2C apps, personal tools | Simpler setup, faster onboarding |
| Hybrid | Both patterns combined | Flexibility for different customer types |
Key Features
Custom IDs — Map to your database IDs directly (e.g., ${yourDbId} or user_clerk-id)
Multi-Org Users — One person can belong to multiple organizations
Cross-Calendar Sync — Events stay in sync across Google, Outlook, etc.
Shared Availability — Find free slots across organization members