# Firestore identity-boundary worksheet

Application and environment:
Review owner and date:
Current Firebase services:
Goal: change login / retain Firebase Auth / remove Firebase Auth from the selected access path

## Current path

| Client, job or function | Identity presented | Credential issuer | Data accessed | Permission enforcement | Owner |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

List direct SDK reads, realtime listeners, offline behavior, Storage operations and authentication-triggered functions separately.

## Proposed architecture

Selected path: existing Firebase / OIDC federation / custom-token bridge / server-mediated Firestore
Provider and configuration evidence:
Firebase Auth dependencies retained:
Stable application account mapping:
Server runtime identity and IAM permissions:
Rules and deployed database review:
Session, disable and revocation ownership:

## Synthetic rehearsal

| Case | Expected result | Observed result | Evidence | Reviewer |
| --- | --- | --- | --- | --- |
| Intended user reads an authorized record | | | | |
| Other customer's identifier | | | | |
| Missing or expired authenticated context | | | | |
| Removed membership with an existing session | | | | |
| Wrong API audience or issuer | | | | |
| Unintended direct client read or write | | | | |
| Existing listener or offline workflow | | | | |
| Background job and lifecycle function | | | | |
| Rollback after an identity change | | | | |

Record emulator tests separately from approved staging or provider-environment tests.
Do not claim that a server library is restricted by Firestore Security Rules.
Do not claim that a custom-token bridge removes Firebase Authentication.
Keep user records, credentials, project secrets and raw tokens out of this worksheet.

Unresolved requirements and owner:
Rollback and stop conditions:
Retirement conditions for old sessions and credentials:
Independent review and release decision:
