Firm lane
Calendar connection (Google, Microsoft)
Kind: A connection to an outside provider's service.
Availability
Owner-gatedWaits on the platform's owner to register the calendar app; the read-only deadline feed works without it.
- Door
/api/calendar/connect- Unlocks with
- The firm's own account at the provider, once the platform's owner registers the app.
Every status follows one rule from this deployment's own configuration: a capability is marked shipped only when everything it needs is in place.
What it does
Writes a matter's dated steps as events to the firm's connected Google or Microsoft calendar.
Keep in mind
Events go only to the calendar account the firm itself connected.
What it refuses
| Answer | HTTP | Meaning |
|---|---|---|
forbidden | 403 | The session is not the firm's staff for this matter; the door reads nothing further. |
mfa-required | — | A staff session needs its second factor before any staff door opens: 401 to verify it, 403 to set one up. |
- Answer
forbidden- HTTP
- 403
- Meaning
- The session is not the firm's staff for this matter; the door reads nothing further.
- Answer
mfa-required- HTTP
- —
- Meaning
- A staff session needs its second factor before any staff door opens: 401 to verify it, 403 to set one up.
What can leave EstateDraft
Each action that can reach outside EstateDraft is declared in one registry with the channel it uses; the outbox refuses an action that is not declared.
- Calendar · a provider
calendar.event-push
Evidence
src/lib/second-factor.test.tssrc/lib/calendar.tssrc/lib/second-factor.ts
Reviewed: